From: Valdis.Kletnieks@vt.edu
To: David Woodhouse <dwmw2@infradead.org>
Cc: Youquan Song <youquan.song@linux.intel.com>,
"Song, Youquan" <youquan.song@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"hpa@linux.intel.com" <hpa@linux.intel.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Sankaran, Rajesh" <rajesh.sankaran@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Liu, Kent" <kent.liu@intel.com>
Subject: Re: [PATCH v3] x86, vt-d: enable x2apic opt out
Date: Tue, 24 May 2011 08:13:28 -0400 [thread overview]
Message-ID: <5843.1306239208@localhost> (raw)
In-Reply-To: Your message of "Tue, 24 May 2011 08:38:47 BST." <1306222728.2627.49.camel@i7.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On Tue, 24 May 2011 08:38:47 BST, David Woodhouse said:
> On Tue, 2011-05-24 at 05:18 +0100, Valdis.Kletnieks@vt.edu wrote:
> > Do we want an actual WARN there, complete with stack traceback and
> > all?
> >
> > Or did you intend a pr_warn or printk(KERN_WARNING or similar?
>
> The traceback has been very useful in other BIOS issues, because it gets
> tracked and counted on kerneloops.org along with platform
> identification. So we have been able to track down the major offenders
> of some of the most egregious BIOS stupidities and make *some* progress
> on getting them to improve the untested dross they habitually turn out.
Oh OK... that probably is a good idea then.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2011-05-24 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 14:32 [PATCH v3] x86, vt-d: enable x2apic opt out Youquan Song
2011-05-24 2:18 ` Valdis.Kletnieks
2011-05-24 15:36 ` Youquan Song
2011-05-24 4:18 ` Valdis.Kletnieks
2011-05-24 7:38 ` David Woodhouse
2011-05-24 12:13 ` Valdis.Kletnieks [this message]
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=5843.1306239208@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=allen.m.kay@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kent.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rajesh.sankaran@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=youquan.song@intel.com \
--cc=youquan.song@linux.intel.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 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.