From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH 0/4] Improve cpuid x86 code.
Date: Fri, 30 Jan 2009 15:45:53 +0530 [thread overview]
Message-ID: <20090130101553.GB25998@amit-x200.pnq.redhat.com> (raw)
In-Reply-To: <1233249569-16686-1-git-send-email-glommer@redhat.com>
On (Thu) Jan 29 2009 [12:19:25], Glauber Costa wrote:
> Hey,
>
> This is a resend of the cpuid patches, following Anthony's last
> suggestion. It proved to lead to a much better code IMHO.
>
> I'm also using the existing host_cpuid function to mask out features,
> but now relying on kvm's provided ioctl. This seem to provide the expected
> behavior.
I had submitted patches previously to convert to get_cpuid2. If Anthony
has them in his queue, we're going to have clashes. My patches add full
support for cupid functions 4, 0xb and 0xd that's missing currently.
I also have a patch ready for function 2; guess I'll send them after
this stuff is in.
prev parent reply other threads:[~2009-01-30 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 17:19 [Qemu-devel] [PATCH 0/4] Improve cpuid x86 code Glauber Costa
2009-01-29 17:19 ` [Qemu-devel] [PATCH 1/4] convert cpuid registration to KVM_SET_CPUID2 Glauber Costa
2009-01-29 17:19 ` [Qemu-devel] [PATCH 2/4] Factor out common code in filling cpuid code Glauber Costa
2009-01-29 17:19 ` [Qemu-devel] [PATCH 3/4] mask out forbidden cpuid features with kvm ioctl Glauber Costa
2009-01-29 17:19 ` [Qemu-devel] [PATCH 4/4] kvm pv features PART I Glauber Costa
2009-01-29 19:17 ` Glauber Costa
2009-01-29 20:50 ` [Qemu-devel] Re: [PATCH 3/4] mask out forbidden cpuid features with kvm ioctl Anthony Liguori
2009-01-30 12:37 ` Glauber Costa
2009-02-03 21:25 ` Avi Kivity
2009-02-04 6:26 ` Amit Shah
2009-02-03 21:27 ` Avi Kivity
2009-02-03 21:36 ` Anthony Liguori
2009-01-30 10:15 ` Amit Shah [this message]
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=20090130101553.GB25998@amit-x200.pnq.redhat.com \
--to=amit.shah@redhat.com \
--cc=aliguori@us.ibm.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).