mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Borislav Petkov" <bp@alien8.de>,
	"Bjorn Helgaas" <helgaas@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Maciej Grochowski" <Maciej.Grochowski@sony.com>,
	"Nikolas Joshua Britton" <nbritton@exabit.io>,
	"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>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Bradley Morgan" <brads@mainlining.org>,
	"Hans de Goede" <hansg@kernel.org>,
	"Kai-Heng Feng" <kaihengf@nvidia.com>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3 8/8] PCI/quirks: Avoid certain address on Genoa systems
Date: Wed, 14 Oct 2026 13:49:29 +0300	[thread overview]
Message-ID: <as9eOZjjRtW7dqAM@ashevche-desk.local> (raw)
In-Reply-To: <3f578b9f-cdac-4bdb-8f0a-f5b3a48f6622@amd.com>

On Tue, Oct 13, 2026 at 09:41:48PM -0500, Mario Limonciello wrote:
> On 10/13/26 19:43, Borislav Petkov wrote:
> > On Tue, Oct 13, 2026 at 05:40:10PM -0500, Bjorn Helgaas wrote:
> > > But I'm frankly terrified to touch it because I'm skeptical that two
> > > more quirks are enough.  I just expect that whatever strategy BIOS
> > > uses to build these maps is likely to be used on many models.  I do
> > 
> > Do we have an explanation why BIOS is doing that shit?
> > 
> > Mario?
> 
> If I was to guess; because Windows allocates MMIO space differently it
> hasn't been a problem.

Oh, I can confirm this part as I noticed the issue on 64-bit addresses for
Intel LPSS at some point exactly due to different ways of allocating space for
the devices for PCI. Id est one is goes upwards (from the start to the end of
the region), while the other downwards (from the end to the start of the
region).

> Which begs the question; does Ilpo's series improve things enough that we
> wouldn't have these problems either?
> 
> Maybe we should just tail my patches on Ilpos' series and then land them
> linux-next the very beginning of next cycle and beg everyone who was
> affected to test linux-next.
> 
> > Btw, Mario, you should replace "Genoa" with "Zen4" everywhere so that it is
> > more clear to people.
> 
> Ack; if I send mine out on their own I'll adjust.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-10-14 10:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 13:09 [PATCH v3 0/8] PCI: Resource placement algorithm fixes Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 1/8] resource: Mark free space assigned Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 2/8] PCI/parisc: Clean up resource debug print & use dynamic debug Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 3/8] PCI: Honor alignment overrides Ilpo Järvinen
2026-10-13 14:08   ` Rodrigo Vivi
2026-10-13 13:09 ` [PATCH v3 4/8] PCI: Fix nesting windows with remainder at the left edge Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 5/8] linux/log2.h: Add 64-bit roundup/down_pow_of_two64() variants Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 6/8] PCI: Place resources to either edge of the window Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 7/8] PCI: Fix composite resource sizing Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 8/8] PCI/quirks: Avoid certain address on Genoa systems Ilpo Järvinen
2026-10-13 17:00   ` Mario Limonciello
2026-10-13 17:03     ` Mario Limonciello
2026-10-13 17:26       ` Ilpo Järvinen
2026-10-13 18:59         ` Mario Limonciello
2026-10-13 22:40           ` Bjorn Helgaas
2026-10-14  0:43             ` Borislav Petkov
2026-10-14  2:41               ` Mario Limonciello
2026-10-14 10:49                 ` Andy Shevchenko [this message]
2026-10-14  9:34             ` Hans de Goede
2026-10-14 10:51               ` Andy Shevchenko
2026-10-14 11:17                 ` Ilpo Järvinen
2026-10-14 10:46             ` Andy Shevchenko

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=as9eOZjjRtW7dqAM@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=Maciej.Grochowski@sony.com \
    --cc=alexey.fomenko@intel.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=brads@mainlining.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=eauger@redhat.com \
    --cc=gloveless@jqluv.com \
    --cc=hansg@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kaihengf@nvidia.com \
    --cc=kw@linux.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mario.limonciello@amd.com \
    --cc=mingo@redhat.com \
    --cc=nbritton@exabit.io \
    --cc=robh@kernel.org \
    --cc=tglx@kernel.org \
    --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 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®