From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Jordan Niethe" <jniethe5@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 4/6] KVM: PPC: Book3s HV: Hold LPIDs in an unsigned long
Date: Mon, 14 Aug 2023 18:12:07 +1000 [thread overview]
Message-ID: <CUS477NDPEQI.27SBUCRNYD0XG@wheely> (raw)
In-Reply-To: <20230807014553.1168699-5-jniethe5@gmail.com>
On Mon Aug 7, 2023 at 11:45 AM AEST, Jordan Niethe wrote:
> The LPID register is 32 bits long. The host keeps the lpids for each
> guest in an unsigned word struct kvm_arch. Currently, LPIDs are already
> limited by mmu_lpid_bits and KVM_MAX_NESTED_GUESTS_SHIFT.
>
> The nestedv2 API returns a 64 bit "Guest ID" to be used be the L1 host
> for each L2 guest. This value is used as an lpid, e.g. it is the
> parameter used by H_RPT_INVALIDATE. To minimize needless special casing
> it makes sense to keep this "Guest ID" in struct kvm_arch::lpid.
>
> This means that struct kvm_arch::lpid is too small so prepare for this
> and make it an unsigned long. This is not a problem for the KVM-HV and
> nestedv1 cases as their lpid values are already limited to valid ranges
> so in those contexts the lpid can be used as an unsigned word safely as
> needed.
>
> In the PAPR, the H_RPT_INVALIDATE pid/lpid parameter is already
> specified as an unsigned long so change pseries_rpt_invalidate() to
> match that. Update the callers of pseries_rpt_invalidate() to also take
> an unsigned long if they take an lpid value.
I don't suppose it would be worth having an lpid_t.
> diff --git a/arch/powerpc/kvm/book3s_xive.c b/arch/powerpc/kvm/book3s_xive.c
> index 4adff4f1896d..229f0a1ffdd4 100644
> --- a/arch/powerpc/kvm/book3s_xive.c
> +++ b/arch/powerpc/kvm/book3s_xive.c
> @@ -886,10 +886,10 @@ int kvmppc_xive_attach_escalation(struct kvm_vcpu *vcpu, u8 prio,
>
> if (single_escalation)
> name = kasprintf(GFP_KERNEL, "kvm-%d-%d",
> - vcpu->kvm->arch.lpid, xc->server_num);
> + (unsigned int)vcpu->kvm->arch.lpid, xc->server_num);
> else
> name = kasprintf(GFP_KERNEL, "kvm-%d-%d-%d",
> - vcpu->kvm->arch.lpid, xc->server_num, prio);
> + (unsigned int)vcpu->kvm->arch.lpid, xc->server_num, prio);
> if (!name) {
> pr_err("Failed to allocate escalation irq name for queue %d of VCPU %d\n",
> prio, xc->server_num);
I would have thought you'd keep the type and change the format.
Otherwise seems okay too.
Thanks,
Nick
next prev parent reply other threads:[~2023-08-14 8:13 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
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 [this message]
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=CUS477NDPEQI.27SBUCRNYD0XG@wheely \
--to=npiggin@gmail.com \
--cc=amachhiw@linux.vnet.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=jniethe5@gmail.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=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).