From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: akataria@vmware.com, kvm@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Dan Hecht <dhecht@vmware.com>,
LKML <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
"avi@redhat.com" <avi@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC] CPUID usage for interaction between Hypervisors and Linux.
Date: Wed, 01 Oct 2008 13:08:08 -0700 [thread overview]
Message-ID: <48E3D8A8.604@goop.org> (raw)
In-Reply-To: <48E3D7A0.3000403@codemonkey.ws>
Anthony Liguori wrote:
> Mmm, cpuid bikeshedding :-)
My shade of blue is better.
>> The space 0x40000000-0x400000ff is reserved for hypervisor usage.
>>
>> This region is divided into 16 16-leaf blocks. Each block has the
>> structure:
>>
>> 0x400000x0:
>> eax: max used leaf within the leaf block (max 0x400000xf)
>
> Why even bother with this? It doesn't seem necessary in your proposal.
It allows someone to incrementally add things to their block in a fairly
orderly way. But more importantly, its the prevailing idiom, and the
existing and proposed cpuid schemes already do this, so they'd fit in as-is.
J
next prev parent reply other threads:[~2008-10-01 20:08 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 17:14 [RFC] CPUID usage for interaction between Hypervisors and Linux Alok Kataria
2008-10-01 17:14 ` Alok Kataria
2008-10-01 17:21 ` H. Peter Anvin
2008-10-01 17:21 ` H. Peter Anvin
2008-10-01 17:33 ` Alok Kataria
2008-10-01 17:45 ` H. Peter Anvin
2008-10-01 17:45 ` H. Peter Anvin
2008-10-01 18:06 ` Jeremy Fitzhardinge
2008-10-01 18:06 ` Jeremy Fitzhardinge
2008-10-01 21:05 ` Alok Kataria
2008-10-01 22:46 ` H. Peter Anvin
2008-10-02 1:11 ` Nakajima, Jun
2008-10-02 1:11 ` Nakajima, Jun
2008-10-02 1:11 ` Nakajima, Jun
2008-10-02 1:24 ` H. Peter Anvin
2008-10-02 1:24 ` H. Peter Anvin
2008-10-03 22:33 ` Nakajima, Jun
2008-10-03 22:33 ` Nakajima, Jun
2008-10-03 22:33 ` Nakajima, Jun
2008-10-03 23:30 ` H. Peter Anvin
2008-10-03 23:30 ` H. Peter Anvin
2008-10-04 0:27 ` Nakajima, Jun
2008-10-04 0:27 ` Nakajima, Jun
2008-10-04 0:35 ` H. Peter Anvin
2008-10-07 22:30 ` Nakajima, Jun
2008-10-07 22:30 ` Nakajima, Jun
2008-10-07 22:30 ` Nakajima, Jun
2008-10-07 22:37 ` H. Peter Anvin
2008-10-07 22:37 ` H. Peter Anvin
2008-10-07 23:45 ` Jeremy Fitzhardinge
2008-10-07 23:45 ` Jeremy Fitzhardinge
2008-10-08 1:09 ` H. Peter Anvin
2008-10-08 1:09 ` H. Peter Anvin
2008-10-07 23:41 ` Jeremy Fitzhardinge
2008-10-07 23:45 ` H. Peter Anvin
2008-10-07 23:45 ` H. Peter Anvin
2008-10-08 0:40 ` Jeremy Fitzhardinge
2008-10-08 0:40 ` Jeremy Fitzhardinge
2008-10-07 23:41 ` Jeremy Fitzhardinge
2008-10-04 0:35 ` H. Peter Anvin
2008-10-04 8:53 ` Avi Kivity
2008-10-04 8:53 ` Avi Kivity
2008-10-04 0:27 ` Nakajima, Jun
2008-10-01 22:46 ` H. Peter Anvin
2008-10-01 21:05 ` Alok Kataria
2008-10-01 17:33 ` Alok Kataria
2008-10-01 17:47 ` H. Peter Anvin
2008-10-01 17:47 ` H. Peter Anvin
2008-10-01 18:04 ` Jeremy Fitzhardinge
2008-10-01 20:03 ` Anthony Liguori
2008-10-01 20:08 ` Jeremy Fitzhardinge [this message]
2008-10-01 20:08 ` Jeremy Fitzhardinge
2008-10-01 21:03 ` Anthony Liguori
2008-10-01 21:03 ` Anthony Liguori
2008-10-01 21:03 ` Anthony Liguori
2008-10-01 20:03 ` Anthony Liguori
2008-10-01 18:04 ` Jeremy Fitzhardinge
2008-10-01 18:07 ` H. Peter Anvin
2008-10-01 18:12 ` Jeremy Fitzhardinge
2008-10-01 18:16 ` H. Peter Anvin
2008-10-01 18:16 ` H. Peter Anvin
2008-10-01 18:36 ` Jeremy Fitzhardinge
2008-10-01 18:36 ` Jeremy Fitzhardinge
2008-10-01 18:43 ` H. Peter Anvin
2008-10-01 19:56 ` Jeremy Fitzhardinge
2008-10-01 19:56 ` Jeremy Fitzhardinge
2008-10-01 18:43 ` H. Peter Anvin
2008-10-01 20:38 ` Chris Wright
2008-10-01 20:38 ` Chris Wright
2008-10-01 22:38 ` H. Peter Anvin
2008-10-01 22:38 ` H. Peter Anvin
2008-10-01 18:12 ` Jeremy Fitzhardinge
2008-10-01 18:07 ` H. Peter Anvin
2008-10-01 21:01 ` Alok Kataria
2008-10-01 21:01 ` Alok Kataria
2008-10-01 21:08 ` Anthony Liguori
2008-10-01 21:08 ` Anthony Liguori
2008-10-01 21:15 ` Chris Wright
2008-10-01 21:31 ` Anthony Liguori
2008-10-01 21:31 ` Anthony Liguori
2008-10-01 21:15 ` Chris Wright
2008-10-01 21:23 ` Alok Kataria
2008-10-01 21:23 ` Alok Kataria
2008-10-01 21:29 ` Anthony Liguori
2008-10-01 21:29 ` Anthony Liguori
2008-10-01 21:17 ` Jeremy Fitzhardinge
2008-10-01 21:34 ` Anthony Liguori
2008-10-01 21:43 ` Chris Wright
2008-10-02 11:29 ` Avi Kivity
2008-10-02 11:29 ` Avi Kivity
2008-10-01 21:43 ` Chris Wright
2008-10-01 23:47 ` Zachary Amsden
2008-10-01 23:47 ` Zachary Amsden
2008-10-02 0:39 ` H. Peter Anvin
2008-10-02 0:57 ` H. Peter Anvin
2008-10-02 0:57 ` H. Peter Anvin
2008-10-02 1:11 ` Zachary Amsden
2008-10-02 1:11 ` Zachary Amsden
2008-10-02 1:21 ` H. Peter Anvin
2008-10-02 1:21 ` H. Peter Anvin
2008-10-02 0:39 ` H. Peter Anvin
2008-10-02 0:41 ` Anthony Liguori
2008-10-02 0:41 ` Anthony Liguori
2008-10-01 21:34 ` Anthony Liguori
2008-10-01 21:17 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2008-10-01 17:14 Alok Kataria
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=48E3D8A8.604@goop.org \
--to=jeremy@goop.org \
--cc=akataria@vmware.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=dhecht@vmware.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.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.