linux-kernel - Re: [PATCH] mips/mm: Add page soft dirty tracking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 27 Apr 2020 11:04:12 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Paul Cercueil <paul@...pouillou.net>
Cc:     Guoyun Sun <sunguoyun@...ngson.cn>,
        Paul Burton <paulburton@...nel.org>,
        Daniel Silsby <dansilsby@...il.com>,
        Jiaxun Yang <jiaxun.yang@...goat.com>,
        Dmitry Korotin <dkorotin@...ecomp.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Steven Price <steven.price@....com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Mike Rapoport <rppt@...ux.ibm.com>,
        Anshuman Khandual <anshuman.khandual@....com>,
        linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        TieZhu Yang <yangtiezhu@...ngson.cn>,
        Xuefeng Li <lixuefeng@...ngson.cn>
Subject: Re: [PATCH] mips/mm: Add page soft dirty tracking

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 ]