mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yinghai@kernel.org>,
	Weidong Han <weidong.han@intel.com>,
	dwmw2@infradead.org, suresh.b.siddha@intel.com,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	kvm@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Intel-IOMMU, intr-remap: source-id checking
Date: Wed, 20 May 2009 05:02:23 -0700	[thread overview]
Message-ID: <m1r5ykm180.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20090520094310.GF9835@amd.com> (Joerg Roedel's message of "Wed\, 20 May 2009 11\:43\:10 +0200")

Joerg Roedel <joerg.roedel@amd.com> writes:

> On Wed, May 20, 2009 at 10:21:14AM +0200, Ingo Molnar wrote:
>> 
>> * Eric W. Biederman <ebiederm@xmission.com> wrote:
>> > Being a major nitpick, I have to point out that the code is not 
>> > structured to support other iommus, and I think AMD has one that 
>> > can do this as well.
>> 
>> (Joerg Cc:-ed)
>
> The AMD IOMMU does also have an interrupt remapping feature. But it is
> currently unsupported in the Linux driver. When this is going to be
> implemented I think we can go the same way as for device passthrough in
> KVM. This was an Intel-only feature too and was later adapted to support
> AMD IOMMU too.

The Intel IOMMU is also interesting because it allows traffic from
buggy ioapcis to be remapped safely in process context, adding a large
margin of safety and flexibility to the existing irq migration
and cpu hotunplug scenarios.

Can we use the AMD IOMMU to achieve the same objective?

I would really like to say from point X on AMD and Intel systems don't
have to worry about irq migrations used caused by old buggy ioapic
state machines, which I have previously confirmed in both AMD and
Intel ioapics.

Eric

  reply	other threads:[~2009-05-20 12:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 18:31 [PATCH v2 0/2] Intel-IOMMU: source-id checking for interrupt remapping Weidong Han
2009-05-19 18:31 ` [PATCH v2 1/2] Intel-IOMMU, intr-remap: set the whole 128bits of irte when modify/free it Weidong Han
2009-05-19 12:14   ` Ingo Molnar
2009-05-19 14:15     ` Han, Weidong
2009-05-19 18:31 ` [PATCH v2 2/2] Intel-IOMMU, intr-remap: source-id checking Weidong Han
2009-05-19 11:50   ` Ingo Molnar
2009-05-19 14:12     ` Han, Weidong
2009-05-19 19:28     ` Eric W. Biederman
2009-05-20  8:21       ` Ingo Molnar
2009-05-20  8:38         ` Han, Weidong
2009-05-20 12:13           ` Eric W. Biederman
2009-05-20  9:43         ` Joerg Roedel
2009-05-20 12:02           ` Eric W. Biederman [this message]
2009-05-20 12:24         ` Eric W. Biederman
2009-05-21  9:00         ` Han, Weidong
2009-05-21 10:04           ` Eric W. Biederman
2009-05-21 13:37             ` Han, Weidong

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=m1r5ykm180.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=weidong.han@intel.com \
    --cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome