From: "Alex G." <mr.nuke.me@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: bhelgaas@google.com, keith.busch@intel.com,
alex_gagniuc@dellteam.com, austin_bolen@dell.com,
shyam_iyer@dell.com, Frederick Lawler <fred@fredlawl.com>,
Oza Pawandeep <poza@codeaurora.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] PCI/AER: Fix aerdrv loading with "pcie_ports=native" parameter
Date: Tue, 3 Jul 2018 12:13:19 -0500 [thread overview]
Message-ID: <77bd7f4b-adf6-15f8-e506-61fe934c4493@gmail.com> (raw)
In-Reply-To: <20180703163854.GA61685@bhelgaas-glaptop.roam.corp.google.com>
On 07/03/2018 11:38 AM, Bjorn Helgaas wrote:
> On Mon, Jul 02, 2018 at 11:16:01AM -0500, Alexandru Gagniuc wrote:
>> According to the documentation, "pcie_ports=native", linux should use
>> native AER and DPC services. While that is true for the _OSC method
>> parsing, this is not the only place that is checked. Should the HEST
>> table list PCIe ports as firmware-first, linux will not use native
>> services.
>>
>> This happens because aer_acpi_firmware_first() doesn't take
>> 'pcie_ports' into account. This is wrong. DPC uses the same logic when
>> it decides whether to load or not, so fixing this also fixes DPC not
>> loading.
>>
>> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
>> ---
>> drivers/pci/pcie/aer.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c
>> index a2e88386af28..db2c01056dc7 100644
>> --- a/drivers/pci/pcie/aer.c
>> +++ b/drivers/pci/pcie/aer.c
>> @@ -283,13 +283,14 @@ static int aer_hest_parse(struct acpi_hest_header *hest_hdr, void *data)
>>
>> static void aer_set_firmware_first(struct pci_dev *pci_dev)
>> {
>> - int rc;
>> + int rc = 0;
>> struct aer_hest_parse_info info = {
>> .pci_dev = pci_dev,
>> .firmware_first = 0,
>> };
>>
>> - rc = apei_hest_parse(aer_hest_parse, &info);
>> + if (!pcie_ports_native)
>> + rc = apei_hest_parse(aer_hest_parse, &info);
>>
>> if (rc)
>> pci_dev->__aer_firmware_first = 0;
>> @@ -324,7 +325,9 @@ bool aer_acpi_firmware_first(void)
>> };
>>
>> if (!parsed) {
>> - apei_hest_parse(aer_hest_parse, &info);
>> + if (!pcie_ports_native)
>> + apei_hest_parse(aer_hest_parse, &info);
>> +
>> aer_firmware_first = info.firmware_first;
>> parsed = true;
>> }
>
> I was thinking something along the lines of the patch below, so we
> don't have to work through the settings of "rc" and "info". But maybe
> I'm missing something subtle?
>
> One subtle thing that I didn't look into is the
> pcie_aer_get_firmware_first() stub for the non-CONFIG_ACPI_APEI case.
>
>
> diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c
> index b24f2d252180..5ccbd7635f33 100644
> --- a/drivers/pci/pcie/aer.c
> +++ b/drivers/pci/pcie/aer.c
> @@ -342,6 +342,9 @@ int pcie_aer_get_firmware_first(struct pci_dev *dev)
> if (!pci_is_pcie(dev))
> return 0;
>
> + if (pcie_ports_native)
> + return 0;
> +
Here we're not setting dev->__aer_firmware_first_valid. Assuming we only
check for it via pcie_aer_get_firmware_first(), we should be fine. THis
field is used in portdrv.h, but its use seems safe. I think this
approach can work.
> if (!dev->__aer_firmware_first_valid)
> aer_set_firmware_first(dev);
> return dev->__aer_firmware_first;
> @@ -362,6 +365,9 @@ bool aer_acpi_firmware_first(void)
> .firmware_first = 0,
> };
>
> + if (pcie_ports_native)
> + return false;
> +
This makes better sense.
> if (!parsed) {
> apei_hest_parse(aer_hest_parse, &info);
> aer_firmware_first = info.firmware_first;
>
next prev parent reply other threads:[~2018-07-03 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 19:58 [PATCH v2] PCI/AER: Fix aerdrv loading with "pcie_ports=native" parameter Alexandru Gagniuc
2018-06-30 21:31 ` Bjorn Helgaas
2018-07-01 4:39 ` Alex G
2018-07-02 13:16 ` Bjorn Helgaas
2018-07-02 14:52 ` Alex G.
2018-07-02 13:19 ` Bjorn Helgaas
2018-07-02 16:16 ` [PATCH v3] " Alexandru Gagniuc
2018-07-03 16:38 ` Bjorn Helgaas
2018-07-03 17:13 ` Alex G. [this message]
2018-07-03 23:27 ` [PATCH v4] " Alexandru Gagniuc
2018-07-10 23:19 ` Bjorn Helgaas
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=77bd7f4b-adf6-15f8-e506-61fe934c4493@gmail.com \
--to=mr.nuke.me@gmail.com \
--cc=alex_gagniuc@dellteam.com \
--cc=austin_bolen@dell.com \
--cc=bhelgaas@google.com \
--cc=fred@fredlawl.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=poza@codeaurora.org \
--cc=shyam_iyer@dell.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).