From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PULL 0/3] x86 queue, 2019-06-11
Date: Tue, 11 Jun 2019 10:42:21 -0300 [thread overview]
Message-ID: <20190611134224.6683-1-ehabkost@redhat.com> (raw)
The following changes since commit a578cdfbdd8f9beff5ced52b7826ddb1669abbbf:
Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20190610' into staging (2019-06-10 16:09:19 +0100)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/x86-next-pull-request
for you to fetch changes up to 89a44a103315267122119b4311218d00d2561ebe:
i386: Save EFER for 32-bit targets (2019-06-11 10:17:47 -0300)
----------------------------------------------------------------
x86 queue, 2019-06-11
* "unavailable-features" QOM property (Eduardo Habkost)
* Save EFER for 32-bit targets (Pavel Dovgalyuk)
----------------------------------------------------------------
Eduardo Habkost (2):
i386: x86_cpu_list_feature_names() function
i386: "unavailable-features" QOM property
Pavel Dovgalyuk (1):
i386: Save EFER for 32-bit targets
target/i386/cpu.c | 55 +++++++++++++++++++++++++++++++++----------
target/i386/machine.c | 24 +++++++++++++++++++
2 files changed, 66 insertions(+), 13 deletions(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2019-06-11 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 13:42 Eduardo Habkost [this message]
2019-06-11 13:42 ` [Qemu-devel] [PULL 1/3] i386: x86_cpu_list_feature_names() function Eduardo Habkost
2019-06-11 13:42 ` [Qemu-devel] [PULL 2/3] i386: "unavailable-features" QOM property Eduardo Habkost
2019-06-11 13:42 ` [Qemu-devel] [PULL 3/3] i386: Save EFER for 32-bit targets Eduardo Habkost
2019-06-11 15:40 ` [Qemu-devel] [PULL 0/3] x86 queue, 2019-06-11 Peter Maydell
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=20190611134224.6683-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).