qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 16:56:47 +0100	[thread overview]
Message-ID: <4F4F9C3F.5020201@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203011446190.923@kaball-desktop>

Il 01/03/2012 15:50, Stefano Stabellini ha scritto:
>>> > > 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.
>  
> Because msi(x)_notify is called by QEMU's emulated devices: it is not
> possible from QEMU to cause an emulation trap in Xen on behalf of the
> guest.

msi{x,}_notify doesn't have to go to Xen MMIO emulation, so in Wei's
patch you don't need anymore the msi{,x}_notify parts, only apic_send_msi.

But you could take it further and create a separate subclass of
apic-common that does absolutely nothing except register an MMIO memory
region and use it to trap MSI writes.  Basically an even more stripped
down version than hw/kvm/apic.c, but using memory_region_init_io rather
than memory_region_init_reservation.  You would also get support for the
monitor command inject-nmi (there is another hypercall for that in Xen
IIRC).

Paolo

  reply	other threads:[~2012-03-01 15:57 UTC|newest]

Thread overview: 14+ 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:47 ` Jan Kiszka
2012-03-01 10:20   ` Wei Liu
2012-03-01 11:22     ` Jan Kiszka
2012-03-01 11:51       ` Wei Liu
2012-03-01 12:56         ` Paolo Bonzini
2012-03-01 14:06           ` Stefano Stabellini
2012-03-01 14:03             ` Paolo Bonzini
2012-03-01 14:50               ` Stefano Stabellini
2012-03-01 15:56                 ` Paolo Bonzini [this message]
2012-03-01 16:06                   ` Stefano Stabellini
2012-04-03 16:44                   ` Wei Liu
2012-04-03 16:52                     ` Jan Kiszka
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=4F4F9C3F.5020201@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).