From: Baoquan He <bhe@redhat.com>
To: Chao Fan <fanc.fnst@cn.fujitsu.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: 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 10:26:19 +0800 [thread overview]
Message-ID: <20170904022619.GB30906@x1> (raw)
In-Reply-To: <2895411.GR6mzpbNLk@aspire.rjw.lan>
On 09/04/17 at 12:55am, Rafael J. Wysocki wrote:
> On Sunday, September 3, 2017 4:31:23 PM CEST Chao Fan wrote:
> > KASLR should choose the memory region of immovable node to extract kernel.
> > So get ACPI SRAT table and store the memory region of movable node which
> > kaslr shold avoid.
>
> Please elaborate.
>
> This is far too little information on what problem you are trying to address
> and why you are trying to address it in this particular way.
Agree with Rafael.
Why don't you try specifying those regions in cmdline and process them
in kaslr.c? Your colleague, Liyang has tried this way, just he only
considered the region in the first node. In this way, you don't need to
touch ACPI tables with so many lines of code.
Thanks
Baoquan
next prev parent reply other threads:[~2017-09-04 2:26 UTC|newest]
Thread overview: 9+ 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 22:55 ` Rafael J. Wysocki
2017-09-04 1:44 ` Chao Fan
2017-09-04 2:26 ` Baoquan He [this message]
2017-09-04 3:08 ` Chao Fan
2017-09-04 8:17 ` Dou Liyang
2017-09-04 8:39 ` Baoquan He
2017-09-04 8:52 ` Dou Liyang
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=20170904022619.GB30906@x1 \
--to=bhe@redhat.com \
--cc=arnd@arndb.de \
--cc=dave.jiang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox