xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Wang2 <wei.wang2@amd.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: AMD IOMMU intremap tables and IOAPICs
Date: Wed, 7 Sep 2011 13:18:33 +0200	[thread overview]
Message-ID: <201109071318.34239.wei.wang2@amd.com> (raw)
In-Reply-To: <CAFLBxZbvogJfQM0vR0dLCA1YmiWnVz90kRs89KXsJ8VdEqvb=g@mail.gmail.com>

On Tuesday 06 September 2011 17:47:59 George Dunlap wrote:
> Wei,
>
> Quick question:  Am I reading the code correctly, that even with
> per-device interrupt remap tables, that GSIs are accounted to the
> intremap table of the corresponding IOAPIC, presumably because the
> IOMMU sees interrupts generated as GSIs as coming from the IOAPIC?  In
> that case, then we need all devices sharing the same IOAPIC must not
> have any vector collisions.  Is that correct?
>
>  -George

That is true.  All legacy devices have to send interrupts to IOMMU via IOAPIC. 
So even we use per-device table. All devices attached to the same IOAPIC will 
use the same interrupt table. There should be no vector collisions. 
Per-device table only makes sense for MSI devices or systems with multiple 
IOAPICs.

Thanks
Wei

      parent reply	other threads:[~2011-09-07 11:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 15:47 AMD IOMMU intremap tables and IOAPICs George Dunlap
2011-09-06 15:54 ` Andrew Cooper
2011-09-06 15:57   ` George Dunlap
2011-09-06 16:03     ` Andrew Cooper
2011-09-06 16:00       ` George Dunlap
2011-09-06 16:06   ` Tim Deegan
2011-09-06 16:03     ` George Dunlap
2011-09-06 16:13     ` Keir Fraser
2011-09-06 16:25     ` Andrew Cooper
2011-09-07 11:18 ` Wei Wang2 [this message]

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=201109071318.34239.wei.wang2@amd.com \
    --to=wei.wang2@amd.com \
    --cc=George.Dunlap@eu.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).