From: Christoph Hellwig <hch@lst.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Alexandru Gagniuc <alex_gagniuc@dellteam.com>,
Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Jan Vesely <jano.vesely@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Alex Williamson <alex.williamson@redhat.com>,
Austin Bolen <austin_bolen@dell.com>,
Shyam Iyer <Shyam_Iyer@dell.com>, Sinan Kaya <okaya@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Issues with "PCI/LINK: Report degraded links via link bandwidth notification"
Date: Thu, 30 Jan 2020 17:26:06 +0100 [thread overview]
Message-ID: <20200130162606.GB6377@lst.de> (raw)
In-Reply-To: <20200120023326.GA149019@google.com>
On Sun, Jan 19, 2020 at 08:33:26PM -0600, Bjorn Helgaas wrote:
> NVMe, GPU folks, do your drivers or devices change PCIe link
> speed/width for power saving or other reasons? When CONFIG_PCIE_BW=y,
> the PCI core interprets changes like that as problems that need to be
> reported.
The NVMe driver doesn't. For devices I don't know of any, but Ican't
find anything in the spec that would forbid it.
next prev parent reply other threads:[~2020-01-30 16:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 22:10 Issues with "PCI/LINK: Report degraded links via link bandwidth notification" Bjorn Helgaas
2020-01-16 2:44 ` Alex G
2020-01-18 0:18 ` Bjorn Helgaas
2020-01-20 2:33 ` Bjorn Helgaas
2020-01-20 15:56 ` Alex Williamson
2020-01-20 16:01 ` Alex G.
2020-01-21 11:10 ` Lucas Stach
2020-01-21 14:55 ` Alex G.
2020-02-03 1:56 ` Dave Airlie
2020-02-03 2:04 ` Dave Airlie
2020-02-03 2:07 ` Ben Skeggs
2020-02-03 21:16 ` Alex Deucher
2020-02-04 4:38 ` Lukas Wunner
2020-02-04 14:47 ` Alex Deucher
2020-01-30 16:26 ` Christoph Hellwig [this message]
2020-02-22 16:58 ` Bjorn Helgaas
2021-01-28 23:39 ` Bjorn Helgaas
2021-01-28 23:51 ` Sinan Kaya
2021-01-29 0:07 ` Alex G.
2021-01-29 21:56 ` Bjorn Helgaas
2021-02-02 19:50 ` Alex G.
2021-02-02 20:16 ` Bjorn Helgaas
2021-02-02 20:25 ` Alex G.
2021-01-29 1:30 ` Alex Deucher
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=20200130162606.GB6377@lst.de \
--to=hch@lst.de \
--cc=Shyam_Iyer@dell.com \
--cc=airlied@linux.ie \
--cc=alex.williamson@redhat.com \
--cc=alex_gagniuc@dellteam.com \
--cc=austin_bolen@dell.com \
--cc=axboe@fb.com \
--cc=daniel@ffwll.ch \
--cc=helgaas@kernel.org \
--cc=jano.vesely@gmail.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mr.nuke.me@gmail.com \
--cc=okaya@kernel.org \
--cc=sagi@grimberg.me \
/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).