public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Jeff Garzik <jeff@garzik.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Document x86-64 iommu kernel parameters
Date: Thu, 4 Oct 2007 11:01:46 +0200	[thread overview]
Message-ID: <200710041101.46794.ak@suse.de> (raw)
In-Reply-To: <4703CA28.9010609@redhat.com>

On Wednesday 03 October 2007 18:58, Chuck Ebbert wrote:
> On 10/03/2007 12:10 AM, H. Peter Anvin wrote:
> > Randy Dunlap wrote:
> >> 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.)

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


  reply	other threads:[~2007-10-04  9: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
2007-10-03  4:10       ` H. Peter Anvin
2007-10-03 16:58         ` Chuck Ebbert
2007-10-04  9:01           ` Andi Kleen [this message]
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=200710041101.46794.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=cebbert@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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