public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>, <x86@kernel.org>
Cc: <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>
Subject: [POC] Get acpi table to limit memory scope chosen by KASLR to home SB when "movable_node" is specified
Date: Thu, 3 Aug 2017 16:51:55 +0800	[thread overview]
Message-ID: <20170803085155.GE25014@localhost.localdomain> (raw)

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 OK for community.
If there are any problems, please let me know.
Any comments will be welcome.

Thanks,
Chao Fan

             reply	other threads:[~2017-08-03  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  8:51 Chao Fan [this message]
2017-08-03  8:59 ` [POC] Get acpi table to limit memory scope chosen by KASLR to home SB when "movable_node" is specified Dou Liyang
2017-08-03  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=20170803085155.GE25014@localhost.localdomain \
    --to=fanc.fnst@cn.fujitsu.com \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --cc=dave.jiang@intel.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-kernel@vger.kernel.org \
    --cc=mingo@redhat.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