From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>
Cc: kvmarm@lists.linux.dev, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH v2 0/4] KVM: arm64: Use 'generic' vCPU target across all uarches
Date: Tue, 11 Jul 2023 00:29:41 -0700 [thread overview]
Message-ID: <ZK0E5VoHimicxZv1@linux.dev> (raw)
In-Reply-To: <86ilaqx605.wl-maz@kernel.org>
On Tue, Jul 11, 2023 at 08:27:22AM +0100, Marc Zyngier wrote:
> On Mon, 10 Jul 2023 20:31:36 +0100,
> Oliver Upton <oliver.upton@linux.dev> wrote:
> >
> > kvm_vcpu_init::target is quite useless at this point. We don't do any
> > uarch-specific emulation in the first place, and require userspace
> > select the 'generic' vCPU target on all but a few implementations.
> >
> > Small series to (1) clean up usage of the target value in the kernel and
> > (2) switch to the 'generic' target on implementations that previously
> > had their own target values. The implementation-specific values are
> > still tolerated, though, to avoid UAPI breakage.
> >
> > v1: https://lore.kernel.org/kvmarm/20230623194258.2648987-1-oliver.upton@linux.dev/
> >
> > v1 -> v2:
> > - Set the generic v8 target in the kvm_vcpu_init struct initializer
> > (Marc)
> > - Use the kvm_vcpu_initialized() helper (Zenghui)
> > - Collect Zenghui's ack/reviews (Thanks!)
> >
> > Oliver Upton (4):
> > KVM: arm64: Delete pointless switch statement in kvm_reset_vcpu()
> > KVM: arm64: Remove pointless check for changed init target
> > KVM: arm64: Replace vCPU target with a configuration flag
> > KVM: arm64: Always return generic v8 as the preferred target
> >
> > arch/arm64/include/asm/kvm_host.h | 6 +++---
> > arch/arm64/kvm/arm.c | 24 +++++++++++-------------
> > arch/arm64/kvm/guest.c | 15 ---------------
> > arch/arm64/kvm/hyp/nvhe/switch.c | 2 +-
> > arch/arm64/kvm/reset.c | 25 ++++++++++---------------
> > 5 files changed, 25 insertions(+), 47 deletions(-)
> >
> >
> > base-commit: 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5
>
> Looks great to me. This is 6.6 material, right? If so, I'll earmark it
> as such.
Yup, I don't think there's any amount of BS I can say to make this look
like a fix :)
--
Thanks,
Oliver
next prev parent reply other threads:[~2023-07-11 7:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 19:31 [PATCH v2 0/4] KVM: arm64: Use 'generic' vCPU target across all uarches Oliver Upton
2023-07-10 19:31 ` [PATCH v2 1/4] KVM: arm64: Delete pointless switch statement in kvm_reset_vcpu() Oliver Upton
2023-07-11 13:00 ` Shaoqin Huang
2023-07-10 19:31 ` [PATCH v2 2/4] KVM: arm64: Remove pointless check for changed init target Oliver Upton
2023-07-11 4:55 ` Zenghui Yu
2023-07-11 13:37 ` Shaoqin Huang
2023-07-10 19:31 ` [PATCH v2 3/4] KVM: arm64: Replace vCPU target with a configuration flag Oliver Upton
2023-07-11 13:30 ` Shaoqin Huang
2023-07-10 19:31 ` [PATCH v2 4/4] KVM: arm64: Always return generic v8 as the preferred target Oliver Upton
2023-07-11 13:22 ` Shaoqin Huang
2023-07-11 7:27 ` [PATCH v2 0/4] KVM: arm64: Use 'generic' vCPU target across all uarches Marc Zyngier
2023-07-11 7:29 ` Oliver Upton [this message]
2023-07-28 8:47 ` Marc Zyngier
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=ZK0E5VoHimicxZv1@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.