From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Rostyslav Khudolii <ros@qtec.com>
Cc: Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, "bhelgaas@google.com" <bhelgaas@google.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: PCI IO ECS access is no longer possible for AMD family 17h
Date: Tue, 4 Mar 2025 10:26:14 -0500 [thread overview]
Message-ID: <20250304152614.GA1785630@yaz-khff2.amd.com> (raw)
In-Reply-To: <CAJDH93u+9KLBVSrFnQm3==9E4VaVohavq+FZT+UqWdRs9FHn-g@mail.gmail.com>
On Tue, Mar 04, 2025 at 08:39:29AM +0100, Rostyslav Khudolii wrote:
> Hi Yazen,
>
> >
> > Ros,
> > Is/was there a reason why you didn't have the MCFG/MMCONFIG options
> > enabled in your kernel?
> >
> > Was this a side effect of trying to build a minimal kernel or similar?
> >
> > Thanks,
> > Yazen
> >
> > P.S. Sorry for the late reply. My mailbox is missing Ros's reply to me.
>
> I inherited a kernel config used here from a previous custom,
> V1000-based solution. Most likely originally
> it came from the x86_64_defconfig. Maybe MMCONFIG wasn't enabled by
> default at that time.
> We never had problems with this because our BIOS keeps the IO ECS
> enabled (that's against the spec recommendation).
> The kernel default for PCI_MMCONFIG is 'y' now, so it's unlikely that
> people will run into this issue unless
> they explicitly disable it.
>
Thanks Rostyslav for confirming.
This seems to be the commit:
55027a7772b1 ("x86: Align x86_64 PCI_MMCONFIG with 32-bit variant")
Before this, PCI_MMCONFIG was default 'y' on 32-bit and no default on
64-bit.
It has been default 'y' on 32-bit since the beginning of history.
1da177e4c3f4 ("Linux-2.6.12-rc2")
Thanks,
Yazen
next prev parent reply other threads:[~2025-03-04 15:26 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 [this message]
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
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=20250304152614.GA1785630@yaz-khff2.amd.com \
--to=yazen.ghannam@amd.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ros@qtec.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.