qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Don Slutz <Don@CloudSwitch.com>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv3] qemu: enable PV EOI for qemu 1.3
Date: Mon, 22 Oct 2012 15:12:00 +0200	[thread overview]
Message-ID: <20121022131159.GB16851@redhat.com> (raw)
In-Reply-To: <50851AB2.1060304@suse.de>

On Mon, Oct 22, 2012 at 12:06:42PM +0200, Andreas Färber wrote:
> Am 18.10.2012 17:01, schrieb Michael S. Tsirkin:
> > Enable KVM PV EOI by default. You can still disable it with
> > -kvm_pv_eoi cpu flag. To avoid breaking cross-version migration,
> > enable only for qemu 1.3 (or in the future, newer) machine type.
> > 
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> 
> Thanks for updating,
> 
> Reviewed-by: Andreas Färber <afaerber@suse.de>
> 
> The commit message is not so telling whether there are any downsides
> (security implications?) to enabling this by default if supported,

I don't think there could be security downsides because all this does
is tell guest about the feature in a convenient way.
A well behaved guest doesn't use a feature unless it's listed but
that's irrelevant for security.

> so
> I'll leave it to Anthony to ack/apply this.
> 
> Regards,
> Andreas

It used to be enabled. It was turned off in
ef8621b1a3b199c348606c0a11a77d8e8bf135f1
because it affected migration format and doing that
just before the release seemed too risky.


> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-10-22 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 15:01 [Qemu-devel] [PATCHv3] qemu: enable PV EOI for qemu 1.3 Michael S. Tsirkin
2012-10-22 10:06 ` Andreas Färber
2012-10-22 13:12   ` Michael S. Tsirkin [this message]
2012-10-22 12:17     ` Eduardo Habkost
2012-10-22 12:18 ` 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=20121022131159.GB16851@redhat.com \
    --to=mst@redhat.com \
    --cc=Don@CloudSwitch.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    /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).