From: ebiederm@xmission.com (Eric W. Biederman)
To: "Adam Kropelin" <akropel1@rochester.rr.com>
Cc: "Auke Kok" <auke-jan.h.kok@intel.com>,
"Adrian Bunk" <bunk@stusta.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
<jgarzik@pobox.com>, <alan@lxorguk.ukuu.org.uk>,
"Allen Parker" <parker@isohunt.com>, <jesse.brandeburg@intel.com>,
<gregkh@suse.de>, <linux-pci@atrey.karlin.mff.cuni.cz>,
<netdev@vger.kernel.org>
Subject: Re: 2.6.20-rc7: known regressions (v2) (part 1)
Date: Sat, 03 Feb 2007 22:12:43 -0700 [thread overview]
Message-ID: <m1ireizet0.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <09ba01c74817$1ae12980$84163e05@kroptech.com> (Adam Kropelin's message of "Sat, 3 Feb 2007 23:44:07 -0500")
"Adam Kropelin" <akropel1@rochester.rr.com> writes:
> Naive question... Can the pci layer (or e1000) detect that MSI is not enabled in
> the hardware and avoid using it in that case? With the number of MSI problems
> showing up it seems risky to assume it's usable on any given platform without
> some sort of sanity check.
>
Yes, that is what we should do. Start with the assumption MSI doesn't work
and enable it when we detect the hardware is setup properly.
Thing is that is going to take a little bit of work, and a little bit of
thinking on how to structure it properly. So in real time it is going
to be a couple of weeks before the code to do that is ready.
Right now the model is that piecemeal we put in the code to
conditionally turn off chipsets that are known to have problems.
Which for building a reliable system when MSI isn't mandatory for
operation seems backwards.
Probably in addition we should have a warning such as:
"Found devices supporting MSI and but chipset is unknown".
Eric
prev parent reply other threads:[~2007-02-04 5:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0701302019530.11095@woody.linux-foundation.org>
2007-02-03 0:44 ` 2.6.20-rc7: known regressions (v2) (part 1) Adrian Bunk
2007-02-03 6:06 ` Auke Kok
2007-02-03 7:41 ` Eric W. Biederman
2007-02-03 18:06 ` Adam Kropelin
2007-02-03 20:43 ` Auke Kok
2007-02-03 21:00 ` Adam Kropelin
2007-02-03 21:26 ` Auke Kok
2007-02-03 22:24 ` Eric W. Biederman
2007-02-03 21:12 ` Eric W. Biederman
2007-02-03 23:20 ` Adam Kropelin
2007-02-04 1:14 ` Eric W. Biederman
2007-02-04 4:44 ` Adam Kropelin
2007-02-04 5:12 ` Eric W. Biederman [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=m1ireizet0.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=akropel1@rochester.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=auke-jan.h.kok@intel.com \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=netdev@vger.kernel.org \
--cc=parker@isohunt.com \
--cc=torvalds@linux-foundation.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 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).