DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=RdYBsfE/fcWcTfS4kMkEiSbdXDBqAV/chomnreJGZudovxy9u/uGO0rHynh95Vd4x8hTJZXzC+XL4Bd+8em9NBpBUieX3C8jDsYvk7CsDKPaLJ/XUeu71S4/Un4zWfzwxGim4EULn/+444WBtfZNIUk+7+cDcldD9VdwUrNrHAs=
Message-ID: <2c0942db0706121725o9621b3bv35fc8ccf563b6fbb@mail.gmail.com>
Date: Tue, 12 Jun 2007 17:25:06 -0700
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Pavel Machek" <pavel@ucw.cz>
Subject: Re: [PATCH] trim memory not covered by WB MTRRs
Cc: "Jesse Barnes" <jesse.barnes@intel.com>,
       "Andi Kleen" <andi@firstfloor.org>, linux-kernel@vger.kernel.org,
       "Justin Piszcz" <jpiszcz@lucidpixels.com>,
       "Eric W. Biederman" <ebiederm@xmission.com>
In-Reply-To: <20070612215501.GE13747@elf.ucw.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200706071530.51552.jesse.barnes@intel.com>
	 <20070612145007.GA5986@ucw.cz>
	 <200706120829.21465.jesse.barnes@intel.com>
	 <20070612213020.GA13747@elf.ucw.cz>
	 <2c0942db0706121438y6d2d2bb5qbe11269691366d20@mail.gmail.com>
	 <20070612215501.GE13747@elf.ucw.cz>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1055
Lines: 26

On 6/12/07, Pavel Machek <pavel@ucw.cz> wrote:
> On Tue 2007-06-12 14:38:28, Ray Lee wrote:
> > Panicking when it's not necessary is anti-social. If the kernel can
> > continue, then it should, unless it's a correctness issue that may
> > cause data corruption. Given that the kernel can even work around the
> > problem now, throwing a panic is even less warranted.
>
> Printk("*********************** WARNING")
>
> is anti-social, too.

Pavel, this warning isn't even going to print on any of your systems.
So it's completely different than the straw-man you're proposing (that
I snipped).

Look, if you want to argue that the stars should go away, then sure,
I'm not going to stop you. But panicking over a BIOS misconfiguration
issue? One that can be corrected by the kernel? That's just plain
stupid.

Ray
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/