From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: <linux-kernel@vger.kernel.org>, <x86@kernel.org>, <hpa@zytor.com>,
<tglx@linutronix.de>, <mingo@redhat.com>, <keescook@chromium.org>,
<bhe@redhat.com>, <dyoung@redhat.com>, <arnd@arndb.de>,
<dave.jiang@intel.com>, <indou.takao@jp.fujitsu.com>,
<izumi.taku@jp.fujitsu.com>, "Rafael J.,
Wysocki" <rjw@rjwysocki.net>, "Zheng, Lv" <lv.zheng@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [POC] Get acpi table to limit memory scope chosen by KASLR to home SB when "movable_node" is specified
Date: Thu, 3 Aug 2017 17:03:59 +0800 [thread overview]
Message-ID: <20170803090359.GF25014@localhost.localdomain> (raw)
In-Reply-To: <f894c7cd-9120-f2ea-d25d-8dae3e4243b3@cn.fujitsu.com>
On Thu, Aug 03, 2017 at 04:59:26PM +0800, Dou Liyang wrote:
>Cc ACPI maintainers and mail list
So many thanks.
>
>At 08/03/2017 04:51 PM, Chao Fan wrote:
>> Hi all,
>>
>> Here is an issue about movable_node and KASLR.
>> Currently, KASLR works well with "mem=", by which we can limit the scope of
>> memory chosen by KASLR. But if we use "movable_node" independently without
>> "mem=", we don't know the scope of memory in the home SB, which will cause
>> the memory of hotplug SB may be chosen by KASLR.
>> To solve this problem, I want to do this job:
>> If "movable_node" is specified, try to get the acpi table and find the scope
>> of memory in home SB, then set "mem_limit".
>>
>> The order of getting table is:
>> boot_params
>> \-systab
>> \-efi tables
>> \-rsdp
>> \-rsdt or xsdt
>> \-acpi root table list
>> \-acpi srat mem affinity
>>
I am not sure if it's good to do this job in this period,
so I want to get the feedback of community.
Thanks,
Chao Fan
>> I am not sure if it's OK for community.
>> If there are any problems, please let me know.
>> Any comments will be welcome.
>>
>> Thanks,
>> Chao Fan
>>
>>
>>
prev parent reply other threads:[~2017-08-03 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 8:51 [POC] Get acpi table to limit memory scope chosen by KASLR to home SB when "movable_node" is specified Chao Fan
2017-08-03 8:59 ` Dou Liyang
2017-08-03 9:03 ` Chao Fan [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=20170803090359.GF25014@localhost.localdomain \
--to=fanc.fnst@cn.fujitsu.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=dave.jiang@intel.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=dyoung@redhat.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 \
/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