From: Yijing Wang <wangyijing@huawei.com>
To: Bjorn Helgaas <bhelgaas@google.com>, Keith Busch <keith.busch@intel.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Jon Mason <jon.mason@intel.com>
Subject: Re: Debugging incorrect mps settings detected
Date: Wed, 4 Jun 2014 10:43:45 +0800 [thread overview]
Message-ID: <538E87E1.8030604@huawei.com> (raw)
In-Reply-To: <CAErSpo6B76KL=PVGuuLjvC77kvxSjjYNnngXxPEjj_3dMbA0yg@mail.gmail.com>
accurate>> 0xd5200000-0xd52fffff 64bit pref]
>> [ 2107.015060] pci 0000:09:00.0: Max Payload Size 128, but upstream
>> 0000:05:07.0 set to 256; if necessary, use "pci=pcie_bus_safe" and report a
>> bug
>> [ 2107.015079] pci 0000:09:00.0: no hotplug settings from platform
>>
>> The commit message that added the warning indicates it may be a BIOS
>> issue that incorrectly configures this, but BIOS isn't involved with
>> setting the MPS on a device hot add, am I right? Or is that wrong?
>
> The BIOS is not involved in setting MPS on a device hot-add.
>
>> This is a Dell R620 server, if that matters, though we see this on other
>> platforms as well.
>>
>> Using pci=pcie_bus_perf works around the issue, but that seems a bit
>> odd to suggest to users. Is setting MPS on hot-add something the PCI
>> driver layer ought to be doing, or should I be looking into the platform
>> BIOS instead?
>
> The PCI core should be doing something intelligent here. If we can't
> configure MPS safely, we should prevent the device from being enabled.
> But this is stuff the PCI core doesn't implement yet.
Hi Bjorn,
We had a long discussion about fix this issue.
Link: http://marc.info/?l=linux-pci&m=137714192204947&w=2
Now more BIOS configure device mps larger than 128B, So I think
we should consider to fix it before we have a perfect solution about mps setting.
>
> It's hard to reconfigure MPS after boot because it affects other
> devices in the system, and I don't think we can always change the
> settings of other devices while they're active.
Yes, what we can only change is the device not active after hotplug.
>
> I'm not sure that warning is correct. It seems like it should suggest
> pcie_bus_peer2peer, which is documented as guaranteeing that hot-added
> devices will work. But this is always confusing to me, and I could be
> wrong about this.
I think warning is proper, pcie_bus_safe is designed to fix the hotlplug issue.
pcie_bus_peer2perr guarantee that hotplug device work fine, because all mps setting
128B. Maybe we should change document a little, make it more clear.
>
> Bjorn
>
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2014-06-04 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 20:04 Debugging incorrect mps settings detected Keith Busch
2014-06-03 21:01 ` Bjorn Helgaas
2014-06-04 2:43 ` Yijing Wang [this message]
2014-06-04 17:44 ` Jon Mason
2014-06-05 16:41 ` Keith Busch
2014-07-28 19:59 ` Jordan_Hargrave
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=538E87E1.8030604@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=jon.mason@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.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 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.