public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: ak@suse.de, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Document x86-64 iommu kernel parameters
Date: Tue, 2 Oct 2007 21:01:25 -0700	[thread overview]
Message-ID: <20071002210125.85b84add.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4702FEC7.3000000@garzik.org>

On Tue, 02 Oct 2007 22:30:31 -0400 Jeff Garzik wrote:

> Randy Dunlap wrote:
> > On Tue, 2 Oct 2007 21:34:13 -0400 Jeff Garzik wrote:
> > 
> >> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
> >> ---
> >> 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...
> 
> 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

  parent reply	other threads:[~2007-10-03  4:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03  1:34 [PATCH] Document x86-64 iommu kernel parameters Jeff Garzik
2007-10-03  2:22 ` Randy Dunlap
2007-10-03  2:30   ` Jeff Garzik
2007-10-03  3:42     ` Randy Dunlap
2007-10-03  4:01     ` Randy Dunlap [this message]
2007-10-03  4:10       ` H. Peter Anvin
2007-10-03 16:58         ` Chuck Ebbert
2007-10-04  9:01           ` Andi Kleen
2007-10-04 15:50             ` Chuck Ebbert

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=20071002210125.85b84add.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.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