From: Randy Dunlap <rdunlap@infradead.org>
To: Xin Hao <xhao@linux.alibaba.com>, namit@vmware.com
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org,
peterz@infradead.org, hpa@zytor.com, jroedel@suse.de,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] x86/mm/tlb: update some comments in pte_flags_need_flush
Date: Thu, 29 Sep 2022 20:06:05 -0700 [thread overview]
Message-ID: <5b329c5f-c4b6-5d58-422e-b90df66e13cb@infradead.org> (raw)
In-Reply-To: <20220930022434.51850-1-xhao@linux.alibaba.com>
On 9/29/22 19:24, Xin Hao wrote:
> There just changed the comment about 'flush_on_clear' check, which make
> the explanation more reasonable.
>
> Suggested-by: Nadav Amit <namit@vmware.com>
> Suggested-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
>
> Changes from v2
> (https://lore.kernel.org/lkml/20220929091040.45390-1-xhao@linux.alibaba.com/)
> - fix some comments suggested-by Nadav Amit <namit@vmware.com> and
> Randy Dunlap <rdunlap@infradead.org>
>
> arch/x86/include/asm/tlbflush.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/tlbflush.h b/arch/x86/include/asm/tlbflush.h
> index cda3118f3b27..2a17698fb194 100644
> --- a/arch/x86/include/asm/tlbflush.h
> +++ b/arch/x86/include/asm/tlbflush.h
> @@ -291,8 +291,8 @@ static inline bool pte_flags_need_flush(unsigned long oldflags,
> diff &= ~_PAGE_ACCESSED;
>
> /*
> - * Did any of the 'flush_on_clear' flags was clleared set from between
> - * 'oldflags' and 'newflags'?
> + * Consider the 'flush_on_clear' flags that are set on 'oldflags',
> + * Flush if any of these flags is cleared on 'newflags'.
> */
> if (diff & oldflags & flush_on_clear)
> return true;
> --
> 2.31.0
--
~Randy
prev parent reply other threads:[~2022-09-30 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 2:24 Xin Hao
2022-09-30 3:06 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b329c5f-c4b6-5d58-422e-b90df66e13cb@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xhao@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®