linux-kernel - Re: [PULL 00/14] Xtensa updates for 4.19

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] [day] [month] [year] [list]

Message-ID: <CAMo8BfL7WpM-o=Hp-sNRiG4ANFA9cSoTrKTRZYjeecNa+b3dFQ@mail.gmail.com>
Date:   Thu, 23 Aug 2018 11:31:02 -0700
From:   Max Filippov <jcmvbkbc@...il.com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-xtensa@...ux-xtensa.org, Chris Zankel <chris@...kel.net>
Subject: Re: [PULL 00/14] Xtensa updates for 4.19

On Thu, Aug 23, 2018 at 8:21 AM, Christoph Hellwig <hch@...radead.org> wrote:
>>       xtensa: platform-specific handling of coherent memory
>
> How is this supposed to be used?  For the nommu version there only
> are __weak stubs, but no actual implementation.

The idea is that nommu xtensa platforms that have two views of the
physical memory may map one of them as cached and the other as
uncached. They will provide implementations for these four functions.

A platform with single view of the physical memory but with CPU that
has region translation still may create two views of the memory.

Both situations are platform-specific as we don't have fixed address
space layout for nommu systems.

I had an example here, but the addresses in this example are incorrect
as I misread the spec, so I didn't add it to the PR:
https://github.com/jcmvbkbc/linux-xtensa/commit/21ec04090f59647e69fb775ae9d447fcc778701e

-- 
Thanks.
-- Max