From: "Limonciello, Mario" <Mario.Limonciello@dell.com>
To: "hch@infradead.org" <hch@infradead.org>,
"Derrick, Jonathan" <jonathan.derrick@intel.com>
Cc: "wangxiongfeng2@huawei.com" <wangxiongfeng2@huawei.com>,
"kw@linux.com" <kw@linux.com>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"kai.heng.feng@canonical.com" <kai.heng.feng@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"Huffman, Amber" <amber.huffman@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Subject: RE: [PATCH] PCI/ASPM: Enable ASPM for links under VMD domain
Date: Thu, 27 Aug 2020 17:49:40 +0000 [thread overview]
Message-ID: <DM6PR19MB2636ACECA16E43638B502A6DFA550@DM6PR19MB2636.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20200827162333.GA6822@infradead.org>
> > I don't see the purpose of this line of discussion. VMD has been in the
> > kernel for 5 years. We are constantly working on better support.
>
> Please just work with the platform people to allow the host to disable
> VMD. That is the only really useful value add here.
Can you further elaborate what exactly you're wanting here? VMD enable/disable
is something that is configured in firmware setup as the firmware does the early
configuration for the silicon related to it. So it's up to the OEM whether to
offer the knob to an end user.
At least for Dell this setting also does export to sysfs and can be turned on/off
around a reboot cycle via this: https://patchwork.kernel.org/patch/11693231/.
As was mentioned earlier in this thread VMD is likely to be defaulting to "on"
for many machines with the upcoming silicon. Making it work well on Linux is
preferable to again having to change firmware settings between operating systems
like the NVME remapping thing from earlier silicon required.
next prev parent reply other threads:[~2020-08-27 17:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 12:32 [PATCH] PCI/ASPM: Enable ASPM for links under VMD domain Kai-Heng Feng
2020-08-24 13:04 ` Mika Westerberg
2020-08-25 6:23 ` Christoph Hellwig
2020-08-25 6:39 ` Kai Heng Feng
2020-08-25 6:56 ` Christoph Hellwig
2020-08-26 5:53 ` Kai-Heng Feng
2020-09-02 19:48 ` David Fugate
2020-09-02 22:54 ` Keith Busch
2020-08-26 21:43 ` Derrick, Jonathan
2020-08-27 6:34 ` hch
2020-08-27 16:13 ` Derrick, Jonathan
2020-08-27 16:23 ` hch
2020-08-27 16:45 ` Derrick, Jonathan
2020-08-27 16:50 ` hch
2020-08-27 21:33 ` Dan Williams
2020-08-29 7:23 ` hch
2020-08-27 17:49 ` Limonciello, Mario [this message]
2020-08-29 7:24 ` hch
2020-09-10 1:55 ` Bjorn Helgaas
2020-09-10 16:33 ` Derrick, Jonathan
2020-09-10 17:38 ` Bjorn Helgaas
[not found] <0f902d555deb423ef1c79835b23c917be2633162.camel@intel.com>
2020-09-10 19:17 ` Bjorn Helgaas
2020-09-10 19:51 ` Derrick, Jonathan
2020-09-17 17:20 ` Bjorn Helgaas
2020-09-23 14:29 ` Kai-Heng Feng
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=DM6PR19MB2636ACECA16E43638B502A6DFA550@DM6PR19MB2636.namprd19.prod.outlook.com \
--to=mario.limonciello@dell.com \
--cc=amber.huffman@intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=hkallweit1@gmail.com \
--cc=jonathan.derrick@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=wangxiongfeng2@huawei.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;
as well as URLs for NNTP newsgroup(s).