From: Baoquan He <bhe@redhat.com>
To: Chao Fan <fanc.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,
yasu.isimatu@gmail.com, indou.takao@jp.fujitsu.com,
lcapitulino@redhat.com, caoj.fnst@cn.fujitsu.com,
douly.fnst@cn.fujitsu.com
Subject: Re: [RFC PATCH 0/4] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory.
Date: Tue, 3 Jul 2018 09:39:02 +0800 [thread overview]
Message-ID: <20180703013902.GC2195@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20180703013235.GA7297@localhost.localdomain>
On 07/03/18 at 09:32am, Chao Fan wrote:
> On Mon, Jul 02, 2018 at 08:18:55PM +0800, Baoquan He wrote:
> >Hi Chao,
> >
> >On 06/12/18 at 04:10pm, Chao Fan wrote:
> >> *** Issues need be discussed
> >> There are several issues I am not quite sure, please help review and
> >> give suggestions:
> >>
> >> 1) In PATCH 1, I copy the structures and functions from ACPI head file,
> >> so that ACPI head file will never been used here. I am not sure
> >> whether it's good to include ACPI head file or use the method in
> >> PATCH 1. If people think we can use ACPI head files directely, I
> >> will remove the PATCH 1.
> >
> >Usaully we try to reuse code even though they are located in different
> >life space. I think it applies to this SRAT handling. Copying ACPI codes
>
> Yes, you are right. But as you said, they are in different life space,
> so I don't have a better method to dig the SRAT table.
> If anyone have a good way or suggestion, please tell me.
I think someone has told a good way, please check
arch/x86/boot/compressed/eboot.c and see what uefi has done.
>
> >to kernel decompressing looks messy. Is there better way to reuse ACPI
> >code and read SRAT table, then get what we need in a simple way?
> >
> >Thanks
> >Baoquan
> >>
> >> ***Test results:
> >> - I did a very simple test, and it can get the memory information in
> >> bios and efi KVM guest machine, and put it by early printk. But no
> >> more tests, so it's with RFC tag.
> >>
> >> Any comments will be welcome.
> >>
> >>
> >> Chao Fan (4):
> >> x86/boot: Add acpitb.h to help parse acpi tables
> >> x86/boot: Add acpitb.c to parse acpi tables
> >> x86/boot/KASLR: Walk srat tables to filter immovable memory
> >> x86/boot/KASLR: Limit kaslr to choosing the immovable memory
> >>
> >> arch/x86/boot/compressed/Makefile | 1 +
> >> arch/x86/boot/compressed/acpitb.c | 245 ++++++++++++++++++++++++++++++
> >> arch/x86/boot/compressed/acpitb.h | 175 +++++++++++++++++++++
> >> arch/x86/boot/compressed/kaslr.c | 120 +++++++++++++--
> >> 4 files changed, 530 insertions(+), 11 deletions(-)
> >> create mode 100644 arch/x86/boot/compressed/acpitb.c
> >> create mode 100644 arch/x86/boot/compressed/acpitb.h
> >>
> >> --
> >> 2.17.0
> >>
> >>
> >>
> >
> >
>
>
next prev parent reply other threads:[~2018-07-03 1:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 8:10 [RFC PATCH 0/4] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory Chao Fan
2018-06-12 8:10 ` [RFC PATCH 1/4] x86/boot: Add acpitb.h to help parse acpi tables Chao Fan
2018-06-12 8:10 ` [RFC PATCH 2/4] x86/boot: Add acpitb.c to " Chao Fan
2018-06-12 8:10 ` [RFC PATCH 3/4] x86/boot/KASLR: Walk srat tables to filter immovable memory Chao Fan
2018-06-12 8:10 ` [RFC PATCH 4/4] x86/boot/KASLR: Limit kaslr to choosing the " Chao Fan
2018-07-02 12:18 ` [RFC PATCH 0/4] x86/boot/KASLR: Parse ACPI table and limit kaslr in " Baoquan He
2018-07-03 1:32 ` Chao Fan
2018-07-03 1:39 ` Baoquan He [this message]
2018-07-03 1:40 ` 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=20180703013902.GC2195@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=keescook@chromium.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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.