public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Abel Gordon <ABELG@il.ibm.com>
Cc: Alex Landau <LALEX@il.ibm.com>,
	Dan Tsafrir <dan.tsafrir@gmail.com>,
	sheng qiu <herbert1984106@gmail.com>, kvm <kvm@vger.kernel.org>,
	Muli Ben-Yehuda <muli@cs.technion.ac.il>,
	Nadav Har'El <NYH@il.ibm.com>, Nadav Amit <nadav.amit@gmail.com>
Subject: Re: KVM handling external interrupts
Date: Thu, 07 Jun 2012 13:54:35 +0200	[thread overview]
Message-ID: <4FD0967B.70807@web.de> (raw)
In-Reply-To: <OFF0FD23FE.90216742-ONC2257A16.0040FFB3-C2257A16.00412E3F@il.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]

On 2012-06-07 13:51, Abel Gordon wrote:
> 
> 
> Jan Kiszka <jan.kiszka@web.de> wrote on 07/06/2012 14:13:45:
> 
>>> Well, the shadow IDT only needs to be synced with interrupts coming
> from
>>> assigned devices. The rest of the entries doesn't matter, they just
>>> generate an exception. Once they generate an exception, they are
> delivered
>>> through the host IDT. So, all you need to know are the vectors assigned
>>> to the guest to build the shadow IDT.
>>
>> Not totally true. If the host decides to allocate some new vector that
>> collides with some guest usage, you need to rearrange the shadow IDT and
>> the physical IRQ routing. So you need to track what the host does.
> 
> Well, depends if you re-allocate the vector used by the guest or the vector
> used by the host. Anyway, I think we understand each other :)

KVM is just a subsystem of the Linux kernel, usually not involved in
LAPIC vector allocations. Your suggestion would turn this around a bit.
Not impossible, but expect some discussions. ;)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-06-07 11:54 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
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 [this message]
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=4FD0967B.70807@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