All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Michael Ellerman <michael@ellerman.id.au>,
	"Darrick J. Wong" <djwong@us.ibm.com>,
	linux-kernel@vger.kernel.org, Chris McDermott <lcm@us.ibm.com>
Subject: Re: [PATCH] leave APIC code inactive by default on i386
Date: Mon, 6 Mar 2006 12:52:38 -0500	[thread overview]
Message-ID: <20060306175238.GA15971@redhat.com> (raw)
In-Reply-To: <20060306174122.GA2716@elf.ucw.cz>

On Mon, Mar 06, 2006 at 06:41:22PM +0100, Pavel Machek wrote:

 > >  > Is adding "noapic nolapic" to default command line a big problem?
 > > For end-users, yes.  People want things to 'just work', not have
 > > to find arcane commands to type in to make things work.
 > If distro puts "noapic nolapic" on kernel command line, I'd say users
 > are unlikely to remove it.. And if they do remove it and it breaks,
 > they'll only blame themselves...

If distros put 'noapic nolapic' on the command line they've only
themselves to blame when systems that need local apic for
correct operation don't work.

 > One more config-option is also not "cheap" (half of users will get it
 > wrong), and having config-option to change command-line-default seems
 > wrong to me.
 >
 > [Well, you could add CONFIG_CMDLINE to i386, like arm has... that
 > solves more than just this problem...]

I'm not arguing for extra command line options. The inverse, I want
*no* command line options.

What's so hard to understand about expecting something to just work?

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-03-06 17:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  1:20 [PATCH] leave APIC code inactive by default on i386 Darrick J. Wong
2006-01-20 14:42 ` Jan Engelhardt
2006-03-01  3:57 ` Michael Ellerman
2006-03-01  4:33   ` Dave Jones
2006-03-01  5:10     ` Michael Ellerman
2006-03-01 13:38       ` Dave Jones
2006-03-01 13:52         ` Matthew Garrett
2006-03-01  6:36     ` Zwane Mwaikambo
2006-03-01 13:39       ` Dave Jones
2006-03-01 21:29     ` Darrick J. Wong
2006-03-01 22:14       ` Dave Jones
2006-03-01 22:47         ` Darrick J. Wong
2006-03-01 22:51           ` Dave Jones
2006-03-01 23:29             ` Darrick J. Wong
2006-03-06 12:50     ` Pavel Machek
2006-03-06 17:17       ` Dave Jones
2006-03-06 17:41         ` Pavel Machek
2006-03-06 17:52           ` Dave Jones [this message]
2006-03-06 17:58             ` Pavel Machek
2006-03-06 18:17               ` Dave Jones
2006-03-06 19:05                 ` Darrick J. Wong

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=20060306175238.GA15971@redhat.com \
    --to=davej@redhat.com \
    --cc=djwong@us.ibm.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.