All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "thomas.tai@oracle.com" <thomas.tai@oracle.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"subhan.mohammed@oracle.com" <subhan.mohammed@oracle.com>
Subject: Re: Question regarding PCI/AER: Enable reporting for ports enumerated after AER driver registration
Date: Wed, 20 May 2020 20:09:31 +0000	[thread overview]
Message-ID: <d9c3371d476c849ccf1aef5fd1b0971c68a8c48e.camel@intel.com> (raw)
In-Reply-To: <232b49b5-90cf-8eff-48cb-1bd6ce3a1977@oracle.com>

Hi Thomas,

On Wed, 2020-05-20 at 15:47 -0400, Thomas Tai wrote:
> Hi Bjorn,
> I have a question regarding "PCI/AER: Enable reporting for ports 
> enumerated after AER driver registration" hope that you don't mind 
> giving us some hints.
> 
> We found the patch mentioned in the following link fixes one of our 
> issues where a device's AER was not enable correctly.
> 
> https://patchwork.ozlabs.org/project/linux-pci/patch/1536085989-2956-1-git-send-email-jonathan.derrick@intel.com/
> 
> I am wondering that if you are going to upstream the patch?
> 
> Thank you,
> Thomas

I suspect you could be seeing issues due to the firmware-first
dependencies. Your platform could be requiring FFS via HEST which is
affecting Native AER in non-ACPI domains.

There were some recent commits to converge FFS to _OSC only:
https://marc.info/?l=linux-pci&m=158834532728113&w=2

Could you try Bjorn's latest branch ?

There is also a DPC set for Native DPC which I will be resending soon:
https://marc.info/?l=linux-pci&m=158835454431698&w=2



  reply	other threads:[~2020-05-20 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 19:47 Question regarding PCI/AER: Enable reporting for ports enumerated after AER driver registration Thomas Tai
2020-05-20 20:09 ` Derrick, Jonathan [this message]
2020-05-20 20:20   ` Thomas Tai

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=d9c3371d476c849ccf1aef5fd1b0971c68a8c48e.camel@intel.com \
    --to=jonathan.derrick@intel.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=subhan.mohammed@oracle.com \
    --cc=thomas.tai@oracle.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.