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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211026165348.GA146058@bhelgaas>
Date:   Tue, 26 Oct 2021 11:53:48 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc:     Bjorn Helgaas <bhelgaas@...gle.com>,
        Heiner Kallweit <hkallweit1@...il.com>,
        Anthony Wong <anthony.wong@...onical.com>,
        Linux PCI <linux-pci@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Krzysztof WilczyƄski <kw@...ux.com>,
        Vidya Sagar <vidyas@...dia.com>,
        Logan Gunthorpe <logang@...tatee.com>
Subject: Re: [PATCH v2 3/3] PCI/ASPM: Add LTR sysfs attributes

On Tue, Oct 26, 2021 at 10:28:38AM +0800, Kai-Heng Feng wrote:

> What if we fallback to the original approach and use the VMD driver
> to enable ASPM and LTR values?  At least I think Intel should be
> able to provide correct values for their SoC.

Can you post the patches for that?  I'm not sure exactly what the
original approach was.  Are these the same as the downstream support
you mention below?

> So what other options do we have if we want to enable VMD ASPM while
> keeping CONFIG_PCIEASPM_DEFAULT=y?  Right now we enabled the VMD
> ASPM/LTR bits in downstream kernel, but other distro users may want
> to have upstream support for this.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ