From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: [PULL 0/3] x86 and machine queue, 2019-12-20
Date: Fri, 20 Dec 2019 16:20:28 -0300 [thread overview]
Message-ID: <20191220192031.2226378-1-ehabkost@redhat.com> (raw)
The following changes since commit aceeaa69d28e6f08a24395d0aa6915b687d0a681:
Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2019-12-17' into staging (2019-12-17 15:55:20 +0000)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/x86-and-machine-pull-request
for you to fetch changes up to fcd3f2cc124600385dba46c69a80626985c15b50:
numa: properly check if numa is supported (2019-12-19 14:57:14 -0300)
----------------------------------------------------------------
x86 and machine queue, 2019-12-20
Bug fix:
* Resolve CPU models to v1 by default (Eduardo Habkost)
Cleanup:
* Remove incorrect numa_mem_supported checks (Igor Mammedov)
----------------------------------------------------------------
Eduardo Habkost (1):
i386: Resolve CPU models to v1 by default
Igor Mammedov (2):
numa: remove not needed check
numa: properly check if numa is supported
hw/arm/sbsa-ref.c | 1 -
hw/core/machine.c | 4 ++--
hw/core/numa.c | 7 +------
qemu-deprecated.texi | 8 ++++++++
target/i386/cpu.c | 8 +++++++-
5 files changed, 18 insertions(+), 10 deletions(-)
--
2.23.0
next reply other threads:[~2019-12-20 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 19:20 Eduardo Habkost [this message]
2019-12-20 19:20 ` [PULL 1/3] i386: Resolve CPU models to v1 by default Eduardo Habkost
2019-12-20 19:20 ` [PULL 2/3] numa: remove not needed check Eduardo Habkost
2019-12-20 19:20 ` [PULL 3/3] numa: properly check if numa is supported Eduardo Habkost
2020-01-06 14:51 ` [PULL 0/3] x86 and machine queue, 2019-12-20 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=20191220192031.2226378-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=mst@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).