From: Jan Kiszka <jan.kiszka@web.de>
To: Abel Gordon <ABELG@il.ibm.com>
Cc: sheng qiu <herbert1984106@gmail.com>, kvm <kvm@vger.kernel.org>,
Nadav Har'El <NYH@il.ibm.com>, Alex Landau <LALEX@il.ibm.com>,
Nadav Amit <nadav.amit@gmail.com>,
Dan Tsafrir <dan.tsafrir@gmail.com>,
Muli Ben-Yehuda <muli@cs.technion.ac.il>
Subject: Re: KVM handling external interrupts
Date: Thu, 07 Jun 2012 10:13:48 +0200 [thread overview]
Message-ID: <4FD062BC.5090703@web.de> (raw)
In-Reply-To: <OF0A8D80DC.FDEDAC2E-ONC2257A16.002A8BD4-C2257A16.002B31FA@il.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On 2012-06-07 09:51, Abel Gordon wrote:
>> 3> if we configure not exit on external interrupt by setting some
>> field in VMCS, what will happen during the physical interrupts? will
>> the CPU use the guest IDT for response interrupt? If so, can KVM
>> redirect the CPU to use another IDT for guest (assuming modifying the
>> IDTR)?
>
> Yes, that's exactly something we already did in a research project.
> You can read our paper published in ASPLOS 2012: ELI: Bare-metal
> performance for I/O virtualization
> (
> http://dl.acm.org/citation.cfm?id=2151020&dl=ACM&coll=DL&CFID=86701665&CFTOKEN=26302003
Interesting. Can you provide it publicly (or send a version privately)?
> )
>
> Note this is not so simple, there are many other issues you should
> consider.
Is it just complicated, not upstreamable, or are the unsolved issues
like security holes or the need to paravirtualize the guest?
I'm still hoping that Intel/AMD will finally enable this in hardware, at
least for MSIs. Providing direct injection for legacy line-base
interrupts is likely not worth the silicon and bits (would require some
hw-assisted IOAPIC instead of just a bit more APIC virtualization).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-06-07 8:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 0:12 KVM handling external interrupts sheng qiu
2012-06-07 7:51 ` Abel Gordon
2012-06-07 8:13 ` Jan Kiszka [this message]
2012-06-07 9:02 ` Jan Kiszka
2012-06-07 10:47 ` Abel Gordon
2012-06-07 10:51 ` Jan Kiszka
2012-06-07 11:05 ` Abel Gordon
2012-06-07 11:13 ` Jan Kiszka
2012-06-07 11:51 ` Abel Gordon
2012-06-07 11:54 ` Jan Kiszka
2012-06-07 12:02 ` Abel Gordon
2012-06-07 11:10 ` Jan Kiszka
2012-06-07 11:49 ` Abel Gordon
2012-06-07 12:11 ` Jan Kiszka
2012-06-07 12:25 ` Abel Gordon
2012-06-07 15:05 ` Jan Kiszka
2012-06-10 8:41 ` Abel Gordon
2012-06-10 10:16 ` Jan Kiszka
2012-06-10 10:43 ` Abel Gordon
2012-06-10 12:16 ` Jan Kiszka
2012-06-10 13:30 ` Abel Gordon
2012-06-07 9:55 ` Abel Gordon
2012-06-07 10:23 ` Jan Kiszka
2012-06-07 10:34 ` Nadav Har'El
2012-06-07 10:48 ` Jan Kiszka
2012-06-07 11:40 ` Jan Kiszka
2012-06-07 12:17 ` Abel Gordon
2012-06-07 12:19 ` Jan Kiszka
2012-06-07 12:32 ` Abel Gordon
2012-06-07 15:07 ` Jan Kiszka
2012-06-10 10:12 ` Abel Gordon
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=4FD062BC.5090703@web.de \
--to=jan.kiszka@web.de \
--cc=ABELG@il.ibm.com \
--cc=LALEX@il.ibm.com \
--cc=NYH@il.ibm.com \
--cc=dan.tsafrir@gmail.com \
--cc=herbert1984106@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=muli@cs.technion.ac.il \
--cc=nadav.amit@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox