From: Joerg Roedel <joerg.roedel@amd.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: mingo@elte.hu, 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:27:13 +0200 [thread overview]
Message-ID: <20080922142713.GA24392@amd.com> (raw)
In-Reply-To: <20080922231619X.fujita.tomonori@lab.ntt.co.jp>
On Mon, Sep 22, 2008 at 11:16:25PM +0900, FUJITA Tomonori wrote:
> On Mon, 22 Sep 2008 16:07:49 +0200
> Joerg Roedel <joerg.roedel@amd.com> wrote:
>
> > On Mon, Sep 22, 2008 at 10:35:08PM +0900, FUJITA Tomonori wrote:
> > > This is against tip/x86/iommu.
> > >
> > > =
> > > From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> > > Subject: [PATCH] AMD IOMMU: revert "x86, AMD IOMMU: honor iommu=off instead of amd_iommu=off"
> > >
> > > This reverts:
> > >
> > > commit 8b14518fadd9d5915827d86d5c10e602fedf042e
> > > Author: Joerg Roedel <joerg.roedel@amd.com>
> > > Date: Thu Jul 3 19:35:09 2008 +0200
> > >
> > > 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.
>
> I'm not talking about what the best way to disable IOMMUs for
> users. I'm talking about how the current code works. It's a different
> topic. If you want to fix this, that's fine.
>
> I just pointed out:
>
> - You think that iommu=off and amd_iommu=off worked in the same way,
> but they didn't.
>
> - This commit removed the useful feature.
Ok, let me explain it this way. Before there was an AMD IOMMU driver
the user had to pass iommu=off to disable iommu usage at all and
iommu=soft to just disable usage of hardware IOMMUs. Further you have
iommu=calgary to select the Calgary driver. With AMD IOMMU the
situation is not very different. You can have two different hardware
IOMMUs in the system: GART and AMD IOMMU. Passing iommu=off still
disables all hardware IOMMUs. Your patch doesn't change that too. But to
be consistent with whats already there, the best solution to achieve
what you want it implementing iommu=gart and iommu=amd to select which
hardware IOMMU in the system you want to use.
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
next prev parent reply other threads:[~2008-09-22 14:27 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 [this message]
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
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=20080922142713.GA24392@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