From: Borislav Petkov <bp@alien8.de>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: jeremy@goop.org, xen-devel@lists.xensource.com,
Matt Wilson <msw@amazon.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
x86@kernel.org, Paul Bolle <pebolle@tiscali.nl>,
virtualization@lists.linux-foundation.org, mingo@redhat.com,
Jan Beulich <JBeulich@suse.com>, "H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen: remove unused Kconfig parameter
Date: Wed, 10 Jul 2013 05:20:56 +0200 [thread overview]
Message-ID: <20130710032056.GA14873@pd.tnic> (raw)
In-Reply-To: <1382658288.20130710003458@eikelenboom.it>
On Wed, Jul 10, 2013 at 12:34:58AM +0200, Sander Eikelenboom wrote:
> Grub does this in it's update script to prevent adding a xen + kernel
> combination that has no chance of booting when dom0 support has not
> been configured in the kernel. That doesn't seem to be a unreasonable
> thought.
Actually, I don't see the problem - if there's no such support, then the
boot fails - plain and simple. That's like not building in or adding
into the initrd, support for your root filesystem - it is your own damn
fault. It is not the bootloader's job to sanity check whether your
kernel boots or not.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-07-10 3:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1373264904-27053-1-git-send-email-michael.opdenacker@free-electrons.com>
2013-07-08 19:28 ` [PATCH] xen: remove unused Kconfig parameter Konrad Rzeszutek Wilk
2013-07-08 19:34 ` [Xen-devel] " Matt Wilson
2013-07-08 20:13 ` H. Peter Anvin
[not found] ` <20130708193457.GA6926@u109add4315675089e695.ant.amazon.com>
2013-07-08 20:29 ` [Xen-devel] " H. Peter Anvin
2013-07-08 20:58 ` Borislav Petkov
[not found] ` <20130708205834.GA481@pd.tnic>
2013-07-08 23:35 ` Paul Bolle
[not found] ` <1373326534.1438.10.camel@x61.thuisdomein>
2013-07-09 0:26 ` Konrad Rzeszutek Wilk
2013-07-09 7:41 ` Jan Beulich
2013-07-09 14:48 ` Konrad Rzeszutek Wilk
2013-07-09 14:54 ` Jan Beulich
2013-07-09 15:05 ` Borislav Petkov
[not found] ` <20130709150554.GA27579@pd.tnic>
2013-07-09 15:09 ` H. Peter Anvin
2013-07-09 17:19 ` Konrad Rzeszutek Wilk
2013-07-09 20:01 ` Borislav Petkov
2013-07-09 20:40 ` Konrad Rzeszutek Wilk
2013-07-09 20:57 ` Borislav Petkov
2013-07-09 22:34 ` Sander Eikelenboom
[not found] ` <1382658288.20130710003458@eikelenboom.it>
2013-07-10 3:20 ` Borislav Petkov [this message]
2013-07-10 3:55 ` H. Peter Anvin
2013-07-10 6:19 ` Matt Wilson
2013-07-10 7:41 ` Sander Eikelenboom
2013-07-10 14:46 ` Konrad Rzeszutek Wilk
2013-07-11 10:08 ` Paul Bolle
2013-07-11 17:57 ` H. Peter Anvin
2013-07-11 18:13 ` Paul Bolle
2013-07-11 18:24 ` Konrad Rzeszutek Wilk
2013-07-11 21:13 ` Geert Uytterhoeven
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=20130710032056.GA14873@pd.tnic \
--to=bp@alien8.de \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=michael.opdenacker@free-electrons.com \
--cc=mingo@redhat.com \
--cc=msw@amazon.com \
--cc=pebolle@tiscali.nl \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).