From: Shivaprasad G Bhat <sbhat@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>,
kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: atrajeev@linux.vnet.ibm.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, namhyung@kernel.org,
naveen.n.rao@linux.ibm.com, pbonzini@redhat.com,
jniethe5@gmail.com
Subject: Re: [PATCH 6/6] KVM: PPC: Book3S HV: Add one-reg interface for HASHKEYR register
Date: Wed, 5 Jun 2024 18:43:02 +0530 [thread overview]
Message-ID: <3dea8d70-9f04-4410-8063-d98c392c10c7@linux.ibm.com> (raw)
In-Reply-To: <D1R0AHN2MCOS.BPHUJKSV7YSO@gmail.com>
On 6/4/24 11:37, Nicholas Piggin wrote:
> On Mon Jun 3, 2024 at 9:15 PM AEST, Shivaprasad G Bhat wrote:
>> The patch adds a one-reg register identifier which can be used to
>> read and set the virtual HASHKEYR for the guest during enter/exit
>> with KVM_REG_PPC_HASHKEYR. The specific SPR KVM API documentation
>> too updated.
>>
>> Signed-off-by: Shivaprasad G Bhat <sbhat@linux.ibm.com>
>> ---
>> Documentation/virt/kvm/api.rst | 1 +
>> arch/powerpc/include/uapi/asm/kvm.h | 1 +
>> arch/powerpc/kvm/book3s_hv.c | 6 ++++++
>> tools/arch/powerpc/include/uapi/asm/kvm.h | 1 +
>> 4 files changed, 9 insertions(+)
>>
>> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
>> index 81077c654281..0c22cb4196d8 100644
>> --- a/Documentation/virt/kvm/api.rst
>> +++ b/Documentation/virt/kvm/api.rst
>> @@ -2439,6 +2439,7 @@ registers, find a list below:
>> PPC KVM_REG_PPC_PSSCR 64
>> PPC KVM_REG_PPC_DEC_EXPIRY 64
>> PPC KVM_REG_PPC_PTCR 64
>> + PPC KVM_REG_PPC_HASHKEYR 64
> Just looking at the QEMU side of this change made me think... AFAIKS
> we need to also set and get and migrate the HASHPKEY SPR.
Thanks Nick. I have posted the v2 with changes for HASHPKEYR
and your other suggestions at
171759276071.1480.9356137231993600304.stgit@linux.ibm.com
Regards,
Shivaprasad
>
> The hashst/hashchk test cases might be "working" by chance if the SPR
> is always zero :/
>
> Thanks,
> Nick
next prev parent reply other threads:[~2024-06-05 13:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 11:13 [PATCH 0/6] KVM: PPC: Book3S HV: Nested guest migration fixes Shivaprasad G Bhat
2024-06-03 11:14 ` [PATCH 1/6] KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 Shivaprasad G Bhat
2024-06-03 11:14 ` [PATCH 2/6] KVM: PPC: Book3S HV: Fix the get_one_reg of SDAR Shivaprasad G Bhat
2024-06-03 11:14 ` [PATCH 3/6] KVM: PPC: Book3S HV nestedv2: Keep nested guest DEXCR in sync Shivaprasad G Bhat
2024-06-04 5:46 ` Nicholas Piggin
2024-06-03 11:14 ` [PATCH 4/6] KVM: PPC: Book3S HV: Add one-reg interface for DEXCR register Shivaprasad G Bhat
2024-06-04 5:43 ` Nicholas Piggin
2024-06-04 11:29 ` Michael Ellerman
2024-06-04 11:26 ` Michael Ellerman
2024-06-03 11:14 ` [PATCH 5/6] KVM: PPC: Book3S HV nestedv2: Keep nested guest HASHKEYR in sync Shivaprasad G Bhat
2024-06-04 5:46 ` Nicholas Piggin
2024-06-03 11:15 ` [PATCH 6/6] KVM: PPC: Book3S HV: Add one-reg interface for HASHKEYR register Shivaprasad G Bhat
2024-06-04 5:43 ` Nicholas Piggin
2024-06-04 6:07 ` Nicholas Piggin
2024-06-05 13:13 ` Shivaprasad G Bhat [this message]
2024-06-04 5:48 ` [PATCH 0/6] KVM: PPC: Book3S HV: Nested guest migration fixes Nicholas Piggin
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=3dea8d70-9f04-4410-8063-d98c392c10c7@linux.ibm.com \
--to=sbhat@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=jniethe5@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).