From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: akataria@vmware.com, "avi@redhat.com" <avi@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Gerd Hoffmann <kraxel@redhat.com>, Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Dan Hecht <dhecht@vmware.com>, Zachary Amsden <zach@vmware.com>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [RFC] CPUID usage for interaction between Hypervisors and Linux.
Date: Wed, 01 Oct 2008 11:36:27 -0700 [thread overview]
Message-ID: <48E3C32B.3090701@goop.org> (raw)
In-Reply-To: <48E3BE65.2050909@zytor.com>
H. Peter Anvin wrote:
> With a sufficiently large block, we could use fixed points, e.g. by
> having each vendor create interfaces in the 0x40SSSSXX range, where
> SSSS is the PCI ID they use for PCI devices.
Sure, you could do that, but you'd still want to have a signature in
0x40SSSS00 to positively identify the chunk. And what if you wanted
more than 256 leaves?
> Note that I said "create interfaces". It's important that all about
> this is who specified the interface -- for "what hypervisor is this"
> just use 0x40000000 and disambiguate based on that.
"What hypervisor is this?" isn't a very interesting question; if you're
even asking it then it suggests that something has gone wrong. Its much
more useful to ask "what interfaces does this hypervisor support?", and
enumerating a smallish range of well-known leaves looking for signatures
is the simplest way to do that. (We could use signatures derived from
the PCI vendor IDs which would help with managing that namespace.)
J
next prev parent reply other threads:[~2008-10-01 18:36 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: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 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: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-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 8:53 ` Avi Kivity
2008-10-04 8:53 ` Avi Kivity
2008-10-04 0:27 ` Nakajima, Jun
2008-10-02 1:11 ` Nakajima, Jun
2008-10-01 22:46 ` H. Peter Anvin
2008-10-01 21:05 ` Alok Kataria
2008-10-01 18:06 ` Jeremy Fitzhardinge
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 18:07 ` H. Peter Anvin
2008-10-01 18:07 ` H. Peter Anvin
2008-10-01 18:12 ` Jeremy Fitzhardinge
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 [this message]
2008-10-01 18:43 ` H. Peter Anvin
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 20:38 ` Chris Wright
2008-10-01 22:38 ` H. Peter Anvin
2008-10-01 22:38 ` H. Peter Anvin
2008-10-01 20:38 ` Chris Wright
2008-10-01 18:36 ` Jeremy Fitzhardinge
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:15 ` Chris Wright
2008-10-01 21:31 ` Anthony Liguori
2008-10-01 21:31 ` Anthony Liguori
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:23 ` Alok Kataria
2008-10-01 21:17 ` Jeremy Fitzhardinge
2008-10-01 21:17 ` Jeremy Fitzhardinge
2008-10-01 21:34 ` Anthony Liguori
2008-10-01 21:34 ` Anthony Liguori
2008-10-01 21:43 ` Chris Wright
2008-10-01 21:43 ` Chris Wright
2008-10-02 11:29 ` Avi Kivity
2008-10-02 11:29 ` Avi Kivity
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: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:41 ` Anthony Liguori
2008-10-02 0:41 ` Anthony Liguori
2008-10-01 21:01 ` Alok Kataria
2008-10-01 18:04 ` Jeremy Fitzhardinge
2008-10-01 20:03 ` Anthony Liguori
2008-10-01 20:08 ` Jeremy Fitzhardinge
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
-- 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=48E3C32B.3090701@goop.org \
--to=jeremy@goop.org \
--cc=akataria@vmware.com \
--cc=avi@redhat.com \
--cc=dhecht@vmware.com \
--cc=hpa@zytor.com \
--cc=jun.nakajima@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=zach@vmware.com \
/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.