All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, qemu-devel@nongnu.org
Cc: Roman Kagan <rkagan@virtuozzo.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] i386/kvm: add NoNonArchitecturalCoreSharing Hyper-V enlightenment
Date: Mon, 21 Oct 2019 18:26:14 +0200	[thread overview]
Message-ID: <66f1dd30-3e45-4dc6-ba0a-d52e5aae6501@redhat.com> (raw)
In-Reply-To: <878spe197z.fsf@vitty.brq.redhat.com>

On 21/10/19 16:09, Vitaly Kuznetsov wrote:
>>> +    if (cpu->hyperv_no_nonarch_cs == ON_OFF_AUTO_ON) {
>>> +        env->features[FEAT_HV_RECOMM_EAX] |= HV_NO_NONARCH_CORESHARING;
>>> +    } else if (cpu->hyperv_no_nonarch_cs == ON_OFF_AUTO_AUTO) {
>> Do you want to make auto the default if "-cpu host,migratable=off"?  It
>> can be done on top so I started queueing this patch.
> Hm, one thing is that CPUID 0x40000004 doesn't exist if no Hyper-V
> enlightenments are passed so we'll probably have to modify your idea to
> "-cpu host,migratable=off,+any-hyperv-enlightenment" but then the
> question is how conservative are we, like if QEMU command line doesn't
> change can new CPUID flags appear or not? And we'll probably need a way
> to explicitly disable HV_NO_NONARCH_CORESHARING if needed.

I would defer to Eduardo on whether "migratable=off" would allow adding
new CPUID flags.  The follow-up question however is whether we would
benefit from a "+hyperv" option that enables all known Hyper-V
enlightenment for a given machine type.

Paolo


  reply	other threads:[~2019-10-21 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 16:39 [PATCH] i386/kvm: add NoNonArchitecturalCoreSharing Hyper-V enlightenment Vitaly Kuznetsov
2019-10-21 13:08 ` Paolo Bonzini
2019-10-21 14:09   ` Vitaly Kuznetsov
2019-10-21 16:26     ` Paolo Bonzini [this message]
2019-10-21 17:15       ` Eduardo Habkost
2019-10-23 11:16         ` Vitaly Kuznetsov
2019-10-23 11:21           ` Eduardo Habkost

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=66f1dd30-3e45-4dc6-ba0a-d52e5aae6501@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkagan@virtuozzo.com \
    --cc=rth@twiddle.net \
    --cc=vkuznets@redhat.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.