Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: kvmarm@lists.linux.dev, Marc Zyngier <maz@kernel.org>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Jing Zhang <jingzhangos@google.com>,
	Reiji Watanabe <reijiw@google.com>
Subject: Re: [PATCH 4/4] KVM: arm64: Always return generic v8 as the preferred target
Date: Mon, 10 Jul 2023 18:35:27 +0000	[thread overview]
Message-ID: <ZKxPb4/La5SPp3uM@linux.dev> (raw)
In-Reply-To: <23bdb1d7-4153-594b-75e7-3452385f81a6@huawei.com>

On Mon, Jul 10, 2023 at 11:13:34PM +0800, Zenghui Yu wrote:
> Hi Oliver,
> 
> On 2023/6/24 3:42, Oliver Upton wrote:
> > Userspace selecting an implementation-specific vCPU target has been
> > completely useless for a very long time. Let's go whole hog and start
> > returning the generic v8 target across all implementations as the
> > preferred target.
> > 
> > Uphold the pre-existing behavior by tolerating either the generic target
> > or an implementation-specific target if the vCPU happens to be running
> > on one of the lucky few parts.
> > 
> > Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
> 
> I love the idea.
> 
> Acked-by: Zenghui Yu <yuzenghui@huawei.com>

Thanks!

> > ---
> >  arch/arm64/kvm/arm.c   | 3 ++-
> >  arch/arm64/kvm/guest.c | 4 +---
> >  2 files changed, 3 insertions(+), 4 deletions(-)
> > 
> > diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> > index 3fa63fdbbf34..5a3b8b2e779b 100644
> > --- a/arch/arm64/kvm/arm.c
> > +++ b/arch/arm64/kvm/arm.c
> > @@ -1250,7 +1250,8 @@ static int kvm_vcpu_set_target(struct kvm_vcpu *vcpu,
> >  {
> >  	int ret;
> > -	if (init->target != kvm_target_cpu())
> > +	if (init->target != KVM_ARM_TARGET_GENERIC_V8 &&
> > +	    init->target != kvm_target_cpu())
> >  		return -EINVAL;
> 
> I can see that user-space can now select GENERIC_V8 or CORTEX_A53 (for
> example) between two KVM_ARM_VCPU_INIT calls on an A53 host, which was
> forbidden before this change. I don't think it's a big deal though.

Agreed, I thought the slight relaxation on invariance was OK. If needed,
we can always change the rules for a new target value, but I doubt we will
need to do that anytime soon.

-- 
Thanks,
Oliver

      reply	other threads:[~2023-07-10 18:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 19:42 [PATCH 0/4] KVM: arm64: Consistently use 'generic' vCPU target across all uarches Oliver Upton
2023-06-23 19:42 ` [PATCH 1/4] KVM: arm64: Delete pointless switch statement in kvm_reset_vcpu() Oliver Upton
2023-07-10 15:14   ` Zenghui Yu
2023-06-23 19:42 ` [PATCH 2/4] KVM: arm64: Remove pointless check for changed init target Oliver Upton
2023-06-23 19:42 ` [PATCH 3/4] KVM: arm64: Replace vCPU target with a configuration flag Oliver Upton
2023-07-10 15:17   ` Zenghui Yu
2023-06-23 19:42 ` [PATCH 4/4] KVM: arm64: Always return generic v8 as the preferred target Oliver Upton
2023-06-24  0:45   ` Marc Zyngier
2023-06-24  0:55     ` Oliver Upton
2023-07-10 15:13   ` Zenghui Yu
2023-07-10 18:35     ` Oliver Upton [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=ZKxPb4/La5SPp3uM@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=james.morse@arm.com \
    --cc=jingzhangos@google.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=reijiw@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox