From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] MSI / MSIX injection for Xen HVM
Date: Thu, 01 Mar 2012 12:22:29 +0100 [thread overview]
Message-ID: <4F4F5BF5.6010206@siemens.com> (raw)
In-Reply-To: <1330597236.10387.70.camel@leeds.uk.xensource.com>
On 2012-03-01 11:20, Wei Liu wrote:
>> However, you know that you miss those (uncommon) messages that are
>> injected via DMA? They end up directly in apic_deliver_msi (where KVM
>> will once pick them up as well).
>>
>
> Thanks for pointing this out. However I cannot find apic_deliver_msi in
> qemu-kvm or upstream qemu tree. I can only find apic_send_msi and
> apic_deliver_irq, none of which seems to be KVM-specific. Can you please
> give me some pointer on this?
Yes, apic_send_msi. I was accidentally looking at my msi refactoring tree.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] MSI / MSIX injection for Xen HVM
Date: Thu, 01 Mar 2012 12:22:29 +0100 [thread overview]
Message-ID: <4F4F5BF5.6010206@siemens.com> (raw)
In-Reply-To: <1330597236.10387.70.camel@leeds.uk.xensource.com>
On 2012-03-01 11:20, Wei Liu wrote:
>> However, you know that you miss those (uncommon) messages that are
>> injected via DMA? They end up directly in apic_deliver_msi (where KVM
>> will once pick them up as well).
>>
>
> Thanks for pointing this out. However I cannot find apic_deliver_msi in
> qemu-kvm or upstream qemu tree. I can only find apic_send_msi and
> apic_deliver_irq, none of which seems to be KVM-specific. Can you please
> give me some pointer on this?
Yes, apic_send_msi. I was accidentally looking at my msi refactoring tree.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-03-01 11:23 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 ` Jan Kiszka [this message]
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 ` [Qemu-devel] " Paolo Bonzini
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=4F4F5BF5.6010206@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--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.