From: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "x86@kernel.org" <x86@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Rudi Horn <rudi.horn@oracle.com>,
Joe Jin <joe.jin@oracle.com>
Subject: Re: [PATCH v3 0/2] x86/pkeys: Set XSTATE_BV[PKRU] when updating
Date: Thu, 21 Nov 2024 18:01:14 +0000 [thread overview]
Message-ID: <F08E74D2-E805-4B86-9B59-8A4A592FC78C@oracle.com> (raw)
In-Reply-To: <20241119174520.3987538-1-aruna.ramakrishna@oracle.com>
Hello,
Gentle reminder to review this patch.
Thanks,
Aruna
> On Nov 19, 2024, at 9:45 AM, Aruna Ramakrishna <aruna.ramakrishna@oracle.com> wrote:
>
> v3:
> - rebased to 6.12.0
> - no functional changes from v2
>
> v1 -> v2 updates:
> - corrected commit description of both patches to reference xstate_bv
> where appropriate
> - renamed local variable in update_pkru_in_sigframe()
> (no functional changes from v1)
>
> Aruna Ramakrishna (2):
> x86/pkeys: Change caller of update_pkru_in_sigframe()
> x86/pkeys: Set XSTATE_BV[PKRU] to 1 so that PKRU is XRSTOR'd correctly
>
> arch/x86/kernel/fpu/signal.c | 20 ++------------------
> arch/x86/kernel/fpu/xstate.h | 27 ++++++++++++++++++++++++++-
> 2 files changed, 28 insertions(+), 19 deletions(-)
>
> --
> 2.43.5
>
prev parent reply other threads:[~2024-11-21 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 17:45 [PATCH v3 0/2] x86/pkeys: Set XSTATE_BV[PKRU] when updating Aruna Ramakrishna
2024-11-19 17:45 ` [PATCH v3 1/2] x86/pkeys: Change caller of update_pkru_in_sigframe() Aruna Ramakrishna
2024-11-19 17:45 ` [PATCH v3 2/2] x86/pkeys: Set XSTATE_BV[PKRU] to 1 so that PKRU is XRSTOR'd correctly Aruna Ramakrishna
2024-11-23 0:10 ` Dave Hansen
2024-12-02 18:33 ` Aruna Ramakrishna
2024-12-02 18:35 ` Dave Hansen
2024-11-21 18:01 ` Aruna Ramakrishna [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=F08E74D2-E805-4B86-9B59-8A4A592FC78C@oracle.com \
--to=aruna.ramakrishna@oracle.com \
--cc=dave.hansen@linux.intel.com \
--cc=joe.jin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rudi.horn@oracle.com \
--cc=tglx@linutronix.de \
--cc=x86@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