All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Myron Stowe" <myron.stowe@redhat.com>,
	"Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	"Benoit Grégoire" <benoitg@coeus.ca>,
	"Hui Wang" <hui.wang@canonical.com>,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	"Guilherme G . Piccoli" <gpiccoli@igalia.com>
Subject: Re: [PATCH] x86/PCI: Revert: "Clip only host bridge windows for E820 regions"
Date: Tue, 14 Jun 2022 16:58:35 +0300	[thread overview]
Message-ID: <YqiUC+zvSxxvb0jw@smile.fi.intel.com> (raw)
In-Reply-To: <Yqh+9Ei5BLhKB/da@smile.fi.intel.com>

On Tue, Jun 14, 2022 at 03:28:36PM +0300, Andy Shevchenko wrote:
> On Sun, Jun 12, 2022 at 04:43:25PM +0200, Hans de Goede wrote:
> > Clipping the bridge windows directly from pci_acpi_root_prepare_resources()
> > instead of clipping from arch_remove_reservations(), has a number of
> > unforseen consequences.
> > 
> > If there is an e820 reservation in the middle of a bridge window, then
> > the smallest of the 2 remaining parts of the window will be also clipped
> > off. Where as the previous code would clip regions requested by devices,
> > rather then the entire window, leaving regions which were either entirely
> > above or below a reservation in the middle of the window alone.
> > 
> > E.g. on the Steam Deck this leads to this log message:
> > 
> > acpi PNP0A08:00: clipped [mem 0x80000000-0xf7ffffff window] to [mem 0xa0100000-0xf7ffffff window]
> > 
> > which then gets followed by these log messages:
> > 
> > pci 0000:00:01.2: can't claim BAR 14 [mem 0x80600000-0x806fffff]: no compatible bridge window
> > pci 0000:00:01.3: can't claim BAR 14 [mem 0x80500000-0x805fffff]: no compatible bridge window
> > 
> > and many more of these. Ultimately this leads to the Steam Deck
> > no longer booting properly, so revert the change.
> > 
> > Note this is not a clean revert, this revert keeps the later change
> > to make the clipping dependent on a new pci_use_e820 bool, moving
> > the checking of this bool to arch_remove_reservations().
> 
> It does _not_ fix the Intel MID case. It requires to have my patch applied as well.
> So the difference as I see is the flags checking. I believe that you still need to
> have it in case pci_use_e820 == true. But it might be that I missed an importan
> detail.

Yeah, I missed that I have compiled a tested something else, and not what I was
focused on.

That said, I double checked with your patch and nothing else and v5.19-rc2
based tree works nicely.

Tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-06-14 13:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 14:43 [PATCH] x86/PCI: Revert: "Clip only host bridge windows for E820 regions" Hans de Goede
2022-06-13 23:15 ` Bjorn Helgaas
2022-06-14  8:15   ` Hans de Goede
2022-06-14 15:17     ` Bjorn Helgaas
2022-06-14 15:47       ` Hans de Goede
2022-06-14 22:49         ` Guilherme G. Piccoli
2022-06-14 23:01           ` Bjorn Helgaas
2022-06-14 23:47             ` Keith Busch
2022-06-15 15:11               ` Bjorn Helgaas
2022-06-17 20:27                 ` Keith Busch
2022-06-14 12:28 ` Andy Shevchenko
2022-06-14 13:58   ` Andy Shevchenko [this message]
2022-06-17 19:55 ` Bjorn Helgaas

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=YqiUC+zvSxxvb0jw@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=benoitg@coeus.ca \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=gpiccoli@igalia.com \
    --cc=hdegoede@redhat.com \
    --cc=hpa@zytor.com \
    --cc=hui.wang@canonical.com \
    --cc=juhapekka.heikkila@gmail.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=rafael@kernel.org \
    --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.