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: Mon, 11 Aug 2025 19:57:56 +0200 [thread overview]
Message-ID: <20250811175756.kqtbnlrmzphpj2lm@pali> (raw)
In-Reply-To: <20250716181320.rhhcdymjy26kg7rq@pali>
Hello Rostyslav, I would like to remind the previous email.
I still do not know which bit in D18F4x044 represents the
EnableCF8ExtCfg config.
On Wednesday 16 July 2025 20:13:20 Pali Rohár wrote:
> On Wednesday 16 July 2025 10:03:40 Rostyslav Khudolii wrote:
> > > Hello, thank you for information.
> > >
> > > Just I would like to know, where did you find information that the
> > > EnableCF8ExtCfg register was moved to D18F4x044? It is documented in
> > > some AMD specification?
> > >
> > > I did not find anything regarding this change.
> >
> > I mentioned the exact specification in my first message. It's under
> > NDA, unfortunately.
>
> Do you know if this applies only for AMD family 17? Or also for later
> fam 18, 19 and 1a?
>
> And for confirmation, which bit represent the EnableCF8ExtCfg in PCI
> config space register D18F4x044? It is still 14th bit like in family 16h?
>
>
> Just for explanation, in your first message you wrote:
>
> "register still exists but is now located at a different address (see
> the "Processor Programming Reference (PPR) for AMD Family 17h", Section 2.1.8)."
>
> Document named "Processor Programming Reference (PPR) for AMD Family 17h
> Models 01h,08h, Revision B2 Processors" with revision information
> "54945 Rev 3.03 - Jun 14, 2019" is publicly available at AMD web:
>
> https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/programmer-references/54945-ppr-family-17h-models-00h-0fh-processors.zip
>
> I looked into that document into section 2.1.8 "PCI Configuration Legacy Access"
> and there is not related to EnableCF8ExtCfg.
>
> So I was somehow confused to which section / document you are referring.
> And now if I understand correctly, you have NDA documentation with the
> same title as the above public one, but with the different content, right?
next prev parent reply other threads:[~2025-08-11 17:57 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 [this message]
2025-08-26 15:07 ` Rostyslav Khudolii
2025-08-26 18:09 ` Pali Rohár
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=20250811175756.kqtbnlrmzphpj2lm@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).