From: Jan Beulich <jbeulich@suse.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: AndrewCooper <andrew.cooper3@citrix.com>,
Steven Haigh <netwiz@crc.id.au>, Andreas Kinzler <hfp@posteo.de>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Ryzen 3xxx works with Windows
Date: Mon, 18 Nov 2019 11:34:39 +0100 [thread overview]
Message-ID: <8d291d80-5cc2-b7da-4fd3-e530504279e8@suse.com> (raw)
In-Reply-To: <4f9cb404-995a-1479-160a-1cf96815cb9d@citrix.com>
On 15.11.2019 18:13, George Dunlap wrote:
> On 11/15/19 5:06 PM, Andreas Kinzler wrote:
>> Hello All,
>>
>> I compared the CPUID listings from Ryzen 2700X (attached as tar.xz) to
>> 3700X and found only very few differences. I added
>>
>> cpuid = [ "0x80000008:ecx=xxxxxxxxxxxxxxxx0100xxxxxxxxxxxx" ]
>>
>> to xl.cfg and then Windows runs great with 16 vCPUs. Cinebench R15 score
>> is >2050 which is more or less the bare metal value.
>
> Awesome. Any idea what those bits do?
That's the apic_id_size field (using the naming of
xen/include/xen/lib/x86/cpuid.h).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-18 10:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 17:06 [Xen-devel] Ryzen 3xxx works with Windows Andreas Kinzler
2019-11-15 17:13 ` George Dunlap
2019-11-18 10:34 ` Jan Beulich [this message]
2019-11-18 16:11 ` Andreas Kinzler
2019-11-18 16:25 ` George Dunlap
2019-11-19 23:11 ` Andreas Kinzler
2019-11-15 17:22 ` Steven Haigh
2019-11-18 11:39 ` [Xen-devel] [SUSPECTED SPAM]Ryzen " George Dunlap
2019-11-18 12:29 ` Jan Beulich
2019-11-18 12:36 ` [Xen-devel] Ryzen " Jan Beulich
2019-11-18 12:54 ` Jan Beulich
2019-11-18 15:15 ` George Dunlap
2019-11-18 15:26 ` Jan Beulich
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=8d291d80-5cc2-b7da-4fd3-e530504279e8@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=hfp@posteo.de \
--cc=netwiz@crc.id.au \
--cc=xen-devel@lists.xenproject.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.