From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
broonie@kernel.org
Subject: Re: [PATCH v2] arm64: Avoid repeated AA64MMFR1_EL1 register read on pagefault path
Date: Wed, 18 Jan 2023 13:08:32 -0300 [thread overview]
Message-ID: <874jsnbzb3.fsf@suse.de> (raw)
In-Reply-To: <20230117161401.GB17756@willie-the-truck> (Will Deacon's message of "Tue, 17 Jan 2023 16:14:02 +0000")
Will Deacon <will@kernel.org> writes:
> On Mon, Jan 16, 2023 at 05:41:35PM -0300, Gabriel Krisman Bertazi wrote:
>>
>> Considering the performance impact on kvm guests, unless someone
>> opposes, can we get this queued already for -rc5?
>
> Given this has been the case since v5.12 afaict and it's not a correctness
> issue, I was thinking we could queue this for 6.3?
hey Will,
On a second thought, I'm fine with having it only in 6.3. :)
--
Gabriel Krisman Bertazi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-18 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 15:19 [PATCH v2] arm64: Avoid repeated AA64MMFR1_EL1 register read on pagefault path Gabriel Krisman Bertazi
2023-01-11 8:34 ` Anshuman Khandual
2023-01-11 13:31 ` Gabriel Krisman Bertazi
2023-01-12 2:57 ` Anshuman Khandual
2023-01-12 3:05 ` Anshuman Khandual
2023-01-16 20:41 ` Gabriel Krisman Bertazi
2023-01-17 16:14 ` Will Deacon
2023-01-18 16:08 ` Gabriel Krisman Bertazi [this message]
2023-01-18 15:44 ` Catalin Marinas
2023-01-18 16:06 ` Gabriel Krisman Bertazi
2023-01-18 16:38 ` Will Deacon
2023-01-20 16:59 ` Catalin Marinas
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=874jsnbzb3.fsf@suse.de \
--to=krisman@suse.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).