From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: libvir-list@redhat.com, donald.d.dugger@intel.com,
jun.nakajima@intel.com, Paolo Bonzini <pbonzini@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] target-i386: Haswell-noTSX and Broadwell-noTSX CPU models
Date: Fri, 13 Mar 2015 20:25:19 +0100 [thread overview]
Message-ID: <5503399F.5040307@suse.de> (raw)
In-Reply-To: <1426273797-11204-1-git-send-email-ehabkost@redhat.com>
Am 13.03.2015 um 20:09 schrieb Eduardo Habkost:
> With the Intel microcode update that removed HLE and RTM, there will be
> different kinds of Haswell and Broadwell CPUs out there: some that still
> have the HLE and RTM features, and some that don't have the HLE and RTM
> features. On both cases people may be willing to use the pc-*-2.3
> machine-types.
>
> So instead of making the CPU model results confusing by making it depend on the
> machine-type, keep HLE and RTM on the existing Haswell and Broadwell CPU
> models, and introduce "Haswell-noTSX" and "Broadwell-noTSX" CPU models later,
> for people who have CPUs that don't have TSX feature available.
>
> Eduardo Habkost (2):
> Revert "target-i386: Disable HLE and RTM on Haswell & Broadwell"
> target-i386: Haswell-noTSX and Broadwell-noTSX
No objections from a generic CPU point of view.
Only thing that comes to mind is whether it might make sense to
hierarchically make Broadwell the parent type of Broadwell-noTSX, to
avoid duplication. But then again we already have a lot of it. ;)
Regards,
Andreas
> hw/i386/pc_piix.c | 4 ---
> hw/i386/pc_q35.c | 4 ---
> target-i386/cpu.c | 74 +++++++++++++++++++++++++++++++++++++++++++++++++++++--
> 3 files changed, 72 insertions(+), 10 deletions(-)
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-03-13 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 19:09 [Qemu-devel] [PATCH 0/2] target-i386: Haswell-noTSX and Broadwell-noTSX CPU models Eduardo Habkost
2015-03-13 19:09 ` [Qemu-devel] [PATCH 1/2] Revert "target-i386: Disable HLE and RTM on Haswell & Broadwell" Eduardo Habkost
2015-03-16 10:18 ` Daniel P. Berrange
2015-03-13 19:09 ` [Qemu-devel] [PATCH 2/2] target-i386: Haswell-noTSX and Broadwell-noTSX Eduardo Habkost
2015-03-16 10:24 ` Daniel P. Berrange
2015-03-19 18:02 ` Eduardo Habkost
2015-03-19 18:14 ` Daniel P. Berrange
2015-03-13 19:25 ` Andreas Färber [this message]
2015-03-13 19:45 ` [Qemu-devel] [PATCH 0/2] target-i386: Haswell-noTSX and Broadwell-noTSX CPU models Eduardo Habkost
2015-03-14 11:42 ` Andreas Färber
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=5503399F.5040307@suse.de \
--to=afaerber@suse.de \
--cc=donald.d.dugger@intel.com \
--cc=ehabkost@redhat.com \
--cc=jdenemar@redhat.com \
--cc=jun.nakajima@intel.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.