Document x86-64 iommu kernel parameters
PATCH 1/1 Document x86-64 iommu kernel parameters
---
After having to go figure out what some of these means, I figured I would save others the trouble.
Some of these are "best guess" based on a quick scan of the code, so it certainly needs a sanity review before going upstream.
Documentation/kernel-parameters.txt +24 -0
@@ -763,6 +763,30 @@ and is between 256 and 4096 characters. It is defined in the file inttest= [IA64] + iommu=option[,option..] [X86-64] + off Disable IOMMU. + force Unconditionally enable IOMMU. + noforce Disable IOMMU and IOMMU merging, by default. + biomerge Unconditionally enable IOMMU, IOMMU merging, + and set BIO IOMMU vmerge boundary to 4096. + panic Panic on IOMMU overflow. + nopanic Do not panic on IOMMU overflow. + merge Unconditionally enable IOMMU, IOMMU merging. + nomerge Disable IOMMU merging. + forcesac Force single address cycle (SAC, 32-bit). + allowdac Permit dual address cycle (DAC, 64-bit). + nodac Forbid dual address cycle (DAC, 64-bit). + soft Enable swiotlb. + calgary Use Calgary IOMMU. + + (GART-only options follow...) + <NNN> Specify size of remapping area. + fullflush Disable optimizing flushing strategy. + nofullflush Enable optimizing flushing strategy. + noagp Use entire aperture, AGP isn't using it. + noaperture Disable aperture fixups / hole init. + memaper=<N> malloc an aperture of order N. + io7= [HW] IO7 for Marvel based alpha systems See comment before marvel_specify_io7 in arch/alpha/kernel/core_marvel.c.
Quoted 8 lines · On Tue, 2 Oct 2007 21:34:13 -0400 Jeff Garzik wrote:
Signed-off-by Jeff Garzik <[email protected]>---
After having to go figure out what some of these means, I figured I would save others the trouble.Some of these are "best guess" based on a quick scan of the code, so it certainly needs a sanity review before going upstream.
"iommu" is listed in Documentation/x86_64/boot-options.txt along with more x86_64-specific boot options.
A few other arches do something similar...
Quoted 26 lines
Documentation/kernel-parameters.txt +18
-0@@ -763,6 +763,30 @@ and is between 256 and 4096 characters. It is defined in the file inttest= [IA64] + iommu=option[,option..] [X86-64] + off Disable IOMMU. + force Unconditionally enable IOMMU. + noforce Disable IOMMU and IOMMU merging, by default. + biomerge Unconditionally enable IOMMU, IOMMU merging, + and set BIO IOMMU vmerge boundary to 4096. + panic Panic on IOMMU overflow. + nopanic Do not panic on IOMMU overflow. + merge Unconditionally enable IOMMU, IOMMU merging. + nomerge Disable IOMMU merging. + forcesac Force single address cycle (SAC, 32-bit). + allowdac Permit dual address cycle (DAC, 64-bit). + nodac Forbid dual address cycle (DAC, 64-bit). + soft Enable swiotlb. + calgary Use Calgary IOMMU. + + (GART-only options follow...) + <NNN> Specify size of remapping area.
Documentation/kernel-parameters.txt and is between 256 and 4096 characters. It is defined in the file
Quoted 10 lines
Documentation/kernel-parameters.txt +6
-1+ fullflush Disable optimizing flushing strategy. + nofullflush Enable optimizing flushing strategy. + noagp Use entire aperture, AGP isn't using it. + noaperture Disable aperture fixups / hole init. + memaper=<N> malloc an aperture of order N. + io7= [HW] IO7 for Marvel based alpha systems See comment before marvel_specify_io7 in arch/alpha/kernel/core_marvel.c. -
---
~Randy
Quoted 7 lines · Randy Dunlap
Quoted 5 lines · On Tue, 2 Oct 2007 21:34:13 -0400 Jeff Garzik wrote:
Signed-off-by Jeff Garzik <[email protected]>---
After having to go figure out what some of these means, I figured I would save others the trouble.
Quoted 6 lines
Quoted 2 lines
Some of these are "best guess" based on a quick scan of the code, so it certainly needs a sanity review before going upstream.
"iommu" is listed in
Documentation/x86_64/boot-options.txtalong with more x86_64-specific boot options.
A few other arches do something similar...
Ah! Well, seeing as how we already have a provision for arch-specific options in kernel-parameters.txt, and some less-obscure arch-specific options can be found there, I think an argument can be made for my patch :)
Nonethless, if the maintainer disagrees, they can drop this patch I suppose.
Jeff
Quoted 15 lines · On Tue, 02 Oct 2007 22:30:31 -0400 Jeff Garzik wrote:
Quoted 7 lines · Randy Dunlap
Quoted 5 lines · On Tue, 2 Oct 2007 21:34:13 -0400 Jeff Garzik wrote:
Signed-off-by Jeff Garzik <[email protected]>---
After having to go figure out what some of these means, I figured I would save others the trouble.Quoted 6 lines
Quoted 2 lines
Some of these are "best guess" based on a quick scan of the code, so it certainly needs a sanity review before going upstream.
"iommu" is listed in
Documentation/x86_64/boot-options.txtalong with more x86_64-specific boot options.
A few other arches do something similar...
Quoted 5 lines
Ah! Well, seeing as how we already have a provision for arch-specific options in kernel-parameters.txt, and some less-obscure arch-specific options can be found there, I think an argument can be made for my patch :)
Nonethless, if the maintainer disagrees, they can drop this patch I suppose.
[sorry if there be duplicates; I thought I sent this but can't find it anywhere]
Maybe we can/should merge the doc files along with the x86 arch merge.
---
~Randy
Quoted 3 lines · Randy Dunlap
Maybe we can/should merge the doc files along with the x86 arch merge.
Well, the x86 merge is pretty much mechanical. It should be followed up with a lot of manual merging.
-hpa
Quoted 8 lines · H. Peter Anvin
Quoted 3 lines · Randy Dunlap
Maybe we can/should merge the doc files along with the x86 arch merge.
Well, the x86 merge is pretty much mechanical. It should be followed up with a lot of manual merging.
It would be really nice if identical kernel parameters used the same names, so people didn't waste their time trying e.g. "nolapic_timer" on x86_64 because that option fixed their problems on i386 (it's "noapictimer" in x86_64.)
Quoted 11 lines · Chuck Ebbert
Quoted 5 lines · H. Peter Anvin
Quoted 1 line · Randy Dunlap
Maybe we can/should merge the doc files along with the x86 arch merge.
Well, the x86 merge is pretty much mechanical. It should be followed up with a lot of manual merging.
It would be really nice if identical kernel parameters used the same names, so people didn't waste their time trying e.g. "
nolapic_timer" onx86_64because that option fixed their problems on i386 (it's "noapictimer" inx86_64.)
Well the x86-64 option was there first; you have to ask whoever added the i386 option why they used a different name
But I normally added aliases as people reported them. Nobody did in this case.
One reason is probably that noapictimer is not very useful on x86-64 -- the nolapic_timer is really more a workaround that only started making sense on HRT because it made "apicmaintimer" default.
On current x86-64 which doesn't do that there is very little reason to use it and you'll usually just break things.
So I guess the real reason is that they're not actually identical when you look closely.
-Andi
Quoted 4 lines · Andi Kleen
Well the x86-64 option was there first; you have to ask whoever added the i386 option why they used a different name
Quoted 9 lines
But I normally added aliases as people reported them. Nobody did in this case.
One reason is probably that noapictimer is not very useful on x86-64 -- the
nolapic_timeris really more a workaround that only started making sense on HRT because it made "apicmaintimer" default.
On current x86-64 which doesn't do that there is very little reason to use it and you'll usually just break things.
I have HRT in my x86_64 kernel. I guess that patchset should add the alias.
Quoted 11 lines · Jeff Garzik
Quoted 10 lines · Randy Dunlap
Quoted 7 lines · On Tue, 2 Oct 2007 21:34:13 -0400 Jeff Garzik wrote:
Signed-off-by Jeff Garzik <[email protected]>---
After having to go figure out what some of these means, I figured I would save others the trouble.Some of these are "best guess" based on a quick scan of the code, so it certainly needs a sanity review before going upstream.
Quoted 7 lines
Quoted 3 lines
"iommu" is listed in
Documentation/x86_64/boot-options.txtalong with more x86_64-specific boot options.
A few other arches do something similar...Ah! Well, seeing as how we already have a provision for arch-specific options in kernel-parameters.txt, and some less-obscure arch-specific options can be found there, I think an argument can be made for my patch :)
Nonethless, if the maintainer disagrees, they can drop this patch I suppose.
or maybe during the x86 merge, we can merge the docs also...
Signature · 1 line
~Randy