linux-kernel - Re: Use CPUID to communicate with the hypervisor.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080929093313.GC9952@redhat.com>
Date:	Mon, 29 Sep 2008 12:33:13 +0300
From:	Gleb Natapov <gleb@...hat.com>
To:	Bernd Eckenfels <ecki@...a.inka.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Use CPUID to communicate with the hypervisor.

On Mon, Sep 29, 2008 at 11:08:10AM +0200, Bernd Eckenfels wrote:
> In article <48E085B3.1080507@...hat.com> you wrote:
> > In theory it can, but it would be a bad idea.  cpuid is best used to 
> > communicate cpu features; ACPI and DMI are (mostly) system features.
> 
> Besides that, nobody stops a Hypervisor to offer valid and usefull DMI and
> ACPI tables in the first place. I dont see a need to tunnel those through
> CPUID.
> 
There is a need to tunnel those somehow since ACPI/DMI tables resides in
a guest memory. Guest BIOS can build them, but some folks want to pass
additional ACPI tables from command line. So if CPUID is not suitable for
this there have to be another channel. CPUID can provide info if this channel
is available.

--
			Gleb.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/