From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/1] x2apic implementation for kvm
Date: Mon, 25 May 2009 12:22:34 +0300 [thread overview]
Message-ID: <4A1A635A.1000000@redhat.com> (raw)
In-Reply-To: <200905251719.16009.sheng@linux.intel.com>
Sheng Yang wrote:
> I think that means the PV interface for lapic. And yes, we can support it
> follow MS's interface, but x2apic still seems another story as you noted... I
> still don't think support x2apic here would bring us more benefits.
>
x2apic has the following benefit:
- msr exits are faster than mmio (no page table walk, emulation)
- no need to read back ICR to look at the busy bit
- one ICR write instead of two
- potential to support large guests once we add interrupt remapping
- shared code with the Hyper-V paravirt interface
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-25 9:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 17:37 [PATCH 0/1] x2apic implementation for kvm Gleb Natapov
2009-05-21 17:37 ` [PATCH 1/1] x2apic interface to lapic Gleb Natapov
2009-05-31 12:44 ` Avi Kivity
2009-05-21 17:37 ` [PATCH 2/2] Advertise X2APIC support Gleb Natapov
2009-05-24 6:46 ` Dor Laor
2009-05-24 6:48 ` Gleb Natapov
2009-06-08 12:13 ` Avi Kivity
2009-05-25 6:08 ` [PATCH 0/1] x2apic implementation for kvm Sheng Yang
2009-05-25 6:13 ` Gleb Natapov
2009-05-25 6:30 ` Sheng Yang
2009-05-25 6:38 ` Gleb Natapov
2009-05-25 6:48 ` Sheng Yang
2009-05-25 6:57 ` Gleb Natapov
2009-05-25 9:07 ` Avi Kivity
2009-05-25 9:19 ` Sheng Yang
2009-05-25 9:22 ` Avi Kivity [this message]
2009-05-25 9:40 ` Dong, Eddie
2009-05-25 9:50 ` Avi Kivity
2009-05-25 9:59 ` Sheng Yang
2009-05-25 10:49 ` 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=4A1A635A.1000000@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=sheng@linux.intel.com \
/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.