From: Hugh Dickins <hughd@google.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@amacapital.net>,
Andy Shevchenko <andy@infradead.org>,
Ard Biesheuvel <ardb@kernel.org>, Baoquan He <bhe@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Darren Hart <dvhart@infradead.org>,
Dave Young <dyoung@redhat.com>, Hugh Dickins <hughd@google.com>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Lianbo Jiang <lijiang@redhat.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Randy Dunlap <rdunlap@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-doc@vger.kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/3] x86/setup: always resrve the first 1M of RAM
Date: Tue, 1 Jun 2021 11:10:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.2106011109020.1045@eggly.anvils> (raw)
In-Reply-To: <20210601075354.5149-1-rppt@kernel.org>
On Tue, 1 Jun 2021, Mike Rapoport wrote:
>
> Randy, Hugh, I'd appreciate if you give this a whirl on your old Sandy
> Bridge laptops as it changes again the way trim_snb_memory() works.
Boots and runs fine here, i386 or x86_64: thanks for remembering us!
Hugh
prev parent reply other threads:[~2021-06-01 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 7:53 [PATCH 0/3] x86/setup: always resrve the first 1M of RAM Mike Rapoport
2021-06-01 7:53 ` [PATCH 1/3] x86/setup: always reserve " Mike Rapoport
2021-06-01 9:06 ` Baoquan He
2021-06-01 17:19 ` Mike Rapoport
2021-06-03 17:57 ` Borislav Petkov
2021-07-01 17:15 ` Dave Hansen
2021-07-01 19:45 ` Mike Rapoport
2021-06-01 7:53 ` [PATCH 2/3] x86/setup: remove CONFIG_X86_RESERVE_LOW and reservelow options Mike Rapoport
2021-06-01 7:53 ` [PATCH 3/3] x86/crash: remove crash_reserve_low_1M() Mike Rapoport
2021-06-01 18:10 ` Hugh Dickins [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=alpine.LSU.2.11.2106011109020.1045@eggly.anvils \
--to=hughd@google.com \
--cc=andy@infradead.org \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dvhart@infradead.org \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=lijiang@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).