From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Richard Henderson <rth@twiddle.net>
Subject: [PULL 0/9] x86 queue for -rc2
Date: Thu, 2 Apr 2020 19:20:42 -0300 [thread overview]
Message-ID: <20200402222051.523093-1-ehabkost@redhat.com> (raw)
This was supposed to be submitted before -rc1, but I've dropped
the ball (sorry).
The following changes since commit 2833ad487cfff7dc33703e4731b75facde1c561e:
Update version for v5.0.0-rc1 release (2020-03-31 18:02:47 +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 d965dc35592d24c0c1519f1c566223c6277cb80e:
target/i386: Add ARCH_CAPABILITIES related bits into Icelake-Server CPU model (2020-03-31 19:13:32 -0300)
----------------------------------------------------------------
x86 queue for -rc2
Fixes:
* EPYC CPU model APIC ID topology fixes (Babu Moger)
* Fix crash when enabling intel-pt on older machine types
(Luwei Kang)
* Add missing ARCH_CAPABILITIES bits to Icelake-Server CPU model
(Xiaoyao Li)
----------------------------------------------------------------
Babu Moger (7):
hw/386: Add EPYC mode topology decoding functions
target/i386: Cleanup and use the EPYC mode topology functions
hw/i386: Introduce apicid functions inside X86MachineState
i386: Introduce use_epyc_apic_id_encoding in X86CPUDefinition
hw/i386: Move arch_id decode inside x86_cpus_init
target/i386: Enable new apic id encoding for EPYC based cpus models
i386: Fix pkg_id offset for EPYC cpu models
Luwei Kang (1):
target/i386: set the CPUID level to 0x14 on old machine-type
Xiaoyao Li (1):
target/i386: Add ARCH_CAPABILITIES related bits into Icelake-Server
CPU model
hw/i386/pc.c | 7 +-
hw/i386/x86.c | 42 ++++++--
include/hw/i386/topology.h | 100 ++++++++++++++++++
include/hw/i386/x86.h | 9 ++
target/i386/cpu.c | 207 ++++++++++++++-----------------------
target/i386/cpu.h | 2 +
6 files changed, 225 insertions(+), 142 deletions(-)
--
2.24.1
next reply other threads:[~2020-04-02 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 22:20 Eduardo Habkost [this message]
2020-04-02 22:20 ` [PULL 1/9] hw/386: Add EPYC mode topology decoding functions Eduardo Habkost
2020-04-02 22:20 ` [PULL 2/9] target/i386: Cleanup and use the EPYC mode topology functions Eduardo Habkost
2020-04-02 22:20 ` [PULL 3/9] hw/i386: Introduce apicid functions inside X86MachineState Eduardo Habkost
2020-04-02 22:20 ` [PULL 4/9] i386: Introduce use_epyc_apic_id_encoding in X86CPUDefinition Eduardo Habkost
2020-04-02 22:20 ` [PULL 5/9] hw/i386: Move arch_id decode inside x86_cpus_init Eduardo Habkost
2020-04-02 22:20 ` [PULL 6/9] target/i386: Enable new apic id encoding for EPYC based cpus models Eduardo Habkost
2020-04-02 22:20 ` [PULL 7/9] i386: Fix pkg_id offset for EPYC cpu models Eduardo Habkost
2020-04-02 22:20 ` [PULL 8/9] target/i386: set the CPUID level to 0x14 on old machine-type Eduardo Habkost
2020-04-02 22:20 ` [PULL 9/9] target/i386: Add ARCH_CAPABILITIES related bits into Icelake-Server CPU model Eduardo Habkost
2020-04-03 11:59 ` [PULL 0/9] x86 queue for -rc2 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=20200402222051.523093-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).