From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH 0/2] x86: adjust disassembling of selector-access insns
Date: Fri, 14 Jul 2023 12:01:20 +0200 [thread overview]
Message-ID: <3f44f9a7-2f4c-d92d-ec19-5023f317357a@suse.com> (raw)
While the first patch is merely simplifying things (back), the latter
(slightly RFC) improves consistency on the disassembler side along the
lines of earlier improvements (c9f5b96bdab0 "x86: correct handling of
LAR and LSL") and ones done only on the assembler side (5eeeafe0a688
"x86: have insns acting on segment selector values allow for consistent
operands").
1: simplify disassembly of LAR/LSL
2: adjust disassembly of insns operating on selector values
Jan
next reply other threads:[~2023-07-14 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 10:01 Jan Beulich [this message]
2023-07-14 10:02 ` [PATCH 1/2] x86: simplify disassembly of LAR/LSL Jan Beulich
2023-07-14 10:02 ` [PATCH 2/2] x86: adjust disassembly of insns operating on selector values Jan Beulich
2023-07-17 2:04 ` Jiang, Haochen
2023-07-17 7:08 ` Jan Beulich
2023-07-21 1:20 ` 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=3f44f9a7-2f4c-d92d-ec19-5023f317357a@suse.com \
--to=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).