public inbox for cygwin-cvs@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org>
To: cygwin-cvs@sourceware.org
Subject: [newlib-cygwin] format_proc_cpuinfo: add enqcmd cpuinfo flag
Date: Tue, 13 Oct 2020 18:06:20 +0000 (GMT)	[thread overview]
Message-ID: <20201013180620.31649387084B@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=3fd14da2c36f32a6a8d5b8f2f6ed6fc38b9e90e3

commit 3fd14da2c36f32a6a8d5b8f2f6ed6fc38b9e90e3
Author: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
Date:   Tue Oct 13 09:11:08 2020 -0600

    format_proc_cpuinfo: add enqcmd cpuinfo flag
    
    Add linux-next 5.9 cpuinfo flag for Intel enqcmd/s instructions:
    x86/cpufeatures: Enumerate ENQCMD and ENQCMDS instructions:
    Work submission instruction comes in two flavors. ENQCMD can be called
    both in ring 3 and ring 0 and always uses the contents of a PASID MSR
    when shipping the command to the device. ENQCMDS allows a kernel driver
    to submit commands on behalf of a user process. The driver supplies the
    PASID value in ENQCMDS. There isn't any usage of ENQCMD in the kernel as
    of now.
    The CPU feature flag is shown as "enqcmd" in /proc/cpuinfo.

Diff:
---
 winsup/cygwin/fhandler_proc.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/winsup/cygwin/fhandler_proc.cc b/winsup/cygwin/fhandler_proc.cc
index 6f6e8291a..13397150f 100644
--- a/winsup/cygwin/fhandler_proc.cc
+++ b/winsup/cygwin/fhandler_proc.cc
@@ -1563,6 +1563,7 @@ format_proc_cpuinfo (void *, char *&destbuf)
 	  ftcprint (features1, 25, "cldemote");         /* cldemote instr */
 	  ftcprint (features1, 27, "movdiri");          /* movdiri instr */
 	  ftcprint (features1, 28, "movdir64b");        /* movdir64b instr */
+	  ftcprint (features1, 29, "enqcmd");		/* enqcmd/s instructions*/
         }
 
       /* AMD MCA cpuid 0x80000007 ebx */


                 reply	other threads:[~2020-10-13 18:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20201013180620.31649387084B@sourceware.org \
    --to=corinna@sourceware.org \
    --cc=cygwin-cvs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).