From: Bjorn Helgaas <helgaas@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"H . Peter Anvin" <hpa@zytor.com>,
linux-pci@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, "Hui Wang" <hui.wang@canonical.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Myron Stowe" <myron.stowe@redhat.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Benoit Grégoire" <benoitg@coeus.ca>,
"Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>
Subject: Re: [PATCH] x86/PCI: Add pci=no_e820 cmdline option to ignore E820 reservations for bridge windows
Date: Fri, 8 Oct 2021 06:01:49 -0500 [thread overview]
Message-ID: <20211008110149.GA1313872@bhelgaas> (raw)
In-Reply-To: <20211007165532.GA1241708@bhelgaas>
[+cc Mika, Benoit, Juha-Pekka]
On Thu, Oct 07, 2021 at 11:55:32AM -0500, Bjorn Helgaas wrote:
> [+cc Hui, Rafael, Myron; this looks like the same issue Hui encountered:
> https://lore.kernel.org/r/20210624095324.34906-1-hui.wang@canonical.com]
Cross reference to another thread about a similar issue:
https://lore.kernel.org/r/20200617164734.84845-1-mika.westerberg@linux.intel.com
Beginning of this thread:
https://lore.kernel.org/r/20211005150956.303707-1-hdegoede@redhat.com
> On Tue, Oct 05, 2021 at 05:09:56PM +0200, Hans de Goede wrote:
> > Some BIOS-es contain a bug where they add addresses which map to system RAM
> > in the PCI bridge memory window returned by the ACPI _CRS method, see
> > commit 4dc2287c1805 ("x86: avoid E820 regions when allocating address
> > space").
> > ...
prev parent reply other threads:[~2021-10-08 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 15:09 [PATCH] x86/PCI: Add pci=no_e820 cmdline option to ignore E820 reservations for bridge windows Hans de Goede
2021-10-05 20:56 ` Randy Dunlap
2021-10-07 16:55 ` Bjorn Helgaas
2021-10-07 18:36 ` Hans de Goede
2021-10-08 11:01 ` Bjorn Helgaas [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=20211008110149.GA1313872@bhelgaas \
--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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox