public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH] x86 built-in command line
Date: Mon, 12 Jun 2006 10:59:19 -0700	[thread overview]
Message-ID: <448DAB77.2040306@am.sony.com> (raw)
In-Reply-To: <e6k7ak$gpd$1@terminus.zytor.com>

H. Peter Anvin wrote:
> b. This patch will override a user-provided command line if one
> exists.  This is the wrong behaviour; instead, the builtin command
> line should only apply if no user-specified command line is present.

I'd prefer that the kernel default command line was appended
to the user-supplied one, instead of replacing it. (Or vice-versa.)
This way I can leave the user-specified command line empty and
get the behaviour described above.  Or, I can choose a few
specific options to come from the bootloader and have others
come from the default command line (in the kernel).

I'm VERY interested in this feature, for purposes of automated
testing on multiple architectures.  I have a test rig that can easily
set the command line at kernel compilation time.  However,
coming up with a mechanism to control command line options on
multiple different bootloaders, for the variety of embedded platforms
I deal with, is very difficult.  Right now this part of my
test rig works on all popular embedded arches except x86.

Eventually, I'd like to automatically test many different
kernel command line options, on multiple platforms.


Regards,
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================


  parent reply	other threads:[~2006-06-12 17:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11 21:55 [PATCH] x86 built-in command line Matt Mackall
2006-06-11 22:54 ` Jesper Juhl
2006-06-11 23:30 ` Jan Engelhardt
2006-06-11 23:47   ` Matt Mackall
2006-06-12 17:14     ` H. Peter Anvin
2006-06-11 23:40 ` Arjan van de Ven
2006-06-11 23:51   ` Matt Mackall
2006-06-12  0:08     ` Arjan van de Ven
2006-06-12  1:38       ` Matt Mackall
2006-06-12  5:13         ` Willy Tarreau
2006-06-12 17:15     ` H. Peter Anvin
2006-06-12  8:11 ` Andi Kleen
2006-06-12 14:37   ` Matt Mackall
2006-06-12 17:18     ` H. Peter Anvin
2006-06-12 17:12 ` H. Peter Anvin
2006-06-12 17:36   ` Michael Buesch
2006-06-12 17:52     ` H. Peter Anvin
2006-06-12 17:59   ` Tim Bird [this message]
     [not found] ` <200606121712.k5CHClUE017185@terminus.zytor.com>
2006-06-12 20:49   ` Matt Mackall
2006-06-12 21:19     ` Thomas Gleixner
2006-06-12 21:36       ` Tim Bird
2006-06-12 21:45         ` Thomas Gleixner
2006-06-12 22:03           ` Tim Bird
2006-06-12 21:45     ` Randy.Dunlap
2006-06-12 22:00       ` Tim Bird
2006-06-12 22:10         ` Randy.Dunlap

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=448DAB77.2040306@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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