qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Babu Moger <babu.moger@amd.com>
To: Ani Sinha <ani.sinha@nutanix.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Singh, Brijesh" <brijesh.singh@amd.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [PATCH] i386: pass CLZERO to guests with EPYC CPU model on AMD ZEN platform
Date: Thu, 6 Feb 2020 09:30:11 -0600	[thread overview]
Message-ID: <78f5dad9-5433-3f7c-69cb-db496b1c37a7@amd.com> (raw)
In-Reply-To: <60B21C9A-30BE-4DC0-8A1B-0BC7757BA9D7@nutanix.com>



On 2/5/20 11:53 PM, Ani Sinha wrote:
> 
> 
>> On Feb 6, 2020, at 11:16 AM, Ani Sinha <ani.sinha@nutanix.com> wrote:
>>
>>
>>
>>> On Feb 6, 2020, at 5:30 AM, Moger, Babu <Babu.Moger@amd.com> wrote:
>>>
>>> Ani, I am already working on it.
>>
>> Wow, I see a whole new AMD-Rome CPU model with it’s own cache info data : 
>>
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fqemu-devel%2F157314966312.23828.17684821666338093910.stgit%40naples-babu.amd.com%2F&amp;data=02%7C01%7CBabu.Moger%40amd.com%7Cc566dc5cf3cc407b5ee608d7aac8d9bc%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637165651955089264&amp;sdata=tlafWD6m5%2BZ12cqd4vqJcWh0%2FIgly%2FPVMgAbjxK5Mog%3D&amp;reserved=0
> 
> Do you think the ROME specific guest cpu cache data will have significant impact on performance?

I have not done performance benchmarks myself. Yes. Rome is expected to
perform better than its previous generations.



  reply	other threads:[~2020-02-06 15:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18  9:05 [PATCH] i386: pass CLZERO to guests with EPYC CPU model on AMD ZEN platform Ani Sinha
2019-12-18 11:53 ` Paolo Bonzini
2019-12-18 15:11   ` Eduardo Habkost
2020-01-20 10:56     ` Ani Sinha
2020-02-05 22:37       ` Eduardo Habkost
2020-02-06  0:00         ` Moger, Babu
2020-02-06  5:46           ` Ani Sinha
2020-02-06  5:53             ` Ani Sinha
2020-02-06 15:30               ` Babu Moger [this message]
2020-02-06 16:03                 ` Eduardo Habkost
2020-02-06 15:52           ` Eduardo Habkost
2020-02-06 15:55             ` Babu Moger
2019-12-22  7:32   ` Ani Sinha
2019-12-22  8:15     ` Paolo Bonzini
2019-12-23  8:14       ` Ani Sinha
2019-12-23  8:50         ` Ani Sinha
     [not found] <yes>
2019-12-04  9:36 ` Ani Sinha
2019-12-16  9:31   ` Ani Sinha

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=78f5dad9-5433-3f7c-69cb-db496b1c37a7@amd.com \
    --to=babu.moger@amd.com \
    --cc=ani.sinha@nutanix.com \
    --cc=brijesh.singh@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 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).