From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Guoyun Sun <sunguoyun@loongson.cn>
Cc: Paul Burton <paulburton@kernel.org>,
Daniel Silsby <dansilsby@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Paul Cercueil <paul@crapouillou.net>,
Dmitry Korotin <dkorotin@wavecomp.com>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Price <steven.price@arm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
TieZhu Yang <yangtiezhu@loongson.cn>,
Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH] mips/mm: Add page soft dirty tracking
Date: Sun, 26 Apr 2020 18:54:42 +0200 [thread overview]
Message-ID: <20200426165441.GA10053@alpha.franken.de> (raw)
In-Reply-To: <1587460527-13986-1-git-send-email-sunguoyun@loongson.cn>
On Tue, Apr 21, 2020 at 05:15:27PM +0800, Guoyun Sun wrote:
> User space checkpoint and restart tool (CRIU) needs the page's change
> to be soft tracked. This allows to do a pre checkpoint and then dump
> only touched pages.
>
> Signed-off-by: Guoyun Sun <sunguoyun@loongson.cn>
> ---
> arch/mips/Kconfig | 1 +
> arch/mips/include/asm/pgtable-bits.h | 8 ++++--
> arch/mips/include/asm/pgtable.h | 48 ++++++++++++++++++++++++++++++++++--
this breaks all 32bit builds where CPU support RIXI, because it overflows
pgtable_bits.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-04-26 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 9:15 [PATCH] mips/mm: Add page soft dirty tracking Guoyun Sun
2020-04-26 16:54 ` Thomas Bogendoerfer [this message]
2020-04-26 17:09 ` Paul Cercueil
2020-04-27 9:04 ` Thomas Bogendoerfer
2020-04-26 17:10 ` Jiaxun Yang
2020-04-29 1:41 ` kbuild test robot
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=20200426165441.GA10053@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dansilsby@gmail.com \
--cc=dkorotin@wavecomp.com \
--cc=geert@linux-m68k.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=paul@crapouillou.net \
--cc=paulburton@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=steven.price@arm.com \
--cc=sunguoyun@loongson.cn \
--cc=yangtiezhu@loongson.cn \
/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).