From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Ingo Molnar <mingo@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Borislav Petkov <bp@suse.de>, Andi Kleen <ak@linux.intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv6 0/4] x86: 5-level related changes into decompression code<Paste>
Date: Fri, 12 Jan 2018 11:37:57 +0300 [thread overview]
Message-ID: <20180112083757.okwsvdhqaodt2d3u@node.shutemov.name> (raw)
In-Reply-To: <20180108161805.jrpmkcrwlr2rs4sy@gmail.com>
On Mon, Jan 08, 2018 at 05:18:05PM +0100, Ingo Molnar wrote:
>
> * Kirill A. Shutemov <kirill@shutemov.name> wrote:
>
> > On Tue, Dec 12, 2017 at 04:57:35PM +0300, Kirill A. Shutemov wrote:
> > > Here's few changes to x86 decompression code.
> > >
> > > The first patch is pure cosmetic change: it gives file with KASLR helpers
> > > a proper name.
> > >
> > > The last three patches bring support of booting into 5-level paging mode if
> > > a bootloader put the kernel above 4G.
> > >
> > > Patch 2/4 Renames l5_paging_required() into paging_prepare() and change
> > > interface of the function.
> > > Patch 3/4 Handles allocation of space for trampoline and gets it prepared.
> > > Patch 4/4 Gets trampoline used.
> > >
> > > Kirill A. Shutemov (4):
> > > x86/boot/compressed/64: Rename pagetable.c to kaslr_64.c
> > > x86/boot/compressed/64: Introduce paging_prepare()
> > > x86/boot/compressed/64: Prepare trampoline memory
> > > x86/boot/compressed/64: Handle 5-level paging boot if kernel is above
> > > 4G
> >
> > Ingo, does it look fine now?
>
> Yes, it looks structurally much better now - but we first need to address all
> existing regressions before we can move forward.
There's a fix for kdump issue that maintainers are okay about.
Is there any other regression do you have in mind?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2018-01-12 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 13:57 [PATCHv6 0/4] x86: 5-level related changes into decompression code<Paste> Kirill A. Shutemov
2017-12-12 13:57 ` [PATCHv6 1/4] x86/boot/compressed/64: Rename pagetable.c to kaslr_64.c Kirill A. Shutemov
2017-12-12 13:57 ` [PATCHv6 2/4] x86/boot/compressed/64: Introduce paging_prepare() Kirill A. Shutemov
2017-12-12 13:57 ` [PATCHv6 3/4] x86/boot/compressed/64: Prepare trampoline memory Kirill A. Shutemov
2017-12-12 13:57 ` [PATCHv6 4/4] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G Kirill A. Shutemov
2017-12-18 10:10 ` [PATCHv6 0/4] x86: 5-level related changes into decompression code<Paste> Kirill A. Shutemov
2018-01-08 16:18 ` Ingo Molnar
2018-01-12 8:37 ` Kirill A. Shutemov [this message]
2018-01-12 14:10 ` Ingo Molnar
2018-01-12 16:22 ` Kirill A. Shutemov
2018-01-16 10:49 ` Kirill A. Shutemov
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=20180112083757.okwsvdhqaodt2d3u@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=gorcunov@openvz.org \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).