From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
Babu Moger <babu.moger@amd.com>
Subject: [Qemu-devel] [PATCH 0/2] i386: Introduce X86CPUCacheCPUID struct
Date: Thu, 20 Jun 2019 17:36:14 -0300 [thread overview]
Message-ID: <20190620203616.22715-1-ehabkost@redhat.com> (raw)
The new struct will let us declare the existing legacy CPU
topology info in a static constant, instead of defining it inside
x86_cpu_realizefn(). While doing it, make the CPU cache
declarations all constants.
This will help us represent the model-specific cache info as QOM
properties in the future. Currently X86CPUDefinition::cache_info
(which is being renamed to X86CPUDefinition::cache_cpuid) is the
only CPU model field that can't be represented as a QOM property
value.
Eduardo Habkost (2):
i386: make cache structs const-safe
i386: Introduce X86CPUCacheCPUID struct
target/i386/cpu.h | 15 +++---
target/i386/cpu.c | 134 +++++++++++++++++++++++++++-------------------
2 files changed, 84 insertions(+), 65 deletions(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2019-06-20 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 20:36 Eduardo Habkost [this message]
2019-06-20 20:36 ` [Qemu-devel] [PATCH 1/2] i386: make cache structs const-safe Eduardo Habkost
2019-06-20 20:36 ` [Qemu-devel] [PATCH 2/2] i386: Introduce X86CPUCacheCPUID struct Eduardo Habkost
2019-06-20 21:31 ` [Qemu-devel] [PATCH 0/2] " no-reply
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=20190620203616.22715-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=babu.moger@amd.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.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).