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] remove fullflush and nofullflush in IOMMU generic option
Date: Mon, 22 Sep 2008 21:01:44 +0200 [thread overview]
Message-ID: <20080922190144.GK24392@amd.com> (raw)
In-Reply-To: <20080922184822.GA24046@elte.hu>
On Mon, Sep 22, 2008 at 08:48:22PM +0200, Ingo Molnar wrote:
> applied Fujita's patch below to tip/x86/iommu that reverts those
> options, thanks guys!
>
> i'm wondering how we should proceed. For debug, iommu=off is certainly
> good enough - all kernels are supposed to work out of box on all hw, and
> every other result is a regression that must be fixed.
>
> For performance tuning, it probably makes sense for developers to tune
> IOMMU details (so that the bootup defaults can be improved - this is not
> really something that should be done on a workload basis), but for that
> IMO a /debug interface is a lot more useful than rather intrusive (and
> inflexible) boot options.
>
> What do you think about a debugfs based tuning of various IOMMU details?
> Maybe even the active driver could be changed - say from AMD-IOMMU to
> GART, or to off.
Yes, for the IO/TLB flushing policy a /debug interface is usefull and
certainly for a number of other parameters we have today at the
commandline.
But I am not sure if we can change the IOMMU implementation on-the-fly
at runtime. We have to wait until all drivers have released their dma
memory before we can switch it off. For coherent allocations this may
take a long time.
So for selecting the type of IOMMU active in the system the command line
parameters are needed, I think. I prefer the iommu=$type parameter for
selecting the default (better: to select a default different from what
the kernel had chosen itself). We can have the IOMMU specific options to
switch it off in addition if we like to.
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 19:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 16:23 [PATCH] remove fullflush and nofullflush in IOMMU generic option FUJITA Tomonori
2008-09-19 16:45 ` Joerg Roedel
2008-09-19 17:09 ` FUJITA Tomonori
2008-09-19 17:20 ` Joerg Roedel
2008-09-19 17:34 ` FUJITA Tomonori
2008-09-19 17:46 ` Joerg Roedel
2008-09-19 18:40 ` FUJITA Tomonori
2008-09-19 19:42 ` Joerg Roedel
2008-09-19 17:30 ` Joerg Roedel
2008-09-19 17:40 ` FUJITA Tomonori
2008-09-19 18:01 ` Joerg Roedel
2008-09-19 18:48 ` FUJITA Tomonori
2008-09-19 19:52 ` Joerg Roedel
2008-09-19 20:02 ` FUJITA Tomonori
2008-09-19 20:19 ` Joerg Roedel
2008-09-19 21:56 ` FUJITA Tomonori
2008-09-19 22:09 ` Joerg Roedel
2008-09-19 22:18 ` FUJITA Tomonori
2008-09-19 22:39 ` Joerg Roedel
2008-09-20 0:54 ` FUJITA Tomonori
2008-09-20 6:00 ` Ingo Molnar
2008-09-20 13:57 ` FUJITA Tomonori
2008-09-22 11:17 ` Ingo Molnar
2008-09-22 12:05 ` Joerg Roedel
2008-09-22 15:25 ` FUJITA Tomonori
2008-09-22 16:23 ` Joerg Roedel
2008-09-22 16:51 ` FUJITA Tomonori
2008-09-22 18:34 ` Joerg Roedel
2008-09-22 18:48 ` Ingo Molnar
2008-09-22 19:01 ` Joerg Roedel [this message]
2008-09-24 13:12 ` FUJITA Tomonori
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=20080922190144.GK24392@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