From: Hans de Goede <hdegoede@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
kernelci-results@groups.io, bot@kernelci.org,
gtucker@collabora.com, linux-pci@vger.kernel.org
Subject: Re: next/master bisection: baseline.login on asus-C523NA-A20057-coral
Date: Mon, 28 Mar 2022 14:54:42 +0200 [thread overview]
Message-ID: <f8e96f8a-c19c-6acd-2f54-688924f491e8@redhat.com> (raw)
In-Reply-To: <Yjzua8Wye/3DHBKx@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
Hi,
On 3/24/22 23:19, Mark Brown wrote:
> On Thu, Mar 24, 2022 at 09:34:30PM +0100, Hans de Goede wrote:
>
>> Mark, if one of use writes a test patch, can you get that Asus machine to boot a
>> kernel build from next + the test patch ?
>
> I can't directly unfortunately as the board is in Collabora's lab but
> Guillaume (who's already CCed) ought to be able to, and I can generally
> prod and try to get that done.
Ok, Guillaume, can you try a kernel with commit 5949965ec9340cfc0e65f7d8a576b660b26e2535
("x86/PCI: Preserve host bridge windows completely covered by E820") + the
attached patch added on top a try on the asus-C523NA-A20057-coral machine please
and see if that makes it boot again ?
Regards,
Hans
[-- Attachment #2: 0001-x86-PCI-Limit-e820-entry-fully-covers-window-check-t.patch --]
[-- Type: text/x-patch, Size: 1809 bytes --]
From b8080a6d2d889847900e1408f71d0c01c73f5c94 Mon Sep 17 00:00:00 2001
From: Hans de Goede <hdegoede@redhat.com>
Date: Mon, 28 Mar 2022 14:47:41 +0200
Subject: [PATCH] x86/PCI: Limit "e820 entry fully covers window" check to non
ISA MMIO addresses
Commit FIXME ("x86/PCI: Preserve host bridge windows completely
covered by E820") added a check to skip e820 table entries which
fully cover a PCI bride's memory window when clipping PCI bridge
memory windows.
This check also caused ISA MMIO windows to not get clipped when
fully covered, which is causing some coreboot based Chromebooks
to not boot.
Modify the fully covered check to not apply to ISA MMIO windows.
Fixes: FIXME ("x86/PCI: Preserve host bridge windows completely covered by E820")
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
arch/x86/kernel/resource.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/resource.c b/arch/x86/kernel/resource.c
index 6be82e16e5f4..d9ec913619c3 100644
--- a/arch/x86/kernel/resource.c
+++ b/arch/x86/kernel/resource.c
@@ -46,8 +46,12 @@ void remove_e820_regions(struct device *dev, struct resource *avail)
* devices. But if it covers the *entire* resource, it's
* more likely just telling us that this is MMIO space, and
* that doesn't need to be removed.
+ * Note this *entire* resource covering check is only
+ * intended for 32 bit memory resources for the 16 bit
+ * isa window we always apply the e820 entries.
*/
- if (e820_start <= avail->start && avail->end <= e820_end) {
+ if (avail->start >= ISA_END_ADDRESS &&
+ e820_start <= avail->start && avail->end <= e820_end) {
dev_info(dev, "resource %pR fully covered by e820 entry [mem %#010Lx-%#010Lx]\n",
avail, e820_start, e820_end);
continue;
--
2.35.1
next prev parent reply other threads:[~2022-03-28 12:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <623c13ec.1c69fb81.8cbdb.5a7a@mx.google.com>
2022-03-24 17:52 ` next/master bisection: baseline.login on asus-C523NA-A20057-coral Mark Brown
2022-03-24 20:34 ` Hans de Goede
2022-03-24 22:19 ` Mark Brown
2022-03-28 12:54 ` Hans de Goede [this message]
2022-03-29 18:44 ` Guillaume Tucker
2022-04-04 19:44 ` Guillaume Tucker
2022-04-05 8:13 ` Hans de Goede
2022-04-05 17:57 ` Bjorn Helgaas
[not found] ` <16E2C910B4947F17.5433@groups.io>
2022-04-04 19:48 ` Guillaume Tucker
2022-03-30 11:35 ` Bjorn Helgaas
2022-04-04 8:45 ` Hans de Goede
2022-04-06 0:19 ` Bjorn Helgaas
2022-04-11 9:54 ` Hans de Goede
2022-04-11 9:57 ` Hans de Goede
2022-03-24 23:08 ` Bjorn Helgaas
2022-03-29 22:14 ` Bjorn Helgaas
2022-04-05 23:53 ` Bjorn Helgaas
2022-04-06 18:59 ` Bjorn Helgaas
2022-04-06 19:37 ` Mark Brown
2022-04-06 20:11 ` Guillaume Tucker
2022-04-07 15:17 ` Denys Fedoryshchenko
2022-04-06 20:56 ` Guenter Roeck
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=f8e96f8a-c19c-6acd-2f54-688924f491e8@redhat.com \
--to=hdegoede@redhat.com \
--cc=bhelgaas@google.com \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=gtucker@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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.