public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@Shaw.ca>,
	Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] fhandler/proc.cc(format_proc_cpuinfo): Add Linux 6.3 cpuinfo
Date: Sun, 21 May 2023 21:32:31 +0100	[thread overview]
Message-ID: <8818056b-6bc9-9e18-c5dd-a88a9106d535@dronecode.org.uk> (raw)
In-Reply-To: <8e45602e-91c6-9621-1e70-4b1b3c400679@Shaw.ca>

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?
> 
> 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 ?


  reply	other threads:[~2023-05-21 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  3:12 Brian Inglis
2023-05-12 15:36 ` Jon Turney
2023-05-12 18:09   ` Brian Inglis
2023-05-21 20:32     ` Jon Turney [this message]
2023-05-22 15:45       ` Brian Inglis
2023-06-05 16:55   ` Corinna Vinschen

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=8818056b-6bc9-9e18-c5dd-a88a9106d535@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Brian.Inglis@Shaw.ca \
    --cc=cygwin-patches@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).