From: Baoquan He <bhe@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: tglx@linutronix.de, hpa@zytor.com, thgarnie@google.com,
kirill.shutemov@linux.intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH v2 2/3] x86/mm/KASLR: Calculate the actual size of vmemmap region
Date: Fri, 21 Sep 2018 10:10:17 +0800 [thread overview]
Message-ID: <20180921021017.GO2555@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20180912063152.GA33500@gmail.com>
On 09/12/18 at 08:31am, Ingo Molnar wrote:
> Would you like to work on this? These would be really nice additions, once the code is cleaned
> up to be maintainable and the pending bug fixes you have are merged.
>
> In terms of patch logistics I'd suggest this ordering:
>
> - documentation fixes
> - simple cleanups
> - fixes
> - enhancements
Sorry, there were some RHEL kernel issues last week, so started this
since yesterday. I have sent out documentation fixes as you suggested in
the first patch series. Next is simple cleanup.
>
> With no more than ~5 patches sent in a series. Feel free to integrate all pending
> boot-memory-map fixes and features as well, we'll figure out the right way to do them as they
> happen - but let's start with the simple stuff first, ok?
>
next prev parent reply other threads:[~2018-09-21 2:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 12:49 [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size Baoquan He
2018-09-09 12:49 ` [PATCH v2 2/3] x86/mm/KASLR: Calculate the actual size of vmemmap region Baoquan He
2018-09-10 6:11 ` Ingo Molnar
2018-09-11 7:30 ` Baoquan He
2018-09-11 7:59 ` Ingo Molnar
2018-09-11 8:18 ` Baoquan He
2018-09-11 9:28 ` Ingo Molnar
2018-09-11 12:08 ` Baoquan He
2018-09-12 3:18 ` Baoquan He
2018-09-12 6:31 ` Ingo Molnar
2018-09-12 9:41 ` Baoquan He
2018-09-12 10:01 ` Ingo Molnar
2018-09-21 2:10 ` Baoquan He [this message]
2018-09-09 12:49 ` [PATCH v2 3/3] mm: Add build time sanity chcek for struct page size Baoquan He
2018-09-10 13:41 ` kbuild test robot
2018-09-11 7:47 ` Baoquan He
2018-09-10 6:18 ` [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size Ingo Molnar
2018-09-11 7:22 ` Baoquan He
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=20180921021017.GO2555@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--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