Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: mas-tachibana@vf.jp.nec.com, mas-hayashi@tg.jp.nec.com,
	Takuya Nakayama <tak-nakayama@tg.jp.nec.com>
Cc: douly.fnst@cn.fujitsu.com, indou.takao@jp.fujitsu.com,
	kexec@lists.infradead.org
Subject: Re: [PATCH 0/4] Makedumpfile: Add 5-level paging support
Date: Thu, 12 Apr 2018 10:45:21 +0800	[thread overview]
Message-ID: <20180412024521.GO19345@localhost.localdomain> (raw)
In-Reply-To: <20180302054841.22195-1-bhe@redhat.com>

Hi Tachibana, Nakayama,

Ping!

Now 5-level suport on x86 64 has been merged into 4.16, do we have plan
to merge this patchset? Or defer to a certain phase?

Thanks
Baoquan

On 03/02/18 at 01:48pm, Baoquan He wrote:
> Kernel has 5-level paging support and now can support boot-time
> switching between 4/5-level paging mode. This patchset is used to add
> 5-level paging support in makedumpfile.
> 
> A kernel fix is posted to export 'pgtable_l5_enabled' to tell if
> the corrupted kernel is in 5-level paging mode.
> https://patchwork.kernel.org/patch/10253399/
> 
> Patch 0001 and 0004 were made by Dou Liyang. While it doesn't work on
> the latest 5-level code. So add patch 0002 to introduce 'pgtable_l5_enabled'.
> Change and take out the function check_5level_paging() from dou's old
> patch and add it into patch 0003. Except of these, don't touch other
> part of dou's patches.
> 
> Thanks, dou, for the effort!
> 
> Baoquan He (2):
>   Makedumpfile: Add pgtable_l5_enabled to number_table
>   Makedumpfile: Add a new function check_5level_paging()
> 
> Dou Liyang (2):
>   arch/x86_64: Cleanup the address translation of the 4-level page
>     tables
>   arch/x86_64: Add 5-level paging support
> 
>  arch/x86_64.c  | 130 +++++++++++++++++++++++++++++++++++++++++----------------
>  makedumpfile.c |   3 ++
>  makedumpfile.h |  39 +++++++++++------
>  3 files changed, 123 insertions(+), 49 deletions(-)
> 
> -- 
> 2.13.6
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2018-04-12  2:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02  5:48 [PATCH 0/4] Makedumpfile: Add 5-level paging support Baoquan He
2018-03-02  5:48 ` [PATCH 1/4] arch/x86_64: Cleanup the address translation of the 4-level page tables Baoquan He
2018-05-07  7:19   ` Masaki Tachibana
2018-05-07  7:30     ` Dou Liyang
2018-05-07  7:31     ` Baoquan He
2018-03-02  5:48 ` [PATCH 2/4] Makedumpfile: Add pgtable_l5_enabled to number_table Baoquan He
2018-05-07  7:20   ` Masaki Tachibana
2018-05-07  7:33     ` Dou Liyang
2018-03-02  5:48 ` [PATCH 3/4] Makedumpfile: Add a new function check_5level_paging() Baoquan He
2018-05-07  7:21   ` Masaki Tachibana
2018-05-07  8:03     ` Baoquan He
2018-03-02  5:48 ` [PATCH 4/4] arch/x86_64: Add 5-level paging support Baoquan He
2018-05-07  7:22   ` Masaki Tachibana
2018-04-12  2:45 ` Baoquan He [this message]
2018-04-12  4:42   ` [PATCH 0/4] Makedumpfile: " Masaki Tachibana
2018-04-12  4:55     ` 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=20180412024521.GO19345@localhost.localdomain \
    --to=bhe@redhat.com \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=indou.takao@jp.fujitsu.com \
    --cc=kexec@lists.infradead.org \
    --cc=mas-hayashi@tg.jp.nec.com \
    --cc=mas-tachibana@vf.jp.nec.com \
    --cc=tak-nakayama@tg.jp.nec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox