From: Bjorn Helgaas <helgaas@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Borislav Petkov <bp@alien8.de>, "H . Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@redhat.com>
Cc: "Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Myron Stowe" <myron.stowe@redhat.com>,
"Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>,
"Benoit Grégoire" <benoitg@coeus.ca>,
"Hui Wang" <hui.wang@canonical.com>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: [PATCH 0/3] x86/PCI: Clip only partial E820 overlaps
Date: Thu, 3 Mar 2022 21:51:07 -0600 [thread overview]
Message-ID: <20220304035110.988712-1-helgaas@kernel.org> (raw)
From: Bjorn Helgaas <bhelgaas@google.com>
This is based on Hans' extensive debugging and patch at
https://lore.kernel.org/r/20220228105259.230903-1-hdegoede@redhat.com
and applies on 7e57714cd0ad ("Linux 5.17-rc6").
This is basically the same idea (applying the 4dc2287c1805 workaround only
when an E820 region *partially* overlaps a host bridge window), but I think
it's a little simpler.
This also adds a little dmesg output when clipping, which should make
future debugging easier.
I bcc'd several folks who didn't have public email addresses in the RedHat
bugzilla or Launchpad. If you review or test this, I'd be happy to
acknowledge that.
Bjorn Helgaas (3):
x86/PCI: Eliminate remove_e820_regions() common subexpressions
x86/PCI: Log host bridge window clipping for E820 regions
x86/PCI: Preserve host bridge windows completely covered by E820
arch/x86/include/asm/e820/api.h | 5 +++++
arch/x86/kernel/resource.c | 34 ++++++++++++++++++++++++++-------
arch/x86/pci/acpi.c | 5 +++++
3 files changed, 37 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-04 3:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 3:51 Bjorn Helgaas [this message]
2022-03-04 3:51 ` [PATCH 1/3] x86/PCI: Eliminate remove_e820_regions() common subexpressions Bjorn Helgaas
2022-03-04 3:51 ` [PATCH 2/3] x86/PCI: Log host bridge window clipping for E820 regions Bjorn Helgaas
2022-03-04 3:51 ` [PATCH 3/3] x86/PCI: Preserve host bridge windows completely covered by E820 Bjorn Helgaas
2022-03-04 14:16 ` Hans de Goede
2022-03-04 15:32 ` Bjorn Helgaas
2022-03-04 15:46 ` Hans de Goede
2022-03-04 18:34 ` Bjorn Helgaas
2022-03-05 10:37 ` Hans de Goede
2022-03-07 10:02 ` Hans de Goede
2022-03-08 14:52 ` Rafael J. Wysocki
2022-03-09 18:15 ` Bjorn Helgaas
2022-03-10 12:28 ` Hans de Goede
2022-03-11 7:52 ` Hans de Goede
2022-03-11 16:24 ` Bjorn Helgaas
2022-03-11 15:13 ` Hans de Goede
2022-03-04 14:15 ` [PATCH 0/3] x86/PCI: Clip only partial E820 overlaps Hans de Goede
2022-03-04 15:21 ` Mika Westerberg
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=20220304035110.988712-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=benoitg@coeus.ca \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=hui.wang@canonical.com \
--cc=juhapekka.heikkila@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=kw@linux.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mingo@redhat.com \
--cc=myron.stowe@redhat.com \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).