From: Mario Limonciello <superm1@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Bjorn Helgaas" <helgaas@kernel.org>
Cc: "Maciej Grochowski" <Maciej.Grochowski@sony.com>,
"Geramy Loveless" <gloveless@jqluv.com>,
"Eric Auger" <eauger@redhat.com>,
"Alexey Fomenko" <alexey.fomenko@intel.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Mesih Kilinc" <Mesih.Kilinc@sony.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 00/14] PCI: Resource placement algorithm fixes
Date: Tue, 10 Nov 2026 14:06:30 -0600 [thread overview]
Message-ID: <47e6cb2d-f84c-4aef-b658-7dac5e046434@kernel.org> (raw)
In-Reply-To: <f37d6958-086b-0006-8fbc-c4c15369b796@linux.intel.com>
>
> The regression is the same genoa iomem blackhole we discussed in the v3
> thread:
>
> https://lore.kernel.org/linux-pci/20261013130948.6231-9-ilpo.jarvinen@linux.intel.com
> /
>
> There were multiple possible possible ways to quirk this and it comes down
> to which one you (Bjorn) prefer. I just left my quirk patch out of these
> v4 and v5 series because it seemed the least likely to be the one taken.
>
> If you want me to test a specific quirk approach on the affected system,
> just let me know. I already did test reverting your change that freed the
> e820 reserved regions for iomem use and that did prevent the regression.
>
Yeah with any luck our best bet for everyone is reverting commit
07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map").
>
> (I now seem to realize I forgot to include Mario while sending v5. I've
> added him to this now.)
>
> Mario was willing to pursue contacting the reporters of the earlier
> problems with a pre-prepared branch to test to see if my placement series
> could resolve the issues reported (earlier). Depending the results of that
> test, we might have yet another way to quirk it.
>
> Mario,
>
> There were quite many changes in v5 so I'd prefer the test branch using
> v5.
>
Done!
https://lore.kernel.org/linux-pci/20261110-superm1-genoa-mess-v1-0-bdcb3a6f2463@kernel.org/
prev parent reply other threads:[~2026-11-10 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 13:43 Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 01/14] resource: Mark free space assigned Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 02/14] parisc/PCI: Clean up resource debug print & use dynamic debug Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 03/14] PCI: Don't size or assign disabled BARs Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 04/14] PCI: Use __ffs64() for resource_size_t typed align Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 05/14] PCI: Prevent zero align from reaching __ffs64() Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 06/14] linux/log2.h: Add 64-bit roundup/down_pow_of_two_u64() variants Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 07/14] PCI: Derive aligns[] array size in a define Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 08/14] PCI: Honor alignment overrides Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 09/14] PCI: Place resources to either edge of the window Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 10/14] PCI: Separate align/raw size calculation from pbus_size_mem() Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 11/14] PCI: Calculate bridge window with optional sizes from scratch Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 12/14] PCI: Move size/align calculation fully into __pbus_size_mem() Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 13/14] PCI: Fix composite resource sizing Ilpo Järvinen
2026-11-06 13:43 ` [PATCH v5 14/14] PCI: Add debug printing to window sizing Ilpo Järvinen
2026-11-06 15:26 ` [PATCH v5 00/14] PCI: Resource placement algorithm fixes Nikolas Joshua Britton
2026-11-06 16:43 ` Ilpo Järvinen
2026-11-08 1:51 ` Doug Calobrisi
2026-11-09 23:27 ` Bjorn Helgaas
2026-11-10 9:47 ` Ilpo Järvinen
2026-11-10 20:06 ` Mario Limonciello [this message]
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=47e6cb2d-f84c-4aef-b658-7dac5e046434@kernel.org \
--to=superm1@kernel.org \
--cc=Maciej.Grochowski@sony.com \
--cc=Mesih.Kilinc@sony.com \
--cc=alexey.fomenko@intel.com \
--cc=bhelgaas@google.com \
--cc=eauger@redhat.com \
--cc=gloveless@jqluv.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®