From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Guoyun Sun <sunguoyun@loongson.cn>,
Paul Burton <paulburton@kernel.org>,
Daniel Silsby <dansilsby@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
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: Mon, 27 Apr 2020 11:04:12 +0200 [thread overview]
Message-ID: <20200427090412.GA7286@alpha.franken.de> (raw)
In-Reply-To: <QNNE9Q.WIYO7ZSN6WHE@crapouillou.net>
On Sun, Apr 26, 2020 at 07:09:26PM +0200, Paul Cercueil wrote:
> >> 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.
>
> I think we'd need to make PTEs 64-bit at some point.
I'm taking patches ;-) Any idea how much performance impact we might
see by this ?
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-27 9:30 UTC|newest]
Thread overview: 7+ 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
2020-04-26 17:09 ` Paul Cercueil
2020-04-27 9:04 ` Thomas Bogendoerfer [this message]
2020-04-26 17:10 ` Jiaxun Yang
2020-04-29 1:41 ` kbuild test robot
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=20200427090412.GA7286@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 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.