From: Karel Zak <kzak@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: akataria@vmware.com, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
avi@redhat.com, Rusty Russell <rusty@rustcorp.com.au>,
Zachary Amsden <zach@vmware.com>, Dan Hecht <dhecht@vmware.com>,
Jun.Nakajima@intel.com, ksrinivasan@novell.com,
Matthias Koenig <mkoenig@suse.de>
Subject: Re: Use CPUID to communicate with the hypervisor.
Date: Mon, 29 Sep 2008 22:56:34 +0200 [thread overview]
Message-ID: <20080929205634.GA2907@nb.net.home> (raw)
In-Reply-To: <48DD799C.3070706@zytor.com>
On Fri, Sep 26, 2008 at 05:09:00PM -0700, H. Peter Anvin wrote:
> Alok Kataria wrote:
>> +{
>> + if (cpu_has_hypervisor) {
>> + unsigned int eax, ebx, ecx, edx;
>> + char hyper_vendor_id[13];
>> +
>> + cpuid(HYPERVISOR_INFO_LEAF, &eax, &ebx, &ecx, &edx);
>> + memcpy(hyper_vendor_id + 0, &ebx, 4);
>> + memcpy(hyper_vendor_id + 4, &ecx, 4);
>> + memcpy(hyper_vendor_id + 8, &edx, 4);
>> + hyper_vendor_id[12] = '\0';
>> + printk(KERN_INFO "Hypervisor vendor id %s\n", hyper_vendor_id);
>> + }
>> +}
>> +
>
> This should be broken out into a separate file in cpu/*, because we
> *will* need to detect hypervisors by other means.
Yes. It would be nice to have "Hypervisor vendor id" somewhere in
/sys or /proc. It seems that userspace is already hungry for that
information:
http://article.gmane.org/gmane.linux.utilities.util-linux-ng/1788
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2008-09-29 21:13 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 23:46 Use CPUID to communicate with the hypervisor Alok Kataria
2008-09-27 0:09 ` H. Peter Anvin
2008-09-27 0:30 ` Alok Kataria
2008-09-27 0:32 ` H. Peter Anvin
2008-09-27 0:59 ` Nakajima, Jun
2008-09-27 1:55 ` H. Peter Anvin
2008-09-27 4:52 ` Nakajima, Jun
2008-09-29 20:56 ` Karel Zak [this message]
2008-09-27 1:02 ` Jeremy Fitzhardinge
2008-09-27 1:28 ` H. Peter Anvin
2008-09-27 3:11 ` Alok Kataria
2008-09-27 4:20 ` H. Peter Anvin
2008-09-27 5:37 ` Alok Kataria
2008-09-28 5:01 ` Jeremy Fitzhardinge
2008-09-29 9:28 ` Tim Deegan
2008-09-29 9:44 ` Avi Kivity
2008-09-29 6:55 ` Gleb Natapov
2008-09-29 7:37 ` Avi Kivity
2008-09-29 9:08 ` Bernd Eckenfels
2008-09-29 9:33 ` Gleb Natapov
2008-09-29 15:32 ` Nakajima, Jun
2008-09-30 9:16 ` Avi Kivity
2008-09-29 8:24 ` Gerd Hoffmann
2008-09-29 17:55 ` Alok Kataria
2008-09-29 17:58 ` H. Peter Anvin
2008-09-29 18:46 ` Gerd Hoffmann
2008-09-29 19:38 ` Alok Kataria
2008-09-29 20:31 ` H. Peter Anvin
2008-09-29 20:55 ` Nakajima, Jun
2008-09-29 21:07 ` H. Peter Anvin
2008-09-29 21:28 ` Jeremy Fitzhardinge
2008-09-29 21:49 ` H. Peter Anvin
2008-09-29 23:20 ` Zachary Amsden
2008-09-30 0:33 ` H. Peter Anvin
2008-09-30 0:12 ` Alok Kataria
2008-09-30 0:31 ` H. Peter Anvin
2008-09-30 0:56 ` Nakajima, Jun
2008-09-30 0:58 ` H. Peter Anvin
2008-09-30 1:14 ` Nakajima, Jun
2008-09-30 2:21 ` H. Peter Anvin
2008-09-30 3:14 ` Nakajima, Jun
2008-09-30 3:48 ` H. Peter Anvin
2008-09-29 22:46 ` Gerd Hoffmann
2008-09-30 0:33 ` Alok Kataria
2008-09-30 8:11 ` Gerd Hoffmann
2008-09-30 16:42 ` Zachary Amsden
2008-10-02 11:52 ` Avi Kivity
2008-10-01 4:35 ` [Hypervisors] TSC frequency change Alok Kataria
2008-10-01 9:47 ` Gerd Hoffmann
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=20080929205634.GA2907@nb.net.home \
--to=kzak@redhat.com \
--cc=Jun.Nakajima@intel.com \
--cc=akataria@vmware.com \
--cc=avi@redhat.com \
--cc=dhecht@vmware.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=ksrinivasan@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mkoenig@suse.de \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--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.