From: jcm@redhat.com (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI/MSI: pci-xgene-msi: Enable MSI support in ACPI boot for X-Gene v1
Date: Wed, 26 Apr 2017 00:17:08 -0400 [thread overview]
Message-ID: <6b577a0e-db39-d2d9-1093-3fb2513c568f@redhat.com> (raw)
In-Reply-To: <CADaLNDkvY_gZwWYfy1dHzBLRwH1S1h3gTN9ib5ixqG4REJuOow@mail.gmail.com>
On 06/03/2016 06:15 PM, Duc Dang wrote:
> Do you have other suggestions? Otherwise, I will prepare a patch
> following Lorenzo's approach.
Duc has since left Applied for other pastures. I miss him, he's a great
guy. He laid all the right groundwork for this, but the ACPI binding
still needs to be upstreamed. It's a few lines of code matching on
APMC0D0E but without it, upstream kernels wont have working MSI on
X-Gene with ACPI. I need this to be upstreamed soon please :) Can
someone at APM followup with an updated patch, and get it in?
Here's the rub. The average person booting a Linux box (even a good
kernel person) isn't going to say "hey, MSIs aren't setup right on this
ARM server because it's compliant with 1 out of 3 possible ways MSIs
might be done at a high level [let's forget the many others] and all it
needs is this...". What they're going to say is "huh, PCIe card doesn't
work, might be an MSI problem". Which is the email I have after someone
tried using an IB card in an X-Gene box and spent a few hours poking.
We're so close to having "ACPI all the things" but the latest
development builds of RHEL don't do MSI on X-Gene because of the Red Hat
"upstream first" rules. So let's get that fixed.
Thanks,
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
prev parent reply other threads:[~2017-04-26 4:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 1:56 [PATCH] PCI/MSI: pci-xgene-msi: Enable MSI support in ACPI boot for X-Gene v1 Duc Dang
2016-02-10 17:08 ` Marc Zyngier
2016-02-10 17:58 ` Duc Dang
2016-02-20 19:47 ` Duc Dang
2016-02-22 16:03 ` Bjorn Helgaas
2016-03-07 19:24 ` Duc Dang
2016-02-24 16:09 ` Mark Salter
2016-02-24 16:16 ` Marc Zyngier
2016-02-24 22:28 ` Duc Dang
2016-02-25 17:38 ` Lorenzo Pieralisi
2016-05-25 23:13 ` Duc Dang
2016-05-26 12:34 ` Lorenzo Pieralisi
2016-05-26 20:49 ` Duc Dang
2016-05-27 10:52 ` Lorenzo Pieralisi
2016-06-03 22:15 ` Duc Dang
2017-04-26 4:17 ` Jon Masters [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=6b577a0e-db39-d2d9-1093-3fb2513c568f@redhat.com \
--to=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).