From: Michael Ellerman <mpe@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>, linuxppc-dev@lists•ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail•com>
Subject: Re: [PATCH v3 3/3] KVM: PPC: Add KVM_CAP_PPC_AIL_MODE_3
Date: Tue, 22 Feb 2022 14:34:08 +1100 [thread overview]
Message-ID: <87a6ejpob3.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220221072353.2219034-4-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail•com> writes:
> Add KVM_CAP_PPC_AIL_MODE_3 to advertise the capability to set the AIL
> resource mode to 3 with the H_SET_MODE hypercall. This capability
> differs between processor types and KVM types (PR, HV, Nested HV), and
> affects guest-visible behaviour.
>
> QEMU will implement a cap-ail-mode-3 to control this behaviour[1], and
> use the KVM CAP if available to determine KVM support[2].
>
> [1] https://lists.nongnu.org/archive/html/qemu-ppc/2022-02/msg00437.html
> [2] https://lists.nongnu.org/archive/html/qemu-ppc/2022-02/msg00439.html
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
> ---
> Documentation/virt/kvm/api.rst | 14 ++++++++++++++
> arch/powerpc/include/asm/setup.h | 2 ++
> arch/powerpc/kvm/powerpc.c | 20 ++++++++++++++++++++
> arch/powerpc/platforms/pseries/setup.c | 12 +++++++++++-
> include/uapi/linux/kvm.h | 1 +
> tools/include/uapi/linux/kvm.h | 1 +
> 6 files changed, 49 insertions(+), 1 deletion(-)
This one especially, but may as well be the whole series, needs to be
Cc'ed to kvm@vger•kernel.org, so that the generic KVM folks are aware of
it.
Can you do a resend Cc'ing them please.
cheers
prev parent reply other threads:[~2022-02-22 3:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 7:23 [PATCH v3 0/3] KVM: PPC: Book3S PR: Fixes for AIL and SCV Nicholas Piggin
2022-02-21 7:23 ` [PATCH v3 1/3] KVM: PPC: Book3S PR: Disable SCV when AIL could be disabled Nicholas Piggin
2022-02-21 7:23 ` [PATCH v3 2/3] KVM: PPC: Book3S PR: Disallow AIL != 0 Nicholas Piggin
2022-02-21 7:23 ` [PATCH v3 3/3] KVM: PPC: Add KVM_CAP_PPC_AIL_MODE_3 Nicholas Piggin
2022-02-21 12:59 ` Fabiano Rosas
2022-02-22 3:34 ` Michael Ellerman [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=87a6ejpob3.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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