All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Eduardo Habkost" <ehabkost@redhat.com>,
	qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Bandan Das <bsd@redhat.com>,
	Anthony Liguori <aliguori@amazon.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/3] Enable x2apic by default on KVM
Date: Wed, 19 Feb 2014 16:24:33 +0100	[thread overview]
Message-ID: <5304CCB1.6000904@redhat.com> (raw)
In-Reply-To: <1392821892-26682-1-git-send-email-ehabkost@redhat.com>

Il 19/02/2014 15:58, Eduardo Habkost ha scritto:
> This is the approach I believe was agreed upon during the last QEMU developers
> conf call (sorry I didn't join, the meeting timezone change confused me).

Yes, that's correct.

> Some may notice that representing this new behavior using solely default values
> on CPU properties may be a little difficult. Making it possible to replace
> x86_cpu_compat_disable_kvm_features() with compat_props entries may be an
> interesting problem, too.

Very clean patches!

Paolo

  parent reply	other threads:[~2014-02-19 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 14:58 [Qemu-devel] [PATCH 0/3] Enable x2apic by default on KVM Eduardo Habkost
2014-02-19 14:58 ` [Qemu-devel] [PATCH 1/3] target-i386: Make kvm_default_features an array Eduardo Habkost
2014-02-19 16:38   ` Igor Mammedov
2014-02-19 16:43     ` Eduardo Habkost
2014-02-19 14:58 ` [Qemu-devel] [PATCH 2/3] target-i386: Introduce x86_cpu_compat_disable_kvm_features() Eduardo Habkost
2014-02-19 14:58 ` [Qemu-devel] [PATCH 3/3] target-i386: Enable x2apic by default on KVM Eduardo Habkost
2014-03-12 14:36   ` Andreas Färber
2014-03-12 15:42     ` Eduardo Habkost
2014-03-12 16:49       ` Andreas Färber
2014-02-19 15:24 ` Paolo Bonzini [this message]
2014-02-19 19:13 ` [Qemu-devel] [PATCH 0/3] " Michael S. Tsirkin
2014-03-03 16:30   ` Andreas Färber

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=5304CCB1.6000904@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=bsd@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@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.