From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Dor Laor" <dlaor@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
avi@redhat.com, kvm@vger.kernel.org,
"Andreas Färber" <afaerber@suse.de>,
"Igor Mammedov" <imammedo@redhat.com>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Anthony Liguori" <aliguori@us.ibm.com>,
gleb@redhat.com
Subject: Re: [PATCHv2 kvm] kvm_pv_eoi: add flag support
Date: Fri, 13 Jul 2012 03:03:46 +0300 [thread overview]
Message-ID: <20120713000346.GB9614@redhat.com> (raw)
In-Reply-To: <20120710125508.GE13348@otherpad.lan.raisama.net>
On Tue, Jul 10, 2012 at 09:55:08AM -0300, Eduardo Habkost wrote:
> On Tue, Jul 10, 2012 at 11:39:57AM +0300, Dor Laor wrote:
> > On 07/01/2012 06:08 PM, Michael S. Tsirkin wrote:
> > >Support the new PV EOI flag in kvm - it recently got merged
> > >into kvm.git. Set by default with -cpu kvm.
> > >Set for -cpu qemu by adding +kvm_pv_eoi.
> > >Clear by adding -kvm_pv_eoi to -cpu option.
> >
> > What about adding them to our cpu models?
> > It should go w/o saying for all models (SandyBridge, OpteronGx,..)
> > but there is the issue of backward compat. I remember we had a
> > discussion about pair the models w/ the current machine type (-M) but
> > I don't remember the final call.
> >
> > What's your take Eduardo?
>
> We can really add it, but only after adding the infra-structure to allow
> "versioned" CPU models (with per-machine-type aliases for backwards
> compatibility with older machine types).
>
> (The current status of this is "I am going to implement it", but there's
> no code do do that yet).
OK so I'll just wait and you'll make it happen?
Also is libvirt support needed?
> >
> > Cheers,
> > Dor
> >
> > >
> > >Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > >---
> > >
> > >Changes from v1:
> > > rebased to uq/master
> > >
> > > target-i386/cpu.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > >diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> > >index 5521709..ee1b64a 100644
> > >--- a/target-i386/cpu.c
> > >+++ b/target-i386/cpu.c
> > >@@ -77,7 +77,7 @@ static const char *ext3_feature_name[] = {
> > > };
> > >
> > > static const char *kvm_feature_name[] = {
> > >- "kvmclock", "kvm_nopiodelay", "kvm_mmu", "kvmclock", "kvm_asyncpf", NULL, NULL, NULL,
> > >+ "kvmclock", "kvm_nopiodelay", "kvm_mmu", "kvmclock", "kvm_asyncpf", NULL, "kvm_pv_eoi", NULL,
> > > NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
> > > NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
> > > NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
> > >
> >
> >
>
> --
> Eduardo
next prev parent reply other threads:[~2012-07-13 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 15:08 [PATCHv2 kvm] kvm_pv_eoi: add flag support Michael S. Tsirkin
2012-07-03 19:57 ` Marcelo Tosatti
2012-07-10 8:39 ` Dor Laor
2012-07-10 12:55 ` Eduardo Habkost
2012-07-13 0:03 ` Michael S. Tsirkin [this message]
2012-07-13 13:31 ` 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=20120713000346.GB9614@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mtosatti@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).