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] [day] [month] [year] [list]
Message-ID: <20250826180945.6o2xfhadv6a2c36i@pali>
Date: Tue, 26 Aug 2025 20:09:45 +0200
From: Pali Rohár <pali@...nel.org>
To: Rostyslav Khudolii <ros@...c.com>
Cc: Ingo Molnar <mingo@...nel.org>, Yazen Ghannam <yazen.ghannam@....com>,
	Borislav Petkov <bp@...en8.de>,
	Filip Štědronský <p@...narg.cz>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	x86@...nel.org
Subject: Re: PCI IO ECS access is no longer possible for AMD family 17h

On Tuesday 26 August 2025 17:07:38 Rostyslav Khudolii wrote:
> >
> > Hello Rostyslav, I would like to remind the previous email.
> > I still do not know which bit in D18F4x044 represents the
> > EnableCF8ExtCfg config.
> >
> 
> Hi Pali,
> 
> Sorry for the late reply again. So in D18F4x044:
> - bit 0. EnableCf8ExtCfg. Enable PCI extended configuration register
> access for CFC/CF8
> accesses;
> - bit 1. DisPciCfgReg. Disable CFC/CF8 Accesses to IO space. When set
> to 1, CFC/CF8 accesses are treated as
> PCI IO space accesses and not PCI configuration accesses.
> 
> Unfortunately, I don't know if this also applies to later families.

Thank you very much for the info. I was missing the information about
the bit 0 offset.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ