From: "Pali Rohár" <pali@kernel.org>
To: Rostyslav Khudolii <ros@qtec.com>
Cc: "Ingo Molnar" <mingo@kernel.org>,
"Yazen Ghannam" <yazen.ghannam@amd.com>,
"Borislav Petkov" <bp@alien8.de>,
"Filip Štědronský" <p@regnarg.cz>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: PCI IO ECS access is no longer possible for AMD family 17h
Date: Tue, 26 Aug 2025 20:09:45 +0200 [thread overview]
Message-ID: <20250826180945.6o2xfhadv6a2c36i@pali> (raw)
In-Reply-To: <CAJDH93svLMPM0O_Lq=EgfH6dxXXbnq4QkM6ye_8tyvsRYs8dug@mail.gmail.com>
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.
next prev parent reply other threads:[~2025-08-26 18:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 13:15 PCI IO ECS access is no longer possible for AMD family 17h Rostyslav Khudolii
2024-12-19 11:23 ` Borislav Petkov
2024-12-19 16:44 ` Yazen Ghannam
2024-12-27 11:07 ` Rostyslav Khudolii
2025-02-26 15:07 ` Ingo Molnar
2025-03-03 9:21 ` Rostyslav Khudolii
2025-03-03 11:32 ` Ingo Molnar
2025-03-03 12:20 ` Rostyslav Khudolii
2025-03-03 18:42 ` Yazen Ghannam
2025-03-04 7:39 ` Rostyslav Khudolii
2025-03-04 15:26 ` Yazen Ghannam
2025-06-21 14:50 ` Pali Rohár
2025-07-15 10:43 ` Rostyslav Khudolii
2025-07-15 17:06 ` Pali Rohár
2025-07-16 8:03 ` Rostyslav Khudolii
2025-07-16 18:13 ` Pali Rohár
2025-08-11 17:57 ` Pali Rohár
2025-08-26 15:07 ` Rostyslav Khudolii
2025-08-26 18:09 ` Pali Rohár [this message]
2025-01-22 22:13 ` Pali Rohár
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=20250826180945.6o2xfhadv6a2c36i@pali \
--to=pali@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=p@regnarg.cz \
--cc=ros@qtec.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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).