From: Joerg Roedel <joerg.roedel@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] AMD IOMMU: revert "x86, AMD IOMMU: honor iommu=off instead of amd_iommu=off"
Date: Mon, 22 Sep 2008 16:59:53 +0200 [thread overview]
Message-ID: <20080922145953.GB24392@amd.com> (raw)
In-Reply-To: <20080922144601.GA27956@elte.hu>
On Mon, Sep 22, 2008 at 04:46:01PM +0200, Ingo Molnar wrote:
>
> * Joerg Roedel <joerg.roedel@amd.com> wrote:
>
> > > x86, AMD IOMMU: honor iommu=off instead of amd_iommu=off
> > >
> > > This patch removes the amd_iommu=off kernel parameter and honors
> > > the generic
> > >
> > > iommu=off parameter for the same purpose.
> > >
> > >
> > > The above commit is wrong.
> >
> > It isn't. The user normally don't care about the type of IOMMU in the
> > system. So disabling it with iommu=off is the right way. To achieve
> > what you want its better to add iommu=gart and iommu=amd to the option
> > parser. This will be consistent with Calgary and SWIOTLB too.
>
> well, what matters in the end is to have a consistent set of exclusion
> options:
>
> gart_iommu=off # disable the GART (and only that one)
> intel_iommu=off # disable the Intel IOMMU (and only that one)
> amd_iommu=off # disable AMD-IOMMU (and only that one)
>
> then there's the all-off option:
>
> iommu=off # wildcard: disable all IOMMUs
>
> [ whether iommu=off also disables the swiotlb is a detail. ]
>
> and we could also do the inclusive options in addition:
>
> iommu=gart # use the GART as the primary IOMMU [if available]
> iommu=amd # use the AMD-IOMMU as the primary IOMMU [if available]
> iommu=intel # use the Intel IOMMU [if available]
>
> so could we please first agree on such a specific list of generic
> options, and then implement them consistently, while keeping legacies
> (the ones that matter) intact as well?
Ok, having $(type)_iommu=off in addition to iommu=$type is surely a good
thing.
Joerg
--
| AMD Saxony Limited Liability Company & Co. KG
Operating | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
System | Register Court Dresden: HRA 4896
Research | General Partner authorized to represent:
Center | AMD Saxony LLC (Wilmington, Delaware, US)
| General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
prev parent reply other threads:[~2008-09-22 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 13:35 [PATCH] AMD IOMMU: revert "x86, AMD IOMMU: honor iommu=off instead of amd_iommu=off" FUJITA Tomonori
2008-09-22 14:07 ` Joerg Roedel
2008-09-22 14:16 ` FUJITA Tomonori
2008-09-22 14:27 ` Joerg Roedel
2008-09-22 15:25 ` FUJITA Tomonori
2008-09-22 16:31 ` Joerg Roedel
2008-09-22 17:07 ` FUJITA Tomonori
2008-09-22 17:22 ` Joerg Roedel
2008-09-22 17:52 ` Ingo Molnar
2008-09-22 14:46 ` Ingo Molnar
2008-09-22 14:59 ` Joerg Roedel [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=20080922145953.GB24392@amd.com \
--to=joerg.roedel@amd.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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