On 2023-05-21 14:32, Jon Turney wrote:
On 12/05/2023 19:09, Brian Inglis wrote:
On 2023-05-12 09:36, Jon Turney wrote:
On 08/05/2023 04:12, Brian Inglis wrote:
cpuid    0x00000007:0 ecx:7 shstk Shadow Stack support & Windows [20]20H1/[20]2004+
            => user_shstk User mode program Shadow Stack support
AMD SVM  0x8000000a:0 edx:25 vnmi virtual Non-Maskable Interrrupts
Sync AMD 0x80000008:0 ebx flags across two output locations

Thanks.  I applied this.

Does this need applying to the 3.4 branch as well?

TL;DR: don't think so, just the next mainline release.

How many users with the latest models will worry about this before 3.5 release about October, and may Cygwin have support by then?

I don't have the data to answer that question.

Instead, I would ask what have we done for previous additions to /proc/cpuinfo ?

While updated for each Linux release that makes visible changes dependent only on cpuid (and available Windows) data (without needing kernel data like processor bug errata, CR, and MSR settings), it is rarely mentioned in announcements, unless additional lines are added for better Linux compatibility.
Without the kernel info, some of the Linux output can not be provided.

This info is for compatibility and informational for human consumption, more a nice to have than an essential, and a side effect of keeping up my own arch and cpuid interests and code with AMD, Intel, and Linux next features.

I don't know if it is used by any code rather than using cpuid instructions to get the info directly.

I don't think Corinna ever back-ported it; I always also tested it on, and Corinna /may/ have also applied to it to, 32 bit 3.3 for consistency.

--
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                -- Antoine de Saint-Exupéry

Reply via email to