From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: New kvm-related qemu patch queue
Date: Mon, 11 Jan 2010 09:51:30 +0200 [thread overview]
Message-ID: <20100111075130.GA7549@redhat.com> (raw)
In-Reply-To: <4B49E9C0.1020108@redhat.com>
On Sun, Jan 10, 2010 at 04:52:48PM +0200, Avi Kivity wrote:
> On 01/10/2010 04:49 PM, Gleb Natapov wrote:
> >
> >>If the feature is already in both, then morph qemu-kvm.git into what
> >>is already in qemu.git. Hopefully anything missing in qemu.git will
> >>be discovered while making the changes.
> >>
> >What about bugs that are present only in qemu.git? Like this:
> >http://patchwork.ozlabs.org/patch/42298/. Should it go through
> >qemu-kvm.git/uq/master?
>
> Yes. So there is a central place for kvm patches, and so they see autotest.
>
So I assume you'll take it then.
>
> >What about this one: http://patchwork.ozlabs.org/patch/42447/ should it
> >be postponed untill qemu.git and qemu-kvm.git converge on using the same
> >cpuid infrastructure, or add similar functionality to qemu-kvm to,
> >or add new cpu flags to qemu-kvm only and when cpuid code converge
> >qemu.git will have it too?
>
> Best to make qemu-kvm.git and qemu.git converge first. Duplicating
> the patch extends the problem. Of course if something is urgent we
> can bypass the process.
>
Actually, looking into it, this patch is needed for qemu-kvm.git and qemu.git
to converge. For qemu-kvm to use kvm -cpu flags the patch below should
be applied on top of the previous patch.
Signed-off-by: Gleb Natapov <gleb@redhat.com>
diff --git a/qemu-kvm-x86.c b/qemu-kvm-x86.c
index 82e362c..b3c371c 100644
--- a/qemu-kvm-x86.c
+++ b/qemu-kvm-x86.c
@@ -1308,7 +1308,7 @@ int kvm_arch_init_vcpu(CPUState *cenv)
pv_ent = &cpuid_ent[cpuid_nent++];
memset(pv_ent, 0, sizeof(*pv_ent));
pv_ent->function = KVM_CPUID_FEATURES;
- pv_ent->eax = get_para_features(kvm_context);
+ pv_ent->eax = cenv->cpuid_kvm_features & get_para_features(kvm_context);
#endif
kvm_trim_features(&cenv->cpuid_features,
--
Gleb.
WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: New kvm-related qemu patch queue
Date: Mon, 11 Jan 2010 09:51:30 +0200 [thread overview]
Message-ID: <20100111075130.GA7549@redhat.com> (raw)
In-Reply-To: <4B49E9C0.1020108@redhat.com>
On Sun, Jan 10, 2010 at 04:52:48PM +0200, Avi Kivity wrote:
> On 01/10/2010 04:49 PM, Gleb Natapov wrote:
> >
> >>If the feature is already in both, then morph qemu-kvm.git into what
> >>is already in qemu.git. Hopefully anything missing in qemu.git will
> >>be discovered while making the changes.
> >>
> >What about bugs that are present only in qemu.git? Like this:
> >http://patchwork.ozlabs.org/patch/42298/. Should it go through
> >qemu-kvm.git/uq/master?
>
> Yes. So there is a central place for kvm patches, and so they see autotest.
>
So I assume you'll take it then.
>
> >What about this one: http://patchwork.ozlabs.org/patch/42447/ should it
> >be postponed untill qemu.git and qemu-kvm.git converge on using the same
> >cpuid infrastructure, or add similar functionality to qemu-kvm to,
> >or add new cpu flags to qemu-kvm only and when cpuid code converge
> >qemu.git will have it too?
>
> Best to make qemu-kvm.git and qemu.git converge first. Duplicating
> the patch extends the problem. Of course if something is urgent we
> can bypass the process.
>
Actually, looking into it, this patch is needed for qemu-kvm.git and qemu.git
to converge. For qemu-kvm to use kvm -cpu flags the patch below should
be applied on top of the previous patch.
Signed-off-by: Gleb Natapov <gleb@redhat.com>
diff --git a/qemu-kvm-x86.c b/qemu-kvm-x86.c
index 82e362c..b3c371c 100644
--- a/qemu-kvm-x86.c
+++ b/qemu-kvm-x86.c
@@ -1308,7 +1308,7 @@ int kvm_arch_init_vcpu(CPUState *cenv)
pv_ent = &cpuid_ent[cpuid_nent++];
memset(pv_ent, 0, sizeof(*pv_ent));
pv_ent->function = KVM_CPUID_FEATURES;
- pv_ent->eax = get_para_features(kvm_context);
+ pv_ent->eax = cenv->cpuid_kvm_features & get_para_features(kvm_context);
#endif
kvm_trim_features(&cenv->cpuid_features,
--
Gleb.
next prev parent reply other threads:[~2010-01-11 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 12:02 New kvm-related qemu patch queue Avi Kivity
2010-01-10 12:02 ` [Qemu-devel] " Avi Kivity
2010-01-10 14:28 ` Gleb Natapov
2010-01-10 14:28 ` [Qemu-devel] " Gleb Natapov
2010-01-10 14:30 ` Avi Kivity
2010-01-10 14:30 ` [Qemu-devel] " Avi Kivity
2010-01-10 14:49 ` Gleb Natapov
2010-01-10 14:49 ` [Qemu-devel] " Gleb Natapov
2010-01-10 14:52 ` Avi Kivity
2010-01-10 14:52 ` [Qemu-devel] " Avi Kivity
2010-01-11 7:51 ` Gleb Natapov [this message]
2010-01-11 7:51 ` Gleb Natapov
2010-01-11 15:30 ` Anthony Liguori
2010-01-11 15:30 ` [Qemu-devel] " Anthony Liguori
2010-01-17 12:51 ` Avi Kivity
2010-01-17 12:51 ` [Qemu-devel] " Avi Kivity
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=20100111075130.GA7549@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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 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.