From: Chris Friesen <chris.friesen@windriver.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] The side effect of changing Processor Brand string?
Date: Tue, 5 Jun 2018 11:10:20 -0600 [thread overview]
Message-ID: <5B16C3FC.60402@windriver.com> (raw)
In-Reply-To: <AD4B58344A9BCE45A17661C5F05E0D893925DE13@shsmsx102.ccr.corp.intel.com>
On 06/04/2018 10:09 PM, You, Lizhen wrote:
> Hi All,
>
> I'd like to change the Processor Brand
> String(CPUID[0x80000002|0x80000003|0x80000004]) of my guest OSS cpu model to
> a string that won't be standard Intel or AMD related processor brand string.
> Would this change have any side effect on the applications that run on this
> guest? Seems some application would check the Processor Brand String for
> choosing different code path, for eg Oracle database?
Unless you know exactly what code will be running in the guest, I don't think
it's possible to answer whether it would impact the code running in the guest.
Chris
prev parent reply other threads:[~2018-06-05 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 4:09 [Qemu-devel] The side effect of changing Processor Brand string? You, Lizhen
2018-06-05 17:10 ` Chris Friesen [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=5B16C3FC.60402@windriver.com \
--to=chris.friesen@windriver.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 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).