qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>, Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH v2] i386: Introduce ARAT CPU feature
Date: Mon, 25 May 2015 16:16:14 +0200	[thread overview]
Message-ID: <55632EAE.9030508@redhat.com> (raw)
In-Reply-To: <55632C7A.8010107@web.de>



On 25/05/2015 16:06, Jan Kiszka wrote:
>  static void pc_compat_2_3(MachineState *machine)
>  {
> +    x86_cpu_compat_set_features("Westmere", FEAT_6_EAX, 0, CPUID_6_EAX_ARAT);
> +    x86_cpu_compat_set_features("SandyBridge", FEAT_6_EAX, 0,
> +                                CPUID_6_EAX_ARAT);
> +    x86_cpu_compat_set_features("IvyBridge", FEAT_6_EAX, 0, CPUID_6_EAX_ARAT);
> +    x86_cpu_compat_set_features("Haswell-noTSX", FEAT_6_EAX, 0,
> +                                CPUID_6_EAX_ARAT);
> +    x86_cpu_compat_set_features("Haswell", FEAT_6_EAX, 0, CPUID_6_EAX_ARAT);
> +    x86_cpu_compat_set_features("Broadwell-noTSC", FEAT_6_EAX, 0,
> +                                CPUID_6_EAX_ARAT);

noTSX.

Also, I think this doesn't cover Q35.  Eduardo has patches to clean that
up so that (I think) less duplication is required.

Paolo

> +    x86_cpu_compat_set_features("Broadwell", FEAT_6_EAX, 0, CPUID_6_EAX_ARAT);
>  }
>  

  reply	other threads:[~2015-05-25 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 15:16 [Qemu-devel] [PATCH] i386: Introduce ARAT CPU feature Jan Kiszka
2015-05-25 13:23 ` Paolo Bonzini
2015-05-25 14:06   ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2015-05-25 14:16     ` Paolo Bonzini [this message]
2015-05-25 18:03       ` Eduardo Habkost
     [not found]         ` <5563F821.7080202@web.de>
2015-05-26 17:18           ` [Qemu-devel] [PATCH v4] " Eduardo Habkost
2015-05-26 17:25             ` Eduardo Habkost

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=55632EAE.9030508@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --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 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).