From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Brijesh Singh <brijesh.singh@amd.com>,
qemu-devel@nongnu.org, Tom Lendacky <Thomas.Lendacky@amd.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3] target-i386/cpu: Add new EPYC CPU model
Date: Wed, 23 Aug 2017 11:17:16 -0300 [thread overview]
Message-ID: <20170823141716.GG27715@localhost.localdomain> (raw)
In-Reply-To: <f2a991e0-6006-e839-f6c8-090be9877037@redhat.com>
On Tue, Aug 22, 2017 at 05:49:30PM +0200, Paolo Bonzini wrote:
> On 22/08/2017 16:44, Brijesh Singh wrote:
> > Hi Eduardo and Paolo,
> >
> > Please let me know if want me to address something else in this patch.
> >
> > After this patch is accepted, I am planning to submit similar patch to
> > to libvirt to create EPYC CPU.
>
> It looks good to me, but Eduardo is the maintainer and may spot
> something missing. :)
>
> QEMU is now in freeze, but the patch can easily go in at the beginning
> of 2.11.
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
I'm queueing it for 2.11 on my x86-next branch.
--
Eduardo
next prev parent reply other threads:[~2017-08-23 14:17 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
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 [this message]
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=20170823141716.GG27715@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=Thomas.Lendacky@amd.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.