From: Sinan Kaya <okaya@codeaurora.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] PCI: disable SERR for kdump kernel
Date: Thu, 20 Apr 2017 20:04:03 -0400 [thread overview]
Message-ID: <a1b0cc72-1724-9b67-ec58-9650d2e8ff94@codeaurora.org> (raw)
In-Reply-To: <CAE9FiQVQ4Mvc_SufENJcuO1309h+jqDdme9XNB3R9OvZJKzHvQ@mail.gmail.com>
On 4/20/2017 7:37 PM, Yinghai Lu wrote:
> On Thu, Apr 20, 2017 at 10:14 AM, Sinan Kaya <okaya@codeaurora.org> wrote:
>> On 4/18/2017 8:31 PM, Yinghai Lu wrote:
>>> * pci_setup_device - fill in class and map information of a device
>>> * @dev: the device structure to fill
>>> @@ -1572,6 +1592,9 @@ int pci_setup_device(struct pci_dev *dev
>>> /* device class may be changed after fixup */
>>> class = dev->class >> 8;
>>>
>>> + if (is_kdump_kernel())
>>> + pci_disable_serr(dev);
>>> +
>>
>> This sounds like something that needs to be done while shutting down
>> the first kernel as part of the kdump procedure rather than boot of
>> the kdump kernel in pci setup.
>
> For kdump path, first kernel shutdown path is not called.
>
> We have to do sth in second kernel instead.
>
I didn't know that. Bjorn's compatibility point is also a concern.
Ideally you want something in both places.
> Thanks
>
> Yinghai
>
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2017-04-21 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 0:31 [PATCH v2] PCI: disable SERR for kdump kernel Yinghai Lu
2017-04-20 17:14 ` Sinan Kaya
2017-04-20 18:38 ` Bjorn Helgaas
2017-04-20 18:52 ` Sinan Kaya
2017-04-20 23:37 ` Yinghai Lu
2017-04-21 0:04 ` Sinan Kaya [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=a1b0cc72-1724-9b67-ec58-9650d2e8ff94@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.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).