From: Jordan Niethe <jniethe5@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: mikey@neuling.org, kvm@vger.kernel.org, sbhat@linux.ibm.com,
amachhiw@linux.vnet.ibm.com, gautam@linux.ibm.com,
kvm-ppc@vger.kernel.org, kconsul@linux.vnet.ibm.com,
vaibhav@linux.ibm.com
Subject: Re: [PATCH v3 2/6] KVM: PPC: Rename accessor generator macros
Date: Wed, 16 Aug 2023 13:20:18 +1000 [thread overview]
Message-ID: <efa0e456-1b7e-f12e-c720-076e962c7ca2@gmail.com> (raw)
In-Reply-To: <CUS4J2YPYFAO.3P4R24H4KFJ83@wheely>
On 14/8/23 6:27 pm, Nicholas Piggin wrote:
> On Mon Aug 7, 2023 at 11:45 AM AEST, Jordan Niethe wrote:
>> More "wrapper" style accessor generating macros will be introduced for
>> the nestedv2 guest support. Rename the existing macros with more
>> descriptive names now so there is a consistent naming convention.
>>
>> Signed-off-by: Jordan Niethe <jniethe5@gmail.com>
>
>> ---
>> v3:
>> - New to series
>> ---
>> arch/powerpc/include/asm/kvm_ppc.h | 60 +++++++++++++++---------------
>> 1 file changed, 30 insertions(+), 30 deletions(-)
>>
>> diff --git a/arch/powerpc/include/asm/kvm_ppc.h b/arch/powerpc/include/asm/kvm_ppc.h
>> index d16d80ad2ae4..b66084a81dd0 100644
>> --- a/arch/powerpc/include/asm/kvm_ppc.h
>> +++ b/arch/powerpc/include/asm/kvm_ppc.h
>> @@ -927,19 +927,19 @@ static inline bool kvmppc_shared_big_endian(struct kvm_vcpu *vcpu)
>> #endif
>> }
>>
>> -#define SPRNG_WRAPPER_GET(reg, bookehv_spr) \
>> +#define KVMPPC_BOOKE_HV_SPRNG_ACESSOR_GET(reg, bookehv_spr) \
>> static inline ulong kvmppc_get_##reg(struct kvm_vcpu *vcpu) \
>> { \
>> return mfspr(bookehv_spr); \
>> } \
>>
>> -#define SPRNG_WRAPPER_SET(reg, bookehv_spr) \
>> +#define KVMPPC_BOOKE_HV_SPRNG_ACESSOR_SET(reg, bookehv_spr) \
>> static inline void kvmppc_set_##reg(struct kvm_vcpu *vcpu, ulong val) \
>> { \
>> mtspr(bookehv_spr, val); \
>> } \
>>
>> -#define SHARED_WRAPPER_GET(reg, size) \
>> +#define KVMPPC_VCPU_SHARED_REGS_ACESSOR_GET(reg, size) \
>> static inline u##size kvmppc_get_##reg(struct kvm_vcpu *vcpu) \
>> { \
>> if (kvmppc_shared_big_endian(vcpu)) \
>> @@ -948,7 +948,7 @@ static inline u##size kvmppc_get_##reg(struct kvm_vcpu *vcpu) \
>> return le##size##_to_cpu(vcpu->arch.shared->reg); \
>> } \
>>
>> -#define SHARED_WRAPPER_SET(reg, size) \
>> +#define KVMPPC_VCPU_SHARED_REGS_ACESSOR_SET(reg, size) \
>> static inline void kvmppc_set_##reg(struct kvm_vcpu *vcpu, u##size val) \
>> { \
>> if (kvmppc_shared_big_endian(vcpu)) \
>> @@ -957,36 +957,36 @@ static inline void kvmppc_set_##reg(struct kvm_vcpu *vcpu, u##size val) \
>> vcpu->arch.shared->reg = cpu_to_le##size(val); \
>> } \
>>
>> -#define SHARED_WRAPPER(reg, size) \
>> - SHARED_WRAPPER_GET(reg, size) \
>> - SHARED_WRAPPER_SET(reg, size) \
>> +#define KVMPPC_VCPU_SHARED_REGS_ACESSOR(reg, size) \
>> + KVMPPC_VCPU_SHARED_REGS_ACESSOR_GET(reg, size) \
>> + KVMPPC_VCPU_SHARED_REGS_ACESSOR_SET(reg, size) \
>>
>> -#define SPRNG_WRAPPER(reg, bookehv_spr) \
>> - SPRNG_WRAPPER_GET(reg, bookehv_spr) \
>> - SPRNG_WRAPPER_SET(reg, bookehv_spr) \
>> +#define KVMPPC_BOOKE_HV_SPRNG_ACESSOR(reg, bookehv_spr) \
>> + KVMPPC_BOOKE_HV_SPRNG_ACESSOR_GET(reg, bookehv_spr) \
>> + KVMPPC_BOOKE_HV_SPRNG_ACESSOR_SET(reg, bookehv_spr) \
>>
>> #ifdef CONFIG_KVM_BOOKE_HV
>>
>> -#define SHARED_SPRNG_WRAPPER(reg, size, bookehv_spr) \
>> - SPRNG_WRAPPER(reg, bookehv_spr) \
>> +#define KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(reg, size, bookehv_spr) \
>> + KVMPPC_BOOKE_HV_SPRNG_ACESSOR(reg, bookehv_spr) \
>>
>> #else
>>
>> -#define SHARED_SPRNG_WRAPPER(reg, size, bookehv_spr) \
>> - SHARED_WRAPPER(reg, size) \
>> +#define KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(reg, size, bookehv_spr) \
>> + KVMPPC_VCPU_SHARED_REGS_ACESSOR(reg, size) \
>
> Not the greatest name I've ever seen :D Hard to be concice and
> consistent though, this is an odd one.
Yes, it is a bit wordy.
>
> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
Thanks.
>
>>
>> #endif
>>
>> -SHARED_WRAPPER(critical, 64)
>> -SHARED_SPRNG_WRAPPER(sprg0, 64, SPRN_GSPRG0)
>> -SHARED_SPRNG_WRAPPER(sprg1, 64, SPRN_GSPRG1)
>> -SHARED_SPRNG_WRAPPER(sprg2, 64, SPRN_GSPRG2)
>> -SHARED_SPRNG_WRAPPER(sprg3, 64, SPRN_GSPRG3)
>> -SHARED_SPRNG_WRAPPER(srr0, 64, SPRN_GSRR0)
>> -SHARED_SPRNG_WRAPPER(srr1, 64, SPRN_GSRR1)
>> -SHARED_SPRNG_WRAPPER(dar, 64, SPRN_GDEAR)
>> -SHARED_SPRNG_WRAPPER(esr, 64, SPRN_GESR)
>> -SHARED_WRAPPER_GET(msr, 64)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR(critical, 64)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(sprg0, 64, SPRN_GSPRG0)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(sprg1, 64, SPRN_GSPRG1)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(sprg2, 64, SPRN_GSPRG2)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(sprg3, 64, SPRN_GSPRG3)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(srr0, 64, SPRN_GSRR0)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(srr1, 64, SPRN_GSRR1)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(dar, 64, SPRN_GDEAR)
>> +KVMPPC_BOOKE_HV_SPRNG_OR_VCPU_SHARED_REGS_ACCESSOR(esr, 64, SPRN_GESR)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR_GET(msr, 64)
>> static inline void kvmppc_set_msr_fast(struct kvm_vcpu *vcpu, u64 val)
>> {
>> if (kvmppc_shared_big_endian(vcpu))
>> @@ -994,12 +994,12 @@ static inline void kvmppc_set_msr_fast(struct kvm_vcpu *vcpu, u64 val)
>> else
>> vcpu->arch.shared->msr = cpu_to_le64(val);
>> }
>> -SHARED_WRAPPER(dsisr, 32)
>> -SHARED_WRAPPER(int_pending, 32)
>> -SHARED_WRAPPER(sprg4, 64)
>> -SHARED_WRAPPER(sprg5, 64)
>> -SHARED_WRAPPER(sprg6, 64)
>> -SHARED_WRAPPER(sprg7, 64)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR(dsisr, 32)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR(int_pending, 32)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR(sprg4, 64)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR(sprg5, 64)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR(sprg6, 64)
>> +KVMPPC_VCPU_SHARED_REGS_ACESSOR(sprg7, 64)
>>
>> static inline u32 kvmppc_get_sr(struct kvm_vcpu *vcpu, int nr)
>> {
>
next prev parent reply other threads:[~2023-08-16 3:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 1:45 [PATCH v3 0/6] KVM: PPC: Nested APIv2 guest support Jordan Niethe
2023-08-07 1:45 ` [PATCH v3 1/6] KVM: PPC: Use getters and setters for vcpu register state Jordan Niethe
2023-08-14 8:08 ` Nicholas Piggin
2023-08-16 3:11 ` Jordan Niethe
2023-08-17 3:25 ` Michael Ellerman
2023-08-07 1:45 ` [PATCH v3 2/6] KVM: PPC: Rename accessor generator macros Jordan Niethe
2023-08-14 8:27 ` Nicholas Piggin
2023-08-16 3:20 ` Jordan Niethe [this message]
2023-08-07 1:45 ` [PATCH v3 3/6] KVM: PPC: Add helper library for Guest State Buffers Jordan Niethe
2023-08-07 1:45 ` [PATCH v3 4/6] KVM: PPC: Book3s HV: Hold LPIDs in an unsigned long Jordan Niethe
2023-08-14 8:12 ` Nicholas Piggin
2023-08-15 10:45 ` Michael Ellerman
2023-08-16 3:21 ` Jordan Niethe
2023-08-16 3:14 ` Jordan Niethe
2023-08-14 8:15 ` David Laight
2023-08-16 3:19 ` Jordan Niethe
2023-08-17 12:21 ` Michael Ellerman
2023-08-07 1:45 ` [PATCH v3 5/6] KVM: PPC: Add support for nestedv2 guests Jordan Niethe
2023-08-17 4:19 ` Michael Ellerman
2023-08-17 12:23 ` Michael Ellerman
2023-08-07 1:45 ` [PATCH v3 6/6] docs: powerpc: Document nested KVM on POWER Jordan Niethe
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=efa0e456-1b7e-f12e-c720-076e962c7ca2@gmail.com \
--to=jniethe5@gmail.com \
--cc=amachhiw@linux.vnet.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=kconsul@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=sbhat@linux.ibm.com \
--cc=vaibhav@linux.ibm.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).