From: Matthew Wilcox <willy@infradead.org>
To: Ram Tummala <rtummala@nvidia.com>
Cc: akpm@linux-foundation.org, fengwei.yin@intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
apopple@nvidia.com, stable@vger.kernel.org
Subject: Re: [PATCH] mm: Fix PTE_AF handling in fault path on architectures with HW AF support
Date: Wed, 10 Jul 2024 01:13:43 +0100 [thread overview]
Message-ID: <Zo3SN_qlYUWLAlyR@casper.infradead.org> (raw)
In-Reply-To: <20240710000942.623704-1-rtummala@nvidia.com>
On Tue, Jul 09, 2024 at 05:09:42PM -0700, Ram Tummala wrote:
> Commit 3bd786f76de2 ("mm: convert do_set_pte() to set_pte_range()")
> replaced do_set_pte() with set_pte_range() and that introduced a regression
> in the following faulting path of non-anonymous vmas on CPUs with HW AF
At no point in this do you say what "AF" stands for.
next prev parent reply other threads:[~2024-07-10 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 0:09 Ram Tummala
2024-07-10 0:13 ` Matthew Wilcox [this message]
2024-07-10 1:02 ` Alistair Popple
2024-07-10 1:08 ` Yin, Fengwei
2024-07-10 4:07 ` David Hildenbrand
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=Zo3SN_qlYUWLAlyR@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rtummala@nvidia.com \
--cc=stable@vger.kernel.org \
/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