From: john cooper <john.cooper@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, john.cooper@redhat.com
Subject: Re: [PATCH] Add definitions for current cpu models..
Date: Tue, 05 Jan 2010 01:06:50 -0500 [thread overview]
Message-ID: <4B42D6FA.3020201@redhat.com> (raw)
In-Reply-To: <20091224130521.GD4781@amt.cnet>
Marcelo Tosatti wrote:
> On Mon, Dec 21, 2009 at 01:46:36AM -0500, john cooper wrote:
>> + {
>> + .name = "Opteron_G2",
>> + .level = 5,
>> + .vendor1 = CPUID_VENDOR_INTEL_1,
>> + .vendor2 = CPUID_VENDOR_INTEL_2,
>> + .vendor3 = CPUID_VENDOR_INTEL_3,
>
> Silly question: why a CPU named "Opteron_G2" uses intel vendor id's?
The feedback I had from AMD indicated using the Intel
strings for a family 15 cpu resulted in the least
amount of guest confusion. The upstream kvm64 model
does similarly.
Sorry for my late response here which was preempted
by the intervening holiday.
-john
--
john.cooper@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: john cooper <john.cooper@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: john.cooper@redhat.com, qemu-devel@nongnu.org,
KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCH] Add definitions for current cpu models..
Date: Tue, 05 Jan 2010 01:06:50 -0500 [thread overview]
Message-ID: <4B42D6FA.3020201@redhat.com> (raw)
In-Reply-To: <20091224130521.GD4781@amt.cnet>
Marcelo Tosatti wrote:
> On Mon, Dec 21, 2009 at 01:46:36AM -0500, john cooper wrote:
>> + {
>> + .name = "Opteron_G2",
>> + .level = 5,
>> + .vendor1 = CPUID_VENDOR_INTEL_1,
>> + .vendor2 = CPUID_VENDOR_INTEL_2,
>> + .vendor3 = CPUID_VENDOR_INTEL_3,
>
> Silly question: why a CPU named "Opteron_G2" uses intel vendor id's?
The feedback I had from AMD indicated using the Intel
strings for a family 15 cpu resulted in the least
amount of guest confusion. The upstream kvm64 model
does similarly.
Sorry for my late response here which was preempted
by the intervening holiday.
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2010-01-05 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 6:46 [PATCH] Add definitions for current cpu models john cooper
2009-12-21 6:46 ` [Qemu-devel] " john cooper
2009-12-24 13:05 ` Marcelo Tosatti
2010-01-05 6:06 ` john cooper [this message]
2010-01-05 6:06 ` [Qemu-devel] " john cooper
2009-12-24 13:45 ` [Qemu-devel] " Avi Kivity
2009-12-31 3:13 ` Jamie Lokier
2009-12-31 14:38 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2010-01-18 16:45 john cooper
2010-01-20 23:20 ` Arnd Bergmann
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=4B42D6FA.3020201@redhat.com \
--to=john.cooper@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.