LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "J.D. Hood" <jdthood@yahoo.co.uk>
To: Stelian Pop <stelian.pop@fr.alcove.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux should not set the "PnP OS" boot flag
Date: Mon, 8 Oct 2001 23:12:09 +0100 (BST)	[thread overview]
Message-ID: <20011008221209.26310.qmail@web10301.mail.yahoo.com> (raw)
In-Reply-To: <20011008152542.J12242@come.alcove-fr>

 --- Stelian Pop <stelian.pop@fr.alcove.com> wrote: 
> Anyway, the PnP OS setting in the BIOS doesn't change anything
> regarding to the Linux PnP initialisation oops (same printouts,
> same calltrace, etc).

Too bad.  :(

Although it apparently won't help Stelian, I still think it's
good practice (1) to set the boot flags to what's safe, and
then (2) to give the user the ability to change the default if
s/he wants to try speeding things up.

(Parenthesis re: time savings
Alan: You say that setting the PnP-OS flag can save up to
thirty seconds at boot time.  My suspicion is that it may
actually be the diagnostics that take up all these seconds
(e.g., testing each of 128 million memory locations), not
the configuration process.  Are you sure that it isn't
clearing the DIAG flag that's important for time savings,
not setting the PNPOS flag?)

It's useful to be able to select a different default at build
time (CONFIG_SBF_PNPOS).  But in addition I would like to provide
/proc access to the bootflags.  That way, if I suspect a hardware
problem I can "echo 1 > /proc/sys/bootflags/diag" and reboot; or
if I am going to boot DOS I can "echo 0 > /proc/sys/bootflags/pnpos"
and reboot.  Question: Where should I put these entries under 
/proc.  Are my examples okay?

--
Thomas


____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

  reply	other threads:[~2001-10-08 22:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-08 12:40 Thomas Hood
2001-10-08 13:25 ` Stelian Pop
2001-10-08 22:12   ` J.D. Hood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-07  2:54 Thomas Hood
2001-10-07 10:02 ` Alan Cox
2001-10-07 13:50   ` Thomas Hood
2001-10-07 14:07     ` Dave Jones
2001-10-07 14:18     ` Alan Cox
2001-10-07 17:10       ` Thomas Hood
2001-10-07 21:59         ` Alan Cox
2001-10-07 17:54       ` Thomas Hood
2001-10-06  3:35 Thomas Hood
2001-10-06 19:24 ` Eric W. Biederman
2001-10-06 21:11   ` Alan Cox
2001-10-07  1:08     ` Eric W. Biederman

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=20011008221209.26310.qmail@web10301.mail.yahoo.com \
    --to=jdthood@yahoo.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian.pop@fr.alcove.com \
    --subject='Re: Linux should not set the "PnP OS" boot flag' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).