From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, jasowang@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 2/2] pci: add PCIIOMMUOps and PCIIOMMUIntRemapFunc
Date: Wed, 17 Feb 2016 20:46:18 +0100 [thread overview]
Message-ID: <56C4CE0A.4070501@redhat.com> (raw)
In-Reply-To: <1455704742-21171-3-git-send-email-peterx@redhat.com>
On 17/02/2016 11:25, Peter Xu wrote:
> This patch extended the current PCI IOMMU functions into operation list,
> one new op is added to do interrupt remapping.
>
> Currently it is not working since int_remap is always NULL. It only
> provide a interface to extend PCI MSI to support interrupt remapping in
> the future.
>
> One helper function pci_setup_iommu_ops() is introduced. We can use this
> instead of the origin pci_setup_iommu() one to extend interrupt
> remapping on specific platform.
For MSI, I think interrupt remapping can be done directly in the IOMMU
MemoryRegion. You can just overlay a new MemoryRegion on top of the
IOMMU region where MSIs are sent (that's around 0xFEE00000, I don't
remember where exactly). It will catch interrupts sent by the device,
remap them and forward them to the right interrupt destination in the host.
I'm not sure about INTX interrupts, but I think that the host kernel
remaps them simply by virtualizing the IOAPIC's redirection table.
Paolo
next prev parent reply other threads:[~2016-02-17 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 10:25 [Qemu-devel] [RFC PATCH 0/2] Add one more PCI IOMMU ops Peter Xu
2016-02-17 10:25 ` [Qemu-devel] [RFC PATCH 1/2] pci: renaming PCIIOMMUFunc to PCIIOMMUASLookupFunc Peter Xu
2016-02-17 10:25 ` [Qemu-devel] [RFC PATCH 2/2] pci: add PCIIOMMUOps and PCIIOMMUIntRemapFunc Peter Xu
2016-02-17 19:46 ` Paolo Bonzini [this message]
2016-02-18 4:54 ` Peter Xu
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=56C4CE0A.4070501@redhat.com \
--to=pbonzini@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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.