public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] format_proc_cpuinfo: add enqcmd cpuinfo flag
Date: Tue, 13 Oct 2020 20:07:14 +0200	[thread overview]
Message-ID: <20201013180714.GU26704@calimero.vinschen.de> (raw)
In-Reply-To: <20201013151108.36189-1-Brian.Inglis@SystematicSW.ab.ca>

On Oct 13 09:11, Brian Inglis wrote:
> 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.
> ---
>  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 6f6e8291a0ca..13397150ff53 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 */
> -- 
> 2.28.0

Pushed.


Thanks,
Corinna

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 15:11 Brian Inglis
2020-10-13 18:07 ` Corinna Vinschen [this message]

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=20201013180714.GU26704@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).