Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 27 Apr 2020 11:04:12 +0200
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
Message-ID: <20200427090412.GA7286@alpha.franken.de>
References: <1587460527-13986-1-git-send-email-sunguoyun@loongson.cn>
 <20200426165441.GA10053@alpha.franken.de>
 <QNNE9Q.WIYO7ZSN6WHE@crapouillou.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <QNNE9Q.WIYO7ZSN6WHE@crapouillou.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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 ]