qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [kvm-devel] [Qemu-devel] Re: expose host CPU features to guests


From: Avi Kivity
Subject: Re: [kvm-devel] [Qemu-devel] Re: expose host CPU features to guests
Date: Sun, 09 Sep 2007 16:14:44 +0300
User-agent: Thunderbird 2.0.0.0 (X11/20070419)

Jamie Lokier wrote:
Avi Kivity wrote:
Let's start with '-cpu host' as 'cpu host-cpuid' and implement '-cpu host-os' on the first bug report? I have a feeling we won't ever see it.

I have a feeling you won't ever see it either, but not because it's a
missing feature.

Instead, I think a very small number of users will spend hours
frustrated that some obscure guest doesn't work properly on their
obscure x86 hardware, then they will learn that they should not use
"-cpuid host" for that guest on that hardware, even though it works
fine with other guests, and then their problem will be solved (albeit
at a cost), and seen as such an obscure combination that it might
never be reported to Qemu developers.

In other words, host-os is what _I'd_ implement because I care too
much about the poor obscure users and think it's the safe option, but
I'm not doing the implementing here ;-)

If you are curious what the differences are, do this in a current
Linux source tree:

    egrep -R '(set|clear)_bit\(X86_FEATURE' arch/{i386,x86_64}/kernel


Some of these are Linux issues, not host cpu issues (for example, it looks like VMI disables global pages).

Some of these issues may not impact the guest and we'd be removing them unnecessarily. Also, kvm doesn't run on obscure hardware (although kqemu does; qemu itself is not a candidate for -cpu host).


--
error compiling committee.c: too many arguments to function





reply via email to

[Prev in Thread] Current Thread [Next in Thread]