From: "H. Peter Anvin" <hpa@zytor.com>
To: 7eggert@gmx.de
Cc: Ingo Molnar <mingo@elte.hu>,
Luca Tettamanti <kronos.it@gmail.com>,
"H. Peter Anvin" <hpa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [2.6.27] overlapping early reservations [was: early exception - lockdep related?]
Date: Sun, 07 Sep 2008 21:26:07 -0700 [thread overview]
Message-ID: <48C4A95F.5040900@zytor.com> (raw)
In-Reply-To: <E1KcNQE-0001Le-8P@be1.7eggert.dyndns.org>
Bodo Eggert wrote:
>
> I don't think ignoring an intrd will be as serious, but having a panic (and
> a timeout) is preferable to starting the wrong configuration.
>
Most of the time, ignoring the initrd would result in a panic anyway,
and arguably the times it wouldn't, it's going to do something wrong.
-hpa
next prev parent reply other threads:[~2008-09-08 4:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b8P0N-3Dp-11@gated-at.bofh.it>
[not found] ` <b8PaB-3Or-23@gated-at.bofh.it>
[not found] ` <b8Q6x-51x-11@gated-at.bofh.it>
[not found] ` <b961C-rW-9@gated-at.bofh.it>
[not found] ` <b97qL-26L-15@gated-at.bofh.it>
2008-09-07 16:47 ` [2.6.27] overlapping early reservations [was: early exception - lockdep related?] Bodo Eggert
2008-09-08 4:26 ` H. Peter Anvin [this message]
2008-09-08 14:30 ` Ingo Molnar
2008-09-05 19:17 Luca Tettamanti
2008-09-05 19:25 ` Peter Zijlstra
2008-09-05 20:18 ` H. Peter Anvin
2008-09-06 13:20 ` Luca Tettamanti
2008-09-06 14:51 ` Ingo Molnar
2008-09-06 16:06 ` Yinghai Lu
2008-09-08 17:54 ` Luca Tettamanti
2008-09-08 18:04 ` Yinghai Lu
2008-09-08 19:14 ` Luca Tettamanti
2008-09-08 19:35 ` Yinghai Lu
2008-09-08 20:00 ` Luca Tettamanti
2008-09-08 20:46 ` Yinghai Lu
2008-09-08 21:25 ` Luca Tettamanti
2008-09-08 22:32 ` Yinghai Lu
2008-09-09 21:48 ` Luca Tettamanti
2008-09-06 17:20 ` Luca Tettamanti
2008-09-06 17:25 ` Ingo Molnar
2008-09-06 17:29 ` Luca Tettamanti
2008-09-06 13:41 ` Ingo Molnar
2008-09-06 16:14 ` Yinghai Lu
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=48C4A95F.5040900@zytor.com \
--to=hpa@zytor.com \
--cc=7eggert@gmx.de \
--cc=hpa@kernel.org \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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.