From: Bjorn Helgaas <helgaas@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
"Borislav Petkov" <bp@alien8.de>,
"H . Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>,
"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>,
wse@tuxedocomputers.com
Subject: Re: [PATCH 3/3] x86/PCI: Preserve host bridge windows completely covered by E820
Date: Fri, 4 Mar 2022 12:34:51 -0600 [thread overview]
Message-ID: <20220304183451.GA1046413@bhelgaas> (raw)
In-Reply-To: <86b17447-b285-f6ce-99d8-f2cad01405d5@redhat.com>
On Fri, Mar 04, 2022 at 04:46:11PM +0100, Hans de Goede wrote:
> On 3/4/22 16:32, Bjorn Helgaas wrote:
> > I think what might add useful information would be to always log the
> > EFI "RUN" entries. IIUC, currently the "efi: mem47: ..." lines are
> > only emitted when booting with "efi=debug"?
> >
> > I think the "RUN" lines indicate regions that must be virtually mapped
> > so EFI runtime services can use them, and it seems like it might be
> > more generally useful to always mention them.
>
> I'm not sure about always logging the EFI memmap I agree it might
> be useful sometimes, but it is easy to enable then and the initial
> boot code of the kernel already is pretty "chatty".
Yeah. I didn't mean all of the EFI memmap, just the parts that we're
sharing with firmware. But I guess everybody probably has different
parts of the map they think would be interesting :)
next prev parent reply other threads:[~2022-03-04 18:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 3:51 [PATCH 0/3] x86/PCI: Clip only partial E820 overlaps Bjorn Helgaas
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 [this message]
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=20220304183451.GA1046413@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=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=wse@tuxedocomputers.com \
--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