All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brijesh Singh <brijesh.singh@amd.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: brijesh.singh@amd.com, Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Tom Lendacky <Thomas.Lendacky@amd.com>
Subject: Re: [Qemu-devel] [PATCH v3] target-i386/cpu: Add new EPYC CPU model
Date: Thu, 17 Aug 2017 13:37:51 -0500	[thread overview]
Message-ID: <2f426b2d-cea3-bed4-1966-6868d6e3bbfe@amd.com> (raw)
In-Reply-To: <276d5c64-7ef3-127b-b2f4-e5f7b3a5aab4@redhat.com>

Hi Paolo,

On 08/17/2017 11:45 AM, Paolo Bonzini wrote:
> On 15/08/2017 19:00, Brijesh Singh wrote:
>>
>> The following features bits have been added/removed compare to Opteron_G5
>>
>> Added: monitor, movbe, rdrand, mmxext, ffxsr, rdtscp, cr8legacy, osvw,
>>         fsgsbase, bmi1, avx2, smep, bmi2, rdseed, adx, smap, clfshopt, sha
>>         xsaveopt, xsavec, xgetbv1, arat
>>
>> Removed: xop, fma4, tbm
> 
> Interesting, why were these removed?
> 

I don't know exact reason why these were removed - I am going with whatever is
listed as supported feature bit in PPR [1], but I will ask around and let you
know. I believe some of these instruction are superseded with newer instructions
(e.g fma4->fma)

[1] http://support.amd.com/TechDocs/54945_PPR_Family_17h_Models_00h-0Fh.pdf


> Do we want to add "topoext" support too?  What about mwaitx?
> 

Looking at PPR I think we can safely enable "topoext" - it is listed as fixed to 1
but "mwaitx" support depends on the MSR condition. If host BIOS does not set the MSR
then we may not able to use "mwaitx" feature.

Actually, I was trying to ensure that in this patch I do not use a feature which is not
supported by KVM. Looking at kvm_cpuid_8000_0001_ecx_x86_features [2] hinted me that
both "topoext" and "mwaitx" was not supported hence I skipped it. I can add comment to
remind us.

http://elixir.free-electrons.com/linux/latest/source/arch/x86/kvm/cpuid.c#L360

-Brijesh

  reply	other threads:[~2017-08-17 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 17:00 [Qemu-devel] [PATCH v3] target-i386/cpu: Add new EPYC CPU model Brijesh Singh
2017-08-17  3:55 ` Wanpeng Li
2017-08-17 16:21   ` Brijesh Singh
2017-08-17 16:45 ` Paolo Bonzini
2017-08-17 18:37   ` Brijesh Singh [this message]
2017-08-21 11:52     ` Brijesh Singh
2017-08-22 14:44 ` Brijesh Singh
2017-08-22 15:49   ` Paolo Bonzini
2017-08-23 14:17     ` Eduardo Habkost
2018-06-27 14:48 ` [Qemu-devel] MSRC001_102C on EPYC (was Re: [PATCH v3] target-i386/cpu: Add new EPYC CPU model) Eduardo Habkost
2018-06-27 15:07   ` Paolo Bonzini
2018-06-27 15:09   ` Brijesh Singh

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=2f426b2d-cea3-bed4-1966-6868d6e3bbfe@amd.com \
    --to=brijesh.singh@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=ehabkost@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 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.