From: "Pawar, Amit" <Amit.Pawar@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATH] AMD MWAITX enablement
Date: Tue, 02 Jun 2015 13:35:00 -0000 [thread overview]
Message-ID: <0428E25D138CAA4D819A6FED9429E51AF4A3FE@SCYBEXDAG02.amd.com> (raw)
In-Reply-To: <556D83DE02000078000800CE@mail.emea.novell.com>
Thanks Jan and will come back with updated patch.
--Amit
-----Original Message-----
From: Jan Beulich [mailto:JBeulich@suse.com]
Sent: Tuesday, June 02, 2015 1:52 PM
To: Pawar, Amit
Cc: binutils@sourceware.org
Subject: Re: [PATH] AMD MWAITX enablement
>>> On 02.06.15 at 08:55, <Amit.Pawar@amd.com> wrote:
>--- a/opcodes/i386-opc.tbl
>+++ b/opcodes/i386-opc.tbl
>@@ -5938,3 +5938,16 @@ clzero, 0, 0xf01fc, None, 3, CpuCLZERO,
>No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|
>
> // CLZERO instructions end
>
>+// MONITORX/MWAITX instructions
>+monitorx, 0, 0xf01, 0xfa, 2, CpuMWAITX,
>+No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|ImmExt, { 0 } // Need to ensure only "monitorx %eax/%ax,%ecx,%edx" is accepted.
>+monitorx, 3, 0xf01, 0xfa, 2, CpuMWAITX|CpuNo64,
>+No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|ImmExt|AddrPrefixOp0, { Reg16|Reg32, Reg32, Reg32 } // Need to ensure only "monitorx %rax/%eax,%rcx,%rdx" is accepted.
>+monitorx, 3, 0xf01, 0xfa, 2, CpuMWAITX|Cpu64, No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|ImmExt|AddrPrefixOp0|NoRex64, { Reg32|Reg64, Reg64, Reg64 }
>+
>+mwaitx, 0, 0xf01, 0xfb, 2, CpuMWAITX,
>+No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|ImmExt, { 0 } // Need to ensure only "mwaitx %eax,%ecx" is accepted.
>+mwaitx, 2, 0xf01, 0xfb, 2, CpuMWAITX|CpuNo64,
>+No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|ImmExt|NoAVX, { Reg32, Reg32 } // Need to ensure only "mwaitx %rax,%rcx" is accepted.
>+mwaitx, 2, 0xf01, 0xfb, 2, CpuMWAITX|Cpu64,
>+No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|ImmExt|NoRex64|NoAVX,
>+{ Reg64, Reg64 } // MONITORX/MWAITX instructions end
Looking at the earlier submitted Linux side patch at least one of the instructions also uses %ebx - why is that not being expressed by the instruction forms taking explicit operands?
Jan
next prev parent reply other threads:[~2015-06-02 13:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 6:56 Pawar, Amit
2015-06-02 8:22 ` Jan Beulich
2015-06-02 13:35 ` Pawar, Amit [this message]
2015-06-08 6:16 ` Pawar, Amit
2015-06-08 7:05 ` Jan Beulich
2015-06-10 9:37 ` Pawar, Amit
2015-06-25 7:55 ` Pawar, Amit
2015-06-25 9:26 ` H.J. Lu
2015-06-26 5:46 ` Pawar, Amit
2015-06-26 10:04 ` H.J. Lu
2015-06-26 11:09 ` Pawar, Amit
2015-06-26 11:55 ` H.J. Lu
2015-06-26 15:00 ` Pawar, Amit
2015-06-26 15:04 ` H.J. Lu
2015-06-26 16:26 ` Pawar, Amit
2015-06-26 16:30 ` H.J. Lu
2015-06-26 16:33 ` Pawar, Amit
2015-06-26 16:39 ` Pawar, Amit
2015-06-26 16:43 ` H.J. Lu
2015-06-26 16:52 ` Pawar, Amit
2015-06-26 18:02 ` Andreas Schwab
2015-06-27 5:20 ` Pawar, Amit
2015-06-30 6:58 ` Pawar, Amit
2015-06-30 14:53 ` H.J. Lu
2015-06-30 15:39 ` Pawar, Amit
2015-06-26 17:06 ` Pawar, Amit
2015-06-26 17:08 ` H.J. Lu
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=0428E25D138CAA4D819A6FED9429E51AF4A3FE@SCYBEXDAG02.amd.com \
--to=amit.pawar@amd.com \
--cc=JBeulich@suse.com \
--cc=binutils@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).