[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <297f4912-907-bb45-75df-a030b0d88a8e@google.com>
Date: Fri, 10 Dec 2021 12:11:02 -0800 (PST)
From: Hugh Dickins <hughd@...gle.com>
To: Borislav Petkov <bp@...en8.de>
cc: Mike Rapoport <rppt@...nel.org>, Juergen Gross <jgross@...e.com>,
John Dorminy <jdorminy@...hat.com>, tip-bot2@...utronix.de,
anjaneya.chagam@...el.com, dan.j.williams@...el.com,
linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org,
stable@...r.kernel.org, x86@...nel.org,
Hugh Dickins <hughd@...gle.com>,
"Patrick J. Volkerding" <volkerdi@...il.com>
Subject: Re: [tip: x86/urgent] x86/boot: Pull up cmdline preparation and
early param parsing
On Fri, 10 Dec 2021, Borislav Petkov wrote:
> On Thu, Dec 09, 2021 at 05:37:42PM +0100, Borislav Petkov wrote:
> > Whatever we do, it needs to be tested by all folks on Cc who already
> > reported regressions, i.e., Anjaneya, Hugh, John and Patrick.
>
> Ok, Mike is busy so here are some patches for testing:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=rc4-boot
>
> I'd appreciate it if folks who reported an issue, verify those.
>
> The first two are reverts which should address the issues with mem=
> folks have reported. And the last one should address Anjaneya's issue.
>
> I guess doing it the way as Mike suggested is cleaner/better.
Yes, mem= works fine for me, on both machines, 64-bit and 32-bit,
thanks; but I'm not exercising the troublesome EFI case at all.
Hugh
Powered by blists - more mailing lists