From: Huang Ying <ying.huang@intel.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Len Brown <lenb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/2] ACPI, APEI, PCIE AER, use general HEST table parsing in AER firmware_first setup
Date: Tue, 02 Mar 2010 17:13:27 +0800 [thread overview]
Message-ID: <1267521207.1640.130.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <4B8CC7BD.5020206@jp.fujitsu.com>
On Tue, 2010-03-02 at 16:09 +0800, Hidetoshi Seto wrote:
> (2010/03/02 10:55), Huang Ying wrote:
> > ... The firmware_first setup code is moved from PCI core to
> > AER driver too, because it is only AER related.
> (snip)
> > diff --git a/drivers/pci/pcie/aer/aerdrv_core.c b/drivers/pci/pcie/aer/aerdrv_core.c
> > index c843a79..cc527c1 100644
> > --- a/drivers/pci/pcie/aer/aerdrv_core.c
> > +++ b/drivers/pci/pcie/aer/aerdrv_core.c
> > @@ -858,6 +858,8 @@ void aer_delete_rootport(struct aer_rpc *rpc)
> > */
> > int aer_init(struct pcie_device *dev)
> > {
> > + aer_set_firmware_first(dev);
> > +
> > if (dev->port->aer_firmware_first) {
> > dev_printk(KERN_DEBUG, &dev->device,
> > "PCIe errors handled by platform firmware.\n");
> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> > index 2a94309..ccfaf19 100644
> (snip)
> > @@ -935,7 +928,6 @@ int pci_setup_device(struct pci_dev *dev)
> > dev->multifunction = !!(hdr_type & 0x80);
> > dev->error_state = pci_channel_io_normal;
> > set_pcie_port_type(dev);
> > - set_pci_aer_firmware_first(dev);
> >
> > list_for_each_entry(slot, &dev->bus->slots, list)
> > if (PCI_SLOT(dev->devfn) == slot->number)
>
> The aer_init() will be called for root ports, but not for end point
> devices or so on. So please remain the firmware_first setup code in
> PCI core. Otherwise endpoint drivers will get success on call of
> pci_enable_pcie_error_reporting() regardless of the firmware first.
Or we can call firmware_first setup code in
pci_enable_pcie_error_reporting(), because
1. I think AER related code should be put in drivers/pci/pcie/aer
instead of PCI core or drivers/acpi, if it is possible.
2. pci_setup_device is called so early, so that it is hard to do some
HEST related initialization (such as checking bad format) before it.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2010-03-02 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 1:55 [PATCH 1/2] ACPI, APEI: Make APEI core configurable built-in instead of module Huang Ying
2010-03-02 1:55 ` [PATCH 2/2] ACPI, APEI, PCIE AER, use general HEST table parsing in AER firmware_first setup Huang Ying
2010-03-02 8:09 ` Hidetoshi Seto
2010-03-02 9:13 ` Huang Ying [this message]
2010-03-02 11:04 ` Hidetoshi Seto
2010-03-03 1:43 ` Huang Ying
2010-03-03 2:30 ` Hidetoshi Seto
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=1267521207.1640.130.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=ak@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.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
Powered by JetHome