From: "Richard W.M. Jones" <rjones@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
David Hildenbrand <david@redhat.com>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
Igor Mammedov <imammedo@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] i386: Add "max" CPU model to TCG and KVM
Date: Fri, 24 Feb 2017 13:43:45 +0000 [thread overview]
Message-ID: <20170224134345.GE13825@redhat.com> (raw)
In-Reply-To: <20170224122630.GQ2778@thinpad.lan.raisama.net>
On Fri, Feb 24, 2017 at 09:26:30AM -0300, Eduardo Habkost wrote:
> On Thu, Feb 23, 2017 at 09:57:41PM +0000, Richard W.M. Jones wrote:
> > On Thu, Feb 23, 2017 at 05:07:47PM -0300, Eduardo Habkost wrote:
> > > Ping?
> > >
> > > As v1 was sitting on the list since Jan 19, if there are no
> > > objections I will merge this and include in my next pull request
> > > before soft freeze.
> >
> > Do you have a copy which applies on top of current HEAD? I get
> > loads of conflicts.
>
> It is based on my x86-next branch. See cover letter for git URLs:
>
> ] * Rebased on top of my x86-next branch:
> ] https://github.com/ehabkost/qemu x86-next
> ]
> ] Git branch for testing:
> ] https://github.com/ehabkost/qemu-hacks work/x86-cpu-max-tcg
OK I've tried it now, and it works in both TCG and KVM cases.
If you want you can add:
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Thanks,
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
next prev parent reply other threads:[~2017-02-24 13:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 18:39 [Qemu-devel] [PATCH v2 0/3] i386: Add "max" CPU model to TCG and KVM Eduardo Habkost
2017-02-22 18:39 ` [Qemu-devel] [PATCH v2 1/3] i386: Create "max" CPU model Eduardo Habkost
2017-02-22 18:39 ` [Qemu-devel] [PATCH v2 2/3] i386: Make "max" model not use any host CPUID info on TCG Eduardo Habkost
2017-02-24 11:09 ` David Hildenbrand
2017-02-24 12:32 ` Eduardo Habkost
2017-02-24 12:34 ` David Hildenbrand
2017-02-24 13:44 ` Eduardo Habkost
2017-02-22 18:39 ` [Qemu-devel] [PATCH v2 3/3] i386: Don't set CPUClass::cpu_def on "max" model Eduardo Habkost
2017-02-24 11:13 ` David Hildenbrand
2017-02-24 12:33 ` Eduardo Habkost
2017-02-23 20:07 ` [Qemu-devel] [PATCH v2 0/3] i386: Add "max" CPU model to TCG and KVM Eduardo Habkost
2017-02-23 21:57 ` Richard W.M. Jones
2017-02-24 12:26 ` Eduardo Habkost
2017-02-24 13:43 ` Richard W.M. Jones [this message]
2017-02-24 13:48 ` Peter Maydell
2017-02-24 16:23 ` David Hildenbrand
2017-02-24 17:11 ` Eduardo Habkost
2017-02-24 18:04 ` Peter Maydell
2017-09-07 17:29 ` Peter Maydell
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=20170224134345.GE13825@redhat.com \
--to=rjones@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=david@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jdenemar@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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.