From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6567] KVM: Get all cpuid values from function 2 (Amit Shah)
Date: Mon, 09 Feb 2009 18:06:36 +0200 [thread overview]
Message-ID: <4990548C.60706@redhat.com> (raw)
In-Reply-To: <E1LWYP7-000785-3Z@cvs.savannah.gnu.org>
Anthony Liguori wrote:
> Revision: 6567
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6567
> Author: aliguori
> Date: 2009-02-09 15:50:36 +0000 (Mon, 09 Feb 2009)
>
> Log Message:
> -----------
> KVM: Get all cpuid values from function 2 (Amit Shah)
>
> cpuid function 2 can have multiple values to describe cache behaviour.
> Loop till we have fetched all the values.
>
Note that if we are rescheduled on another cpu, or if another process
calls cpuid 2 during the loop on the same cpu, this will break.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-02-09 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 15:50 [Qemu-devel] [6567] KVM: Get all cpuid values from function 2 (Amit Shah) Anthony Liguori
2009-02-09 16:06 ` Avi Kivity [this message]
2009-02-09 16:46 ` Anthony Liguori
2009-02-09 17:03 ` Amit Shah
2009-02-09 18:27 ` 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=4990548C.60706@redhat.com \
--to=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 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).