From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Wanpeng Li" <kernellwp@gmail.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RESEND v2] i386/kvm: add support for KVM_CAP_X86_DISABLE_EXITS
Date: Wed, 16 May 2018 18:13:17 +0300 [thread overview]
Message-ID: <20180516180847-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2871c099-79fe-8432-12c9-637e743cc89c@redhat.com>
On Wed, May 16, 2018 at 05:04:41PM +0200, Paolo Bonzini wrote:
> On 16/05/2018 16:22, Michael S. Tsirkin wrote:
> >> kvm-hint-dedicated=on only sets the CPUID bit, which Linux for example
> >> uses that to disable pv spinlocks. "-realtime dedicated-cpus=on" only
> >> disables the vmexits. You can use the two independently.
> >
> > But when would you want to use the two independently?
>
> 1) For testing
>
> 2) When some of your QEMUs are too old to support kvm-hint-dedicated=on,
> you may still want to use -realtime dedicated-cpus=on to get better
> performance on the new one.
>
> Paolo
For the second purpose, can't we handle this using machine types?
--
MST
next prev parent reply other threads:[~2018-05-16 15:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 8:24 [Qemu-devel] [PATCH RESEND v2] i386/kvm: add support for KVM_CAP_X86_DISABLE_EXITS Wanpeng Li
2018-04-17 8:28 ` no-reply
2018-04-17 18:08 ` Michael S. Tsirkin
2018-04-18 1:09 ` Wanpeng Li
2018-05-11 21:57 ` Michael S. Tsirkin
2018-05-12 0:49 ` Wanpeng Li
2018-04-17 20:59 ` Eduardo Habkost
2018-04-18 1:20 ` Wanpeng Li
2018-04-19 15:48 ` Paolo Bonzini
2018-04-19 19:56 ` Eduardo Habkost
2018-04-19 21:32 ` Paolo Bonzini
2018-04-19 21:53 ` Eduardo Habkost
2018-05-11 22:12 ` Michael S. Tsirkin
2018-05-16 12:34 ` Eduardo Habkost
2018-05-16 14:26 ` Michael S. Tsirkin
2018-05-17 17:34 ` Eduardo Habkost
2018-05-17 17:57 ` Michael S. Tsirkin
2018-05-17 18:18 ` Eduardo Habkost
2018-05-16 12:44 ` Paolo Bonzini
2018-05-16 14:22 ` Michael S. Tsirkin
2018-05-16 15:04 ` Paolo Bonzini
2018-05-16 15:13 ` Michael S. Tsirkin [this message]
2018-05-16 15:33 ` Eduardo Habkost
2018-05-16 16:21 ` Michael S. Tsirkin
2018-05-16 17:20 ` 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=20180516180847-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@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 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).