From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-devel@nongnu.org
Cc: "Wang, Yong Y" <yong.y.wang@intel.com>,
"Dugger, Donald D" <donald.d.dugger@intel.com>
Subject: Re: [Qemu-devel] [PATCH] taget-i386: Broadwell CPU model
Date: Wed, 18 Jun 2014 12:41:47 +0200 [thread overview]
Message-ID: <53A16CEB.3080705@redhat.com> (raw)
In-Reply-To: <53A0A648.800@suse.de>
Il 17/06/2014 22:34, Andreas Färber ha scritto:
> Apart from that, looks sane, so if someone can confirm the
> Broadwell-specific values I'll be happy to fix the style and queue it
> for 2.1.
The only Broadwell machine I can see the data for (but I cannot access
it) is a laptop version (ULT) and it has family/model/stepping equal to
6/61/3. Eduardo used 6/61/2, that's okay too.
The CPUID features look sane, and match what Intel said about Broadwell
on the KVM mailing lists and also in private email.
Paolo
prev parent reply other threads:[~2014-06-18 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 20:11 [Qemu-devel] [PATCH] taget-i386: Broadwell CPU model Eduardo Habkost
2014-06-17 20:34 ` Andreas Färber
2014-06-17 20:39 ` Eduardo Habkost
2014-06-17 22:57 ` Eduardo Habkost
2014-06-18 10:41 ` Paolo Bonzini [this message]
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=53A16CEB.3080705@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=donald.d.dugger@intel.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yong.y.wang@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).