From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Wei Liu (Intern)" <wei.liu2@citrix.com>,
QEMU-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] MSI / MSIX injection for Xen HVM
Date: Thu, 01 Mar 2012 15:03:26 +0100 [thread overview]
Message-ID: <4F4F81AE.9080503@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203011403140.923@kaball-desktop>
Il 01/03/2012 15:06, Stefano Stabellini ha scritto:
>> > This is not a NACK, but I can't help asking. Perhaps the fake Xen
>> > interrupt controller is a bit too simplistic? You can add a memory
>> > region corresponding to the APICs and trap writes in that region.
>> > Writes coming from QEMU are MSIs and can be injected to the hypervisor,
>> > writes coming from the VM will be trapped by Xen before going out to QEMU.
>
> That is a good point actually: we already have lapic emulation in Xen,
> it makes sense to have apic-msi in Xen too.
> We would still need the changes to msi_notify and msix_notify though.
Why? The stores would just go to the Xen interrupt controller MMIO area
which then does the xc_hvm_inject_msi.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Wei Liu (Intern)" <wei.liu2@citrix.com>,
QEMU-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] MSI / MSIX injection for Xen HVM
Date: Thu, 01 Mar 2012 15:03:26 +0100 [thread overview]
Message-ID: <4F4F81AE.9080503@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203011403140.923@kaball-desktop>
Il 01/03/2012 15:06, Stefano Stabellini ha scritto:
>> > This is not a NACK, but I can't help asking. Perhaps the fake Xen
>> > interrupt controller is a bit too simplistic? You can add a memory
>> > region corresponding to the APICs and trap writes in that region.
>> > Writes coming from QEMU are MSIs and can be injected to the hypervisor,
>> > writes coming from the VM will be trapped by Xen before going out to QEMU.
>
> That is a good point actually: we already have lapic emulation in Xen,
> it makes sense to have apic-msi in Xen too.
> We would still need the changes to msi_notify and msix_notify though.
Why? The stores would just go to the Xen interrupt controller MMIO area
which then does the xc_hvm_inject_msi.
Paolo
next prev parent reply other threads:[~2012-03-01 14:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:21 [Qemu-devel] [PATCH] MSI / MSIX injection for Xen HVM Wei Liu
2012-02-29 17:21 ` Wei Liu
2012-02-29 17:47 ` [Qemu-devel] " Jan Kiszka
2012-02-29 17:47 ` Jan Kiszka
2012-03-01 10:20 ` [Qemu-devel] " Wei Liu
2012-03-01 10:20 ` Wei Liu
2012-03-01 11:22 ` [Qemu-devel] " Jan Kiszka
2012-03-01 11:22 ` Jan Kiszka
2012-03-01 11:51 ` [Qemu-devel] " Wei Liu
2012-03-01 11:51 ` Wei Liu
2012-03-01 12:56 ` [Qemu-devel] " Paolo Bonzini
2012-03-01 12:56 ` Paolo Bonzini
2012-03-01 14:06 ` [Qemu-devel] " Stefano Stabellini
2012-03-01 14:06 ` Stefano Stabellini
2012-03-01 14:03 ` Paolo Bonzini [this message]
2012-03-01 14:03 ` Paolo Bonzini
2012-03-01 14:50 ` [Qemu-devel] " Stefano Stabellini
2012-03-01 14:50 ` Stefano Stabellini
2012-03-01 15:56 ` [Qemu-devel] " Paolo Bonzini
2012-03-01 15:56 ` Paolo Bonzini
2012-03-01 16:06 ` [Qemu-devel] " Stefano Stabellini
2012-03-01 16:06 ` Stefano Stabellini
2012-04-03 16:44 ` [Qemu-devel] " Wei Liu
2012-04-03 16:44 ` Wei Liu
2012-04-03 16:52 ` [Qemu-devel] " Jan Kiszka
2012-04-03 16:52 ` Jan Kiszka
2012-04-04 13:40 ` [Qemu-devel] " Stefano Stabellini
2012-04-04 13:40 ` Stefano Stabellini
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=4F4F81AE.9080503@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.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.