From: "Cui, Lili" <lili.cui@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH V2] Support APX NF
Date: Tue, 19 Mar 2024 01:24:17 +0000 [thread overview]
Message-ID: <SJ0PR11MB5600C86F76AE81144E1CA78C9E2C2@SJ0PR11MB5600.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR11MB5600BC285885AF55E05A985C9E2A2@SJ0PR11MB5600.namprd11.prod.outlook.com>
> > >>> // LZCNT instruction
> > >>> lzcnt, 0xf30fbd, LZCNT, Modrm|CheckOperandSize|No_bSuf|No_sSuf,
> {
> > >>> Reg16|Reg32|Reg64|Unspecified|BaseIndex, Reg16|Reg32|Reg64 }
> > >>> +lzcnt, 0xf5, LZCNT|APX_F,
> > >>> +Modrm|CheckOperandSize|No_bSuf|No_sSuf|EVexMap4|NF, {
> > >>> +Reg16|Reg32|Reg64|Unspecified|BaseIndex, Reg16|Reg32|Reg64 }
> > >>
> > >> ... I think you mean LZCNT&APX_F here.
> > >>
> > >>> // POPCNT instruction
> > >>> popcnt, 0xf30fb8, POPCNT,
> > Modrm|CheckOperandSize|No_bSuf|No_sSuf,
> > >> {
> > >>> Reg16|Reg32|Reg64|Unspecified|BaseIndex, Reg16|Reg32|Reg64 }
> > >>> +popcnt, 0x88, POPCNT|APX_F,
> > >>> +Modrm|CheckOperandSize|No_bSuf|No_sSuf|EVexMap4|NF, {
> > >>> +Reg16|Reg32|Reg64|Unspecified|BaseIndex, Reg16|Reg32|Reg64 }
> > >>
> > >> Whereas here it ought to be just APX_F if the doc is to be trusted.
> > >
> > > I think they should be LZCNT&APX_F and POPCNT&APX_F, why do you
> > > think
> > POPCNT is special? I suspect I've missed something.
> >
> > Unless you're looking at a newer version of the APX spec than me,
> > you'll observe the difference when looking at the respective insn
> > pages: For LZCNT both CPUID bits are mentioned, while for POPCNT only
> > APX_F is there.
> >
> You are right. I will double confirm it with doc.
>
The CPUID of POPCNT should be POPCNT and APX_F, and the APX spec should update it in the next release. Thanks.
Lili.
next prev parent reply other threads:[~2024-03-19 1:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 8:15 Cui, Lili
2024-03-08 9:36 ` Jan Beulich
2024-03-11 13:54 ` Cui, Lili
2024-03-11 14:09 ` Jan Beulich
2024-03-12 6:12 ` Cui, Lili
2024-03-12 7:46 ` Jan Beulich
2024-03-12 8:51 ` Cui, Lili
2024-03-12 13:22 ` Cui, Lili
2024-03-12 13:53 ` Jan Beulich
2024-03-13 2:54 ` Cui, Lili
2024-03-13 7:36 ` Jan Beulich
2024-03-18 11:21 ` Cui, Lili
2024-03-18 11:50 ` Jan Beulich
2024-03-18 13:43 ` Cui, Lili
2024-03-19 1:24 ` Cui, Lili [this message]
2024-03-08 10:40 ` Jan Beulich
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=SJ0PR11MB5600C86F76AE81144E1CA78C9E2C2@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).