From: Gregory Haskins <gregory.haskins@gmail.com>
To: "Jayaraman, Bhaskar" <Bhaskar.Jayaraman@lsi.com>
Cc: "Kumar, Venkat" <Venkat.Kumar@lsi.com>,
Cam Macdonell <cam@cs.ualberta.ca>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] Shared memory device with interrupt support
Date: Tue, 19 May 2009 07:35:44 -0400 [thread overview]
Message-ID: <4A129990.80603@gmail.com> (raw)
In-Reply-To: <F4789BF54654AC44982AC0ED2DE2E64B2CD1FC8D47@inbmail01.lsi.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
Jayaraman, Bhaskar wrote:
> Cam, is it somehow possible to generate a local APIC interrupt from one VM to another? I guess it shouldn't be as the LAPIC interrupts generated in one VM will go to the VCPUs of the same VM...
> Regards,
> Bhaskar.
>
The closest thing to this is the irqfd+iosignalfd thing I mentioned the
other day. With this model, a PIO/MMIO write in the src guest will
directly inject an interrupt into the dst guest's LAPIC. However, as
Avi points out, this is just an optimization. You can also do it by
first taking a hop through each guests userspace as well.
HTH
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
next prev parent reply other threads:[~2009-05-19 11:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D9CB4061D1EB3408D4A0B910433453C030BCA8892@inbmail01.lsi.com>
2009-05-16 3:30 ` [PATCH v2] Shared memory device with interrupt support Cam Macdonell
2009-05-17 21:51 ` Avi Kivity
2009-05-18 11:12 ` Gregory Haskins
2009-05-18 11:38 ` Avi Kivity
2009-05-18 16:50 ` Cam Macdonell
2009-05-18 17:19 ` Avi Kivity
2009-05-18 12:11 ` Kumar, Venkat
2009-05-18 16:20 ` Cam Macdonell
2009-05-19 3:52 ` Kumar, Venkat
2009-05-19 11:20 ` Jayaraman, Bhaskar
2009-05-19 11:35 ` Gregory Haskins [this message]
2009-05-07 16:16 Cam Macdonell
2009-05-16 2:45 ` Kumar, Venkat
2009-05-16 3:27 ` Cam Macdonell
2009-05-17 21:39 ` Avi Kivity
2009-05-18 18:54 ` Anthony Liguori
2009-05-19 4:31 ` Avi Kivity
2009-05-19 18:31 ` Anthony Liguori
2009-05-20 9:01 ` Avi Kivity
2009-05-20 13:45 ` Anthony Liguori
2009-05-20 14:26 ` 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=4A129990.80603@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=Bhaskar.Jayaraman@lsi.com \
--cc=Venkat.Kumar@lsi.com \
--cc=cam@cs.ualberta.ca \
--cc=kvm@vger.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 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.