From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Igor Mammedov <imammedo@redhat.com>, Manish <manish.mishra@nutanix.com>
Cc: John Levon <john.levon@nutanix.com>,
qemu-devel@nongnu.org, berrange@redhat.com, zhao1.liu@intel.com,
pbonzini@redhat.com, bob.ball@nutanix.com,
prerna.saxena@nutanix.com
Subject: Re: [PATCH v1] target/i386: Always set leaf 0x1f
Date: Thu, 1 Aug 2024 23:11:51 +0800 [thread overview]
Message-ID: <e9f61d7d-2f72-4644-ba9f-241672d27cda@intel.com> (raw)
In-Reply-To: <20240801122537.4307ea77@imammedo.users.ipa.redhat.com>
On 8/1/2024 6:25 PM, Igor Mammedov wrote:
> On Thu, 1 Aug 2024 15:36:10 +0530
> Manish <manish.mishra@nutanix.com> wrote:
>
>> On 31/07/24 9:01 pm, Xiaoyao Li wrote:
>>> !-------------------------------------------------------------------|
>>> CAUTION: External Email
>>>
>>> |-------------------------------------------------------------------!
>>>
>>> On 7/31/2024 4:49 PM, John Levon wrote:
>>>> On Wed, Jul 31, 2024 at 03:02:15PM +0800, Xiaoyao Li wrote:
>>>>
>>>>>> Windows does not expect 0x1f to be present for any CPU model. But
>>>>>> if it
>>>>>> is exposed to the guest, it expects non-zero values.
>>>>>
>>>>> Please fix Windows!
>>>>
>>>> A ticket has been filed with MSFT, we are aware this is a guest bug.
>>>>
>>>> But that doesn't really help anybody trying to use Windows right now.
>>>
>>> For existing buggy Windows, we can still introduce
>>> "cpuid-0x1f-enforce" but not make it default on.
>>>
>>> People want to boot the buggy Windows needs to opt-in it themselves
>>> via "-cpu xxx,cpuid-0x1f-enforce=on". This way, we don't have live
>>> migration issue and it doesn't affect anything.
>>
>>
>> Yes, that makes sense, I will send a updated patch by tomorrow if no one
>> has any objection with this.
>
> I'd rename it to
> x-have-cpuid-0x1f-leaf
> (x-) to reflect that it's not stable/maintained and subject
> to be dropped in future
>
> Also please clearly spell out that it's a temporary workaround for ...
> in commit message.
I have a patch at hand, to introduce enable_cpuid_0x1f similar as
enable_cpuid_0xb, for TDX:
https://github.com/intel-staging/qemu-tdx/commit/de08fd30926bc9d7997af6bd12cfff1b998da8b7
It is not a temporary solution. So I would suggest to drop (x-).
If no objection, I think Manish can start from my patch and it only
misses a property definition for windows case:
DEFINE_PROP_BOOL("cpuid-0x1f", X86CPU, enable_cpuid_0x1f, false);
>
>>
>>>
>>>> regards
>>>> john
>>
>>
>> Thanks
>>
>> Manish Mishra
>>
>
next prev parent reply other threads:[~2024-08-01 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 7:52 [PATCH v1] target/i386: Always set leaf 0x1f manish.mishra
2024-07-24 9:00 ` Igor Mammedov
2024-07-24 10:29 ` Manish
2024-07-24 11:13 ` John Levon
2024-07-24 12:38 ` Manish
2024-07-24 12:54 ` Igor Mammedov
2024-07-24 13:50 ` Manish
2024-07-24 15:00 ` Zhao Liu
2024-07-29 6:49 ` Manish
2024-07-29 12:18 ` Igor Mammedov
2024-07-29 12:42 ` Manish
2024-07-30 11:39 ` Igor Mammedov
2024-07-31 14:00 ` Manish
2024-08-02 2:33 ` Zhao Liu
2024-07-31 7:02 ` Xiaoyao Li
2024-07-31 8:49 ` John Levon
2024-07-31 15:31 ` Xiaoyao Li
2024-08-01 10:06 ` Manish
2024-08-01 10:25 ` Igor Mammedov
2024-08-01 15:11 ` Xiaoyao Li [this message]
2024-08-01 16:46 ` Manish
2024-08-02 7:35 ` Xiaoyao Li
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=e9f61d7d-2f72-4644-ba9f-241672d27cda@intel.com \
--to=xiaoyao.li@intel.com \
--cc=berrange@redhat.com \
--cc=bob.ball@nutanix.com \
--cc=imammedo@redhat.com \
--cc=john.levon@nutanix.com \
--cc=manish.mishra@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=prerna.saxena@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@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).