From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Jacob Pan <jacob.jun.pan@intel.com>,
Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
gleb@redhat.com
Subject: Re: [PATCH 0/3] make KVM PV use apic through APIs
Date: Sun, 15 Jul 2012 16:06:04 +0300 [thread overview]
Message-ID: <5002C03C.2030304@redhat.com> (raw)
In-Reply-To: <cover.1342356186.git.mst@redhat.com>
On 07/15/2012 03:56 PM, Michael S. Tsirkin wrote:
> KVM PV EOI optimization overrides eoi_write apic op with its own
> version. at Ingo's suggestion, add an API for this and switch kvm to use
> it, to avoid meddling with core x86 apic driver data structures
> directly.
>
> Ingo, could you please review and let us know whether this
> matches what you had in mind?
>
> This patchset is on top of kvm/next since it touches some
> of the code modified in that tree (and patch 3 reverts a commit
> in that tree). Could x86 some maintainers pls ACK merging this patchset
> through the kvm tree?
>
Looks okay to me.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-15 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 12:56 [PATCH 0/3] make KVM PV use apic through APIs Michael S. Tsirkin
2012-07-15 12:56 ` [PATCH 1/3] apic: add apic_set_eoi_write for PV use Michael S. Tsirkin
2012-07-16 9:25 ` Ingo Molnar
2012-07-15 12:56 ` [PATCH 2/3] kvm: switch to apic_set_eoi_write, apic_write Michael S. Tsirkin
2012-07-15 12:56 ` [PATCH 3/3] Revert "apic: fix kvm build on UP without IOAPIC" Michael S. Tsirkin
2012-07-15 13:06 ` Avi Kivity [this message]
2012-07-16 9:52 ` [PATCH 0/3] make KVM PV use apic through APIs Avi Kivity
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=5002C03C.2030304@redhat.com \
--to=avi@redhat.com \
--cc=fernando@oss.ntt.co.jp \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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).