From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Salil Mehta <salil.mehta@huawei.com>,
"steven.price@arm.com" <steven.price@arm.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
"christoffer.dall@arm.com" <christoffer.dall@arm.com>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
Salil Mehta <salil.mehta@opnsrc.net>,
"andrew.jones@linux.dev" <andrew.jones@linux.dev>,
yuzenghui <yuzenghui@huawei.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Gareth Stockwell <Gareth.Stockwell@arm.com>
Subject: Re: [Question - ARM CCA] vCPU Hotplug Support in ARM Realm world might require ARM spec change?
Date: Wed, 19 Jul 2023 10:28:29 +0100 [thread overview]
Message-ID: <7da93c6e-1cbf-8840-282e-f115197b80c4@arm.com> (raw)
In-Reply-To: <9cb24131a09a48e9a622e92bf8346c9d@huawei.com>
Hi Salil
Thanks for raising this.
On 19/07/2023 03:35, Salil Mehta wrote:
> [Reposting it here from Linaro Open Discussion List for more eyes to look at]
>
> Hello,
> I have recently started to dabble with ARM CCA stuff and check if our
> recent changes to support vCPU Hotplug in ARM64 can work in the realm
> world. I have realized that in the RMM specification[1] PSCI_CPU_ON
> command(B5.3.3) does not handles the PSCI_DENIED return code(B5.4.2),
> from the host. This might be required to support vCPU Hotplug feature
> in the realm world in future. vCPU Hotplug is an important feature to
> support kata-containers in realm world as it reduces the VM boot time
> and facilitates dynamic adjustment of vCPUs (which I think should be
> true even with Realm world as current implementation only makes use
> of the PSCI_ON/OFF to realize the Hotplug look-like effect?)
>
>
> As per our recent changes [2], [3] related to support vCPU Hotplug on
> ARM64, we handle the guest exits due to SMC/HVC Hypercall in the
> user-space i.e. VMM/Qemu. In realm world, REC Exits to host due to
> PSCI_CPU_ON should undergo similar policy checks and I think,
>
> 1. Host should *deny* to online the target vCPUs which are NOT plugged
> 2. This means target REC should be denied by host. Can host call
> RMI_PSCI_COMPETE in such s case?
> 3. The *return* value (B5.3.3.1.3 Output values) should be PSCI_DENIED
The Realm exit with EXIT_PSCI already provides the parameters passed
onto the PSCI request. This happens for all PSCI calls except
(PSCI_VERSION and PSCI_FEAUTRES). The hyp could forward these exits to
the VMM and could invoke the RMI_PSCI_COMPLETE only when the VMM blesses
the request (wherever applicable).
However, the RMM spec currently doesn't allow denying the request.
i.e., without RMI_PSCI_COMPLETE, the REC cannot be scheduled back in.
We will address this in the RMM spec and get back to you.
Kind regards
Suzuki
> 4. Failure condition (B5.3.3.2) should be amended with
> runnable pre: target_rec.flags.runnable == NOT_RUNNABLE (?)
> post: result == PSCI_DENIED (?)
> 5. Change would also be required in the flow (D1.4 PSCI flows) depicting
> PSCI_CPU_ON flow (D1.4.1)
>
>
> I do understand that ARM CCA support is in its infancy stage and
> discussing about vCPU Hotplug in realm world seem to be a far-fetched
> idea right now. But specification changes require lot of time and if
> this change is really required then it should be further discussed
> within ARM.
>
> Many thanks!
>
>
> Bes regards
> Salil
>
>
> References:
>
> [1] https://developer.arm.com/documentation/den0137/latest/
> [2] https://github.com/salil-mehta/qemu.git virt-cpuhp-armv8/rfc-v1-port11052023.dev-1
> [3] https://git.gitlab.arm.com/linux-arm/linux-jm.git virtual_cpu_hotplug/rfc/v2
>
next prev parent reply other threads:[~2023-07-19 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 2:35 [Question - ARM CCA] vCPU Hotplug Support in ARM Realm world might require ARM spec change? Salil Mehta
2023-07-19 9:28 ` Suzuki K Poulose [this message]
2023-07-24 16:27 ` Suzuki K Poulose
2023-07-25 0:05 ` Salil Mehta
2023-07-25 11:19 ` Suzuki K Poulose
2023-07-27 14:24 ` Salil Mehta
2023-07-27 16:40 ` Suzuki K Poulose
2023-07-25 0:28 ` bibo mao
2023-07-25 0:56 ` Salil Mehta
2023-07-25 1:13 ` bibo mao
2023-07-25 5:45 ` Salil Mehta
2023-07-25 6:24 ` bibo mao
2023-07-27 14:15 ` Salil Mehta
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=7da93c6e-1cbf-8840-282e-f115197b80c4@arm.com \
--to=suzuki.poulose@arm.com \
--cc=Gareth.Stockwell@arm.com \
--cc=andrew.jones@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=james.morse@arm.com \
--cc=jean-philippe@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=salil.mehta@opnsrc.net \
--cc=steven.price@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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).