New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PCID #11
Comments
Your CPU doesn’t have INVPCID so enabling PCID would achieve nothing —
sorry :(
On Fri, Jan 5, 2018 at 7:03 PM rpodric ***@***.***> wrote:
I'm seeing PCID on "no" with a CPU (i5-2500k) that absolutely supports it
(MS's script agrees with your program).
Coreinfo confirms that it is there, however, which should eliminate it
being a firmware issue.
This occurs either on the latest Windows Insider build or Window 1709
(with the latest CU).
Is there a Windows setting, perhaps, to enable PCID (and INVPCID, for that
matter)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxIeLNfdddAxKN7_tb-8fc96UAS96Xyks5tHuKRgaJpZM4RVLA->
.
--
Best regards,
Alex Ionescu
|
Ah, OK, there's a dependency. Never would have figured that out. I wasn't really focusing on INVPCID since the MS script makes no mention of it, at least by that name, but sure enough Coreinfo gives it a "-". Thanks |
The MS script combines both. See the verbose flag :)
On Fri, Jan 5, 2018 at 7:23 PM rpodric ***@***.***> wrote:
Ah, OK, there's a dependency. Never would have figured that out.
I wasn't really focusing on INVPCID since the MS script makes no mention
of it, at least by that name, but sure enough Coreinfo gives it a "-".
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxIeJZoBcrEXJFhcQLB5ymcjffCWx8Nks5tHucVgaJpZM4RVLA->
.
--
Best regards,
Alex Ionescu
|
Yes, there it is--I had never seen mention of that switch. |
I've also looked at the Windows code that sets these flags, and it seems that both are either SET or UNSET. In other words, Windows will not report "PCID" support if INVPCID isn't set too. I'll make the tool combine them for more clarity. |
I'm seeing PCID on "no" with a CPU (i5-2500k) that absolutely supports it (MS's script agrees with your program).
Coreinfo confirms that it is there, however, which should eliminate it being a firmware issue.
This occurs either on the latest Windows Insider build or Window 1709 (with the latest CU).
Is there a Windows setting, perhaps, to enable PCID (and INVPCID, for that matter)?
The text was updated successfully, but these errors were encountered: