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

["Natalia Portillo" <claunia@claunia.com>]

Hi,

> On Mon, Sep 10, 2007 at 12:47:51PM +0100, Natalia Portillo wrote:
>> I don't see in what is it useful without KVM/KQEMU.
>
> It is not. I tried to be clear about it in my post. Sorry for not being
> clearer.
Ok now understood.

>> And even with them there are some instructions that can't be accesible
>> without KQEMU/KVM prepared for them.
>
> I suspect this is true. For example, in my patch I blocked ACPI and VMX.
> Still, those features that ARE exposed to the guest, speed it up. Isn't
> it the Right Thing?
Well, I prefer to say "it is a right thing" :p

>> And, the -cpu option, should be enabled in x86 and x86_64 to
>> enable/disable emulation of instructions (and them cpuid adjusted to
>> indicate them).
>
> I'm not sure I understand this comment. If you mean that -cpu should not
> expose a feature that is not emulated by qemu, I agree.
I mean there should be a -cpu 8086, 286, 386, 486, pentium, pentium2, so on

If you use 8086, qemu should behave as a 16-bit real-mode only processor  
doing an "unknown instruction" exception on anything not defined in the  
8086 real processor.
And so on.

And also behave, at identification (CPUID, or legacy identification), like  
the selected CPU (for example -cpu 486 says family 4 model x stepping y,  
no l2 cache, so on)

This can help some operating systems that hangs on unexpected  
identifications (NT 3.xx is the best example, as happens also on real  
hardware), and identifying badly implemented instructions on behave of cpu  
family (for example, in pentium an OS works flawlessly, in pentium2 an OS  
hangs just before sending CMOV instruction).

If you implement it, count with my vote for inclusion :p

(As I think x86, and x86-64 are the only ones archs that still dont  
implement -cpu in qemu. and remember, please, x86_64 only composes from  
pentium4 upwards and athlon64 upwards, no sense to behave like 386 in  
x86-64 emulator lol)

Regards