From: Eduardo Habkost <ehabkost@redhat.com>
To: "Moger, Babu" <Babu.Moger@amd.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ani Sinha <ani.sinha@nutanix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Singh, Brijesh" <brijesh.singh@amd.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 10:52:50 -0500 [thread overview]
Message-ID: <20200206155250.GA25446@habkost.net> (raw)
In-Reply-To: <CY4PR12MB157489B70F2AD26C97779E40951D0@CY4PR12MB1574.namprd12.prod.outlook.com>
On Thu, Feb 06, 2020 at 12:00:04AM +0000, Moger, Babu wrote:
> [AMD Official Use Only - Internal Distribution Only]
Considering that this was posted to qemu-devel, I'm assuming this
notice was added by accident.
>
[...]
> Eduardo, I am still waiting for your feedback on this series.
> https://lore.kernel.org/qemu-devel/abd39b75-0a12-5198-5815-dd51a3d5c901@amd.com/
>
> I have added all the missing feature bits for EPYC models(as
> EPYC-v3) and also added EPYC-Rome model.
I'm still catching up on email and my review queue, but this is
on my list. Sorry for the long delay!
--
Eduardo
next prev parent reply other threads:[~2020-02-06 15:53 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
2020-02-06 16:03 ` Eduardo Habkost
2020-02-06 15:52 ` Eduardo Habkost [this message]
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=20200206155250.GA25446@habkost.net \
--to=ehabkost@redhat.com \
--cc=Babu.Moger@amd.com \
--cc=ani.sinha@nutanix.com \
--cc=brijesh.singh@amd.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.