lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 25 Aug 2020 07:23:20 +0100 From: Christoph Hellwig <hch@...radead.org> To: Kai-Heng Feng <kai.heng.feng@...onical.com> Cc: bhelgaas@...gle.com, jonathan.derrick@...el.com, Mario.Limonciello@...l.com, Heiner Kallweit <hkallweit1@...il.com>, Mika Westerberg <mika.westerberg@...ux.intel.com>, "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>, Xiongfeng Wang <wangxiongfeng2@...wei.com>, Krzysztof Wilczynski <kw@...ux.com>, "open list:PCI SUBSYSTEM" <linux-pci@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>, Dan Williams <dan.j.williams@...el.com>, "Huffman, Amber" <amber.huffman@...el.com> Subject: Re: [PATCH] PCI/ASPM: Enable ASPM for links under VMD domain On Fri, Aug 21, 2020 at 08:32:20PM +0800, Kai-Heng Feng wrote: > New Intel laptops with VMD cannot reach deeper power saving state, > renders very short battery time. So what about just disabling VMD given how bloody pointless it is? Hasn't anyone learned from the AHCI remapping debacle? I'm really pissed at all this pointless crap intel comes up with just to make life hard for absolutely no gain. Is it so hard to just leave a NVMe device as a standard NVMe device instead of f*^&ing everything up in the chipset to make OS support a pain and I/O slower than by doing nothing?
Powered by blists - more mailing lists