public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Cui, Lili" <lili.cui@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Binutils <binutils@sourceware.org>
Subject: RE: [PATCH] x86: add missing APX logic to cpu_flags_match()
Date: Tue, 9 Jan 2024 11:00:09 +0000	[thread overview]
Message-ID: <SJ0PR11MB56009C36A37DCD4D096A59A29E6A2@SJ0PR11MB5600.namprd11.prod.outlook.com> (raw)
In-Reply-To: <29e3e221-f23d-4433-8787-40a3f2141760@suse.com>

> Subject: Re: [PATCH] x86: add missing APX logic to cpu_flags_match()
> 
> On 09.01.2024 06:36, Cui, Lili wrote:
> > By the way, I have a question about " t->cpu_any", is it specific to dual
> VEX/EVEX templates?
> 
> No. And I think it's used elsewhere already - see e.g. SFENCE.
> 
Oh, I get it. "any" means that any cpuid supports this instruction. It should be cleared for APX (Daul VEX/EVEX). IOW, "any" doesn't work with "cpuid&(cpuid|APX_F)".

Thanks,
Lili.

  reply	other threads:[~2024-01-09 11:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 12:15 Jan Beulich
2024-01-08  3:17 ` Cui, Lili
2024-01-08  7:56   ` Jan Beulich
2024-01-08  8:30     ` Cui, Lili
2024-01-08  8:58       ` Jan Beulich
2024-01-08 10:28         ` Cui, Lili
2024-01-08 10:38           ` Jan Beulich
2024-01-09  5:36             ` Cui, Lili
2024-01-09  8:30               ` Jan Beulich
2024-01-09 11:00                 ` Cui, Lili [this message]
2024-01-09 11:07                   ` Jan Beulich
2024-01-10  1:44                     ` Cui, Lili

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=SJ0PR11MB56009C36A37DCD4D096A59A29E6A2@SJ0PR11MB5600.namprd11.prod.outlook.com \
    --to=lili.cui@intel.com \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.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).