All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCHv3] Add KVM paravirt cpuid leaf
Date: Wed, 13 Jan 2010 18:23:32 +0200	[thread overview]
Message-ID: <20100113162332.GO7549@redhat.com> (raw)
In-Reply-To: <20100113161454.GN7549@redhat.com>

On Wed, Jan 13, 2010 at 06:14:54PM +0200, Gleb Natapov wrote:
> On Wed, Jan 13, 2010 at 10:05:33AM -0600, Anthony Liguori wrote:
> > >+#ifdef CONFIG_KVM_PARA
> > >+    /* Paravirtualization CPUIDs */
> > >+    memcpy(signature, "KVMKVMKVM\0\0\0", 12);
> > >+    c =&cpuid_data.entries[cpuid_i++];
> > >+    memset(c, 0, sizeof(*c));
> > >+    c->function = KVM_CPUID_SIGNATURE;
> > >+    c->eax = 0;
> > >+    c->ebx = signature[0];
> > >+    c->ecx = signature[1];
> > >+    c->edx = signature[2];
> > >+
> > >+    c =&cpuid_data.entries[cpuid_i++];
> > >+    memset(c, 0, sizeof(*c));
> > >+    c->function = KVM_CPUID_FEATURES;
> > >+    c->eax = env->cpuid_kvm_features&  get_para_features(env);
> > >+#endif
> > >+
> > >      cpu_x86_cpuid(env, 0, 0,&limit,&unused,&unused,&unused);
> > 
> > Instead of hooking here, would it make more sense to tie into the
> > generic cpuid function in helper.c?
> > 
> What do you mean? This patch ties into generic cpuid function in
> helper.c and pars kvm cpu flags there. Here we just configure
> kernel.
> 
Or do you mean making so that PV leaf will be available via
cpu_x86_cpuid()? This make sense, but lets do it after merging this
code path with qemu-kvm and the proposed patch brings qemu and
qemu-kvm close together.
 
--
			Gleb.

  reply	other threads:[~2010-01-13 16:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 12:44 [Qemu-devel] [PATCH] Add KVM paravirt cpuid leaf Gleb Natapov
2010-01-07 16:09 ` Anthony Liguori
2010-01-07 16:15   ` Gleb Natapov
2010-01-07 16:53     ` Anthony Liguori
2010-01-07 16:56       ` Avi Kivity
2010-01-07 17:08         ` Gleb Natapov
2010-01-07 18:02           ` Anthony Liguori
2010-01-07 18:10             ` Gleb Natapov
2010-01-07 16:59       ` Gleb Natapov
2010-01-07 16:24 ` [Qemu-devel] [PATCHv2] " Gleb Natapov
2010-01-11 19:18   ` Anthony Liguori
2010-01-11 19:18     ` [Qemu-devel] " Anthony Liguori
2010-01-11 19:33     ` Registering key events android (qemu based) emulator Anwar Ghani
2010-01-11 19:33       ` [Qemu-devel] " Anwar Ghani
2010-01-11 20:40     ` [Qemu-devel] [PATCHv2] Add KVM paravirt cpuid leaf Jan Kiszka
2010-01-11 20:40       ` Jan Kiszka
2010-01-11 21:36       ` Anthony Liguori
2010-01-11 21:36         ` Anthony Liguori
2010-01-11 23:22         ` Jan Kiszka
2010-01-11 23:22           ` Jan Kiszka
2010-01-12  7:23     ` Gleb Natapov
2010-01-12  7:23       ` Gleb Natapov
2010-01-12  8:40       ` Avi Kivity
2010-01-12  8:40         ` Avi Kivity
2010-01-12  8:42     ` Avi Kivity
2010-01-12  8:42       ` Avi Kivity
2010-01-13 13:25   ` [Qemu-devel] [PATCHv3] " Gleb Natapov
2010-01-13 16:05     ` Anthony Liguori
2010-01-13 16:14       ` Gleb Natapov
2010-01-13 16:23         ` Gleb Natapov [this message]
2010-01-13 16:57           ` Anthony Liguori
2010-01-13 23:28     ` Anthony Liguori

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=20100113162332.GO7549@redhat.com \
    --to=gleb@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.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 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.