From: Matthew Wilcox <willy@infradead.org>
To: 412574090@163.com
Cc: corbet@lwn.net, bhelgaas@google.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
xiongxin@kylinos.cn, weiyufeng <weiyufeng@kylinos.cn>
Subject: Re: [PATCH] PCI: limit pci bridge and subsystem speed to 2.5GT/s
Date: Mon, 5 Aug 2024 16:15:00 +0100 [thread overview]
Message-ID: <ZrDsdA3-uUJV8VdK@casper.infradead.org> (raw)
In-Reply-To: <20240805092010.82986-1-412574090@163.com>
On Mon, Aug 05, 2024 at 05:20:10PM +0800, 412574090@163.com wrote:
> From: weiyufeng <weiyufeng@kylinos.cn>
>
> Add a kernel command-line option 'speed2_5g' to limit pci bridge
> and subsystem devices speed to 2.5GT/s. As a debug method, this
> provide for developer to temporarily slow down PCIe devices for
> verification.
I am opposed to this patch benig merged. There's no harm to keep it for
your own testing.
prev parent reply other threads:[~2024-08-05 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 9:20 [PATCH] PCI: limit pci bridge and subsystem speed to 2.5GT/s 412574090
2024-08-05 15:15 ` Matthew Wilcox [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=ZrDsdA3-uUJV8VdK@casper.infradead.org \
--to=willy@infradead.org \
--cc=412574090@163.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=weiyufeng@kylinos.cn \
--cc=xiongxin@kylinos.cn \
/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