From: Torbjorn Granlund <tg@gmplib.org>
To: Richard Henderson <rth@twiddle.net>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 3 new x86 instructions
Date: Mon, 14 Jan 2013 19:14:18 +0100 [thread overview]
Message-ID: <86mwwbr5s5.fsf@shell.gmplib.org> (raw)
In-Reply-To: <50F1B339.9010709@twiddle.net> (Richard Henderson's message of "Sat\, 12 Jan 2013 11\:02\:17 -0800")
Richard Henderson <rth@twiddle.net> writes:
> MULX implies a bunch of other instructions due to CPUID flag grouping.
> ADCX and ADOX can be implemented separately. None of these and the
> other instructions in the MULX group look very complex.
I've got a patch for (most of?) the bmi[12] insns:
git://repo.or.cz/qemu/rth.git x86-next
This includes general support for the VEX prefixes.
Nice!
Is it in such a state that grabbing that repo and building a
qemu-system-x86_64 would give me MULX support?
I realise things might not be as stable as a release, but I can deal
with that.
But before I did anything else for the adx extension,
I thought I'd have a look back at Paolo's eflags optimization
patch series that he posted in October. Otherwise we'll
not be able to get really good emulation of these insns.
I see. ADCX and ADOX are several years away, IIUC.
--
Torbjörn
next prev parent reply other threads:[~2013-01-14 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 13:46 [Qemu-devel] 3 new x86 instructions Torbjorn Granlund
2013-01-12 11:40 ` Blue Swirl
2013-01-12 15:09 ` Torbjorn Granlund
2013-01-12 19:02 ` Richard Henderson
2013-01-14 18:14 ` Torbjorn Granlund [this message]
2013-01-14 18:46 ` Richard Henderson
2013-01-15 17:14 ` Torbjorn Granlund
2013-01-15 17:17 ` Richard Henderson
2013-01-16 20:38 ` Torbjorn Granlund
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=86mwwbr5s5.fsf@shell.gmplib.org \
--to=tg@gmplib.org \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 NNTP newsgroup(s).