qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] Add definitions for current cpu models..


From: Chris Wright
Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models..
Date: Wed, 20 Jan 2010 16:25:09 -0800
User-agent: Mutt/1.5.19 (2009-01-05)

* Daniel P. Berrange (address@hidden) wrote:
> To be honest all possible naming schemes for '-cpu <name>' are just as
> unfriendly as each other. The only user friendly option is '-cpu host'. 
> 
> IMHO, we should just pick a concise naming scheme & document it. Given
> they are all equally unfriendly, the one that has consistency with vmware
> naming seems like a mild winner.

Heh, I completely agree, and was just saying the same thing to John
earlier today.  May as well be -cpu {foo,bar,baz} since the meaning for
those command line options must be well-documented in the man page.

This is from an EVC kb article[1]:

ESX/ESXi 4.0 supports the following EVC modes:

    * AMD Opteron™ Generation 1 (Rev. E)
    * AMD Opteron™ Generation 2 (Rev. F)
    * AMD Opteron™ Generation 3 (Greyhound)
    * Intel® Xeon® Core2 (Merom)
    * Intel® Xeon® 45nm Core2 (Penryn)
    * Intel® Xeon® Core i7 (Nehalem) 

Not that different from John's proposal.

thanks,
-chris

[1] http://kb.vmware.com/kb/1005764




reply via email to

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