All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: Chao Fan <fanc.fnst@cn.fujitsu.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-acpi@vger.kernel.org, hpa@zytor.com, tglx@linutronix.de,
	mingo@redhat.com, keescook@chromium.org, arnd@arndb.de,
	dyoung@redhat.com, dave.jiang@intel.com, lv.zheng@intel.com,
	indou.takao@jp.fujitsu.com, izumi.taku@jp.fujitsu.com,
	yasu.isimatu@gmail.com
Subject: Re: [PATCH v2] kaslr: get ACPI SRAT table to avoid movable memory
Date: Mon, 4 Sep 2017 16:39:14 +0800	[thread overview]
Message-ID: <20170904083914.GD30906@x1> (raw)
In-Reply-To: <4f2f9d6e-8d6e-e518-bcb6-493d898b7341@cn.fujitsu.com>

On 09/04/17 at 04:17pm, Dou Liyang wrote:
> With "movable_node=1024M" option in cmdline, KASLR will can't access
> the node3 memory.

So you have extended the movable_node option from no value specified to
adding a limit value, then why don't you go one step further to extend
it as movable_node=xxx@start. With this, you can eat the cake you have.

My personal opinion, could that other peopel have better idea. But dig
into acpi tables to grab the srat table, that is really not a good idea.

Chao has spent time to know the srat table, maybe he can try to make a
patch with the "movable_node=xxx@start" handling in kaslr.c, let's see
what it looks like.

Thanks
Baoquan

> 
> I am looking for the solution of this. Not find a good way.
> 
> Sometimes, I will remember that proverb:
> 
>   You cannot have your cake and eat it too. :-)
> 
> Thanks,
> 	dou.
> > touch ACPI tables with so many lines of code.
> > 
> > Thanks
> > Baoquan
> > 
> > 
> > 
> 
> 

  reply	other threads:[~2017-09-04  8:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 14:31 [PATCH v2] kaslr: get ACPI SRAT table to avoid movable memory Chao Fan
2017-09-03 14:31 ` Chao Fan
2017-09-03 22:55 ` Rafael J. Wysocki
2017-09-04  1:44   ` Chao Fan
2017-09-04  1:44     ` Chao Fan
2017-09-04  2:26   ` Baoquan He
2017-09-04  3:08     ` Chao Fan
2017-09-04  3:08       ` Chao Fan
2017-09-04  8:17     ` Dou Liyang
2017-09-04  8:17       ` Dou Liyang
2017-09-04  8:39       ` Baoquan He [this message]
2017-09-04  8:52         ` Dou Liyang
2017-09-04  8:52           ` Dou Liyang
2017-09-04  9:03         ` Chao Fan
2017-09-04  9:03           ` Chao Fan

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=20170904083914.GD30906@x1 \
    --to=bhe@redhat.com \
    --cc=arnd@arndb.de \
    --cc=dave.jiang@intel.com \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=dyoung@redhat.com \
    --cc=fanc.fnst@cn.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=indou.takao@jp.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=keescook@chromium.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=mingo@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yasu.isimatu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.