From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Michal Hocko <mhocko@kernel.org>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Sistare <steven.sistare@oracle.com>
Subject: Re: [PATCH v2] x86/mm: use max memory block size on bare metal
Date: Wed, 10 Jun 2020 13:16:32 -0400 [thread overview]
Message-ID: <20200610171632.uiaucnp65tg6xexk@ca-dmjordan1.us.oracle.com> (raw)
In-Reply-To: <0311c2e5-aa27-f59e-cd00-0c51332b73fd@redhat.com>
On Wed, Jun 10, 2020 at 09:30:00AM +0200, David Hildenbrand wrote:
> On 10.06.20 09:20, David Hildenbrand wrote:
> > On 10.06.20 00:54, Daniel Jordan wrote:
> >> @@ -1390,6 +1391,15 @@ static unsigned long probe_memory_block_size(void)
> >> goto done;
> >> }
> >>
> >> + /*
> >> + * Use max block size to minimize overhead on bare metal, where
> >> + * alignment for memory hotplug isn't a concern.
> >> + */
> >> + if (hypervisor_is_type(X86_HYPER_NATIVE)) {
> >> + bz = MAX_BLOCK_SIZE;
> >> + goto done;
> >> + }
> >
> > I'd assume that bioses on physical machines >= 64GB will not align
> > bigger (>= 2GB) DIMMs to something < 2GB.
> >
> > Acked-by: David Hildenbrand <david@redhat.com>
Thanks!
> FTWT, setup_arch() does the init_hypervisor_platform() call. I assume
> that should be early enough.
I checked all the places where x86 uses memory_block_size_bytes(), it looks ok.
next prev parent reply other threads:[~2020-06-10 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 22:54 Daniel Jordan
2020-06-09 23:03 ` Daniel Jordan
2020-06-10 7:20 ` David Hildenbrand
2020-06-10 7:30 ` David Hildenbrand
2020-06-10 17:16 ` Daniel Jordan [this message]
2020-06-11 14:16 ` Dave Hansen
2020-06-11 16:59 ` Daniel Jordan
2020-06-11 17:05 ` Dave Hansen
2020-06-12 3:29 ` Daniel Jordan
2020-06-19 12:07 ` Michal Hocko
2020-06-22 19:17 ` Daniel Jordan
2020-06-26 12:47 ` Michal Hocko
2020-07-08 18:46 ` Daniel Jordan
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=20200610171632.uiaucnp65tg6xexk@ca-dmjordan1.us.oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mhocko@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=peterz@infradead.org \
--cc=steven.sistare@oracle.com \
/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