[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aDtFy1Fw5HUZtfcc@gmail.com>
Date: Sat, 31 May 2025 20:09:15 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Andy Shevchenko <andy@...nel.org>
Cc: linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...nel.org>,
Borislav Petkov <bp@...en8.de>, Juergen Gross <jgross@...e.com>,
"H . Peter Anvin" <hpa@...or.com>,
Kees Cook <keescook@...omium.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Mike Rapoport <rppt@...nel.org>,
Paul Menzel <pmenzel@...gen.mpg.de>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
David Woodhouse <dwmw@...zon.co.uk>
Subject: Re: [PATCH 09/32] x86/boot/e820: Call the PCI gap a 'gap' in the
boot log printout
* Andy Shevchenko <andy@...nel.org> wrote:
> On Thu, May 15, 2025 at 02:05:25PM +0200, Ingo Molnar wrote:
> > It is a bit weird and inconsistent that the PCI gap is
> > advertised during bootup as 'mem'ory:
> >
> > [mem 0xc0000000-0xfed1bfff] available for PCI devices
> > ^^^
> >
> > It's not really memory, it's a gap that PCI devices can decode
> > and use and they often do not map it to any memory themselves.
> >
> > So advertise it for what it is, a gap:
> >
> > [gap 0xc0000000-0xfed1bfff] available for PCI devices
>
> Why not use word 'range' instead of the 'gap'? This will allow to switch to
> %pra without modifying the output.
Well, it's not a range, it's a gap in the memory map. Why does %pra
dictate details of the output in such a fashion?
Thanks,
Ingo
Powered by blists - more mailing lists