From: Masayoshi Mizuma <msys.mizuma@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Baoquan He <bhe@redhat.com>,
Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, mike.travis@hpe.com,
sivanich@hpe.com
Subject: Re: [PATCH v3 1/2] x86/mm: Add an option to change the padding used for the physical memory mapping
Date: Thu, 20 Sep 2018 12:28:36 -0400 [thread overview]
Message-ID: <20180920162834.bjpeixsfidqseoeq@gabell> (raw)
In-Reply-To: <alpine.DEB.2.21.1809201127210.3243@nanos.tec.linutronix.de>
On Thu, Sep 20, 2018 at 11:28:47AM +0200, Thomas Gleixner wrote:
> On Wed, 19 Sep 2018, Masayoshi Mizuma wrote:
> > On Wed, Sep 19, 2018 at 02:48:06PM +0200, Ingo Molnar wrote:
>
> > > - Add checking code to the later SRAT case to at least _detect_ bad
> > > padding after the fact.
> > >
> > > We don't utilize RAM with bad padding until that, right?
> >
> > I have an idea as following. Does that make sense?
> >
> > Add a warning message which shows the padding size is not enough
> > for the physical memory mapping and tell to the user about
> > recommended padding size. User can change the padding size in next
> > reboot to add the boot parameter.
>
> Yes, that makes sense because silently failing is bad.
Thanks. I will try to add it.
- Masa
prev parent reply other threads:[~2018-09-20 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 15:11 Masayoshi Mizuma
2018-09-04 15:11 ` [PATCH v3 2/2] docs: kernel-parameters.txt: document rand_mem_physical_padding parameter Masayoshi Mizuma
2018-09-18 13:30 ` [PATCH v3 1/2] x86/mm: Add an option to change the padding used for the physical memory mapping Masayoshi Mizuma
2018-09-19 12:17 ` Ingo Molnar
2018-09-19 12:30 ` Thomas Gleixner
2018-09-19 12:48 ` Ingo Molnar
2018-09-19 14:10 ` Masayoshi Mizuma
2018-09-19 23:05 ` Travis, Mike
2018-09-20 16:26 ` Masayoshi Mizuma
2018-09-20 9:28 ` Thomas Gleixner
2018-09-20 16:28 ` Masayoshi Mizuma [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=20180920162834.bjpeixsfidqseoeq@gabell \
--to=msys.mizuma@gmail.com \
--cc=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.mizuma@jp.fujitsu.com \
--cc=mike.travis@hpe.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=sivanich@hpe.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
all inboxes | Powered by JetHome®