From: Bjorn Helgaas <bhelgaas@google.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Yijing Wang <wangyijing@huawei.com>,
Brian Becker <brian.johnathan.b@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Subject: Re: How to check for proper MSI support?
Date: Sat, 5 Jul 2014 16:21:49 -0600 [thread overview]
Message-ID: <CAErSpo7Dk+7THPn2SUO1p-P0bbfP7nSyOoiukXLgMsuGoJrMOA@mail.gmail.com> (raw)
In-Reply-To: <CAKb7UviYak+Jt6+RGFZc=OtNh2DVJaCvxnBpRRkw7zVn8u+9Vw@mail.gmail.com>
On Thu, Jul 3, 2014 at 10:32 PM, Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> So let me get this straight -- you're suggesting I add a quirk for
> every PCI chipset that doesn't support MSI? There are probably
> hundreds of these... anything made before 1999 or so, and probably a
> bunch since then too. There _has_ to be a way to do this generically.
> Is the PCI spec version anywhere in the root hub?
>
> Perhaps we can check if every bridge on the way to the CPU has the MSI
> capability (including the root hub)? (And naturally _that_ won't
> work... on my sandybridge laptop, the host bridge doesn't have the MSI
> cap but the system most definitely supports MSI.)
>
> Adding Bjorn... perhaps you know? Some of the info has been stripped
> out by now, you can see the full lspci -vvvxxx at
> http://marc.info/?l=linux-pci&m=140443441730503&w=2
Huh, this stinks. We don't really have a good way of figuring out
whether the system chipset supports MSI. The ACPI FADT "MSI Not
Supported" bit (ACPI_FADT_NO_MSI) was added to the ACPI v3.0b spec in
October 2006, so that won't help the systems that predate that or
don't have ACPI.
We have quirks for some Serverworks, ATI, and VIA chipsets that
basically do the same as booting with "pci=nomsi". But as you say,
it's unreasonable to add quirks for all old systems.
Brian, can you open a report at http://bugzilla.kernel.org and attach
a complete dmesg log, /proc/cpuinfo contents, and "lspci -vvv" output?
If I understand correctly, you have a P200MMX with a 430FX chipset.
I'm not a hardware guy, but sounds like that might be a 200MHz Pentium
with MMX (P54CS), which does have an integrated LAPIC, according to
wikipedia.
>From the PCI host bridge's perspective, an incoming MSI just looks
like a normal DMA write. As long as that write reaches the CPU LAPIC,
it should work fine. There's not really any specific MSI support
required, except to route the incoming write to the CPU LAPIC. So
it's possible that a bridge designed before MSI was added to the PCI
spec might be able to support MSI.
But I don't know how much value there is in MSI on such old systems.
Maybe we could default to disabling MSI on BIOS dates before 1998 or
something.
Bjorn
next prev parent reply other threads:[~2014-07-05 22:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 3:20 How to check for proper MSI support? Ilia Mirkin
2014-07-03 5:58 ` Yijing Wang
2014-07-04 0:40 ` Brian Becker
[not found] ` <CALhae2jRz8hL0bwySAbP7r+vJGOG5aif4GA_Yjp0inGAwz5JEA@mail.gmail.com>
2014-07-04 2:35 ` Yijing Wang
2014-07-04 2:43 ` Ilia Mirkin
2014-07-04 3:09 ` Yijing Wang
2014-07-04 3:30 ` Ilia Mirkin
2014-07-04 3:56 ` Yijing Wang
2014-07-04 4:32 ` Ilia Mirkin
2014-07-04 5:59 ` Yijing Wang
2014-07-04 6:26 ` Brian Becker
2014-07-04 7:01 ` Yijing Wang
2014-07-05 22:21 ` Bjorn Helgaas [this message]
2014-07-05 23:04 ` Brian Becker
2014-07-04 2:45 ` Brian Becker
2014-07-04 3:13 ` Yijing Wang
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=CAErSpo7Dk+7THPn2SUO1p-P0bbfP7nSyOoiukXLgMsuGoJrMOA@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=brian.johnathan.b@gmail.com \
--cc=imirkin@alum.mit.edu \
--cc=linux-pci@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=wangyijing@huawei.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).