linux-kernel - Re: [git pull] drm fixes + one missed next for 5.16-rc1

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]

Message-ID: <1ff1389b-bf4c-cd09-8bfd-d4303d100eee@linux.intel.com>
Date:   Mon, 15 Nov 2021 08:18:53 +0100
From:   Thomas Hellström 
        <thomas.hellstrom@...ux.intel.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Dave Airlie <airlied@...il.com>
Cc:     Matthew Auld <matthew.auld@...el.com>,
        Ashutosh Dixit <ashutosh.dixit@...el.com>,
        Rodrigo Vivi <rodrigo.vivi@...el.com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm fixes + one missed next for 5.16-rc1


On 11/14/21 22:19, Linus Torvalds wrote:
> On Sun, Nov 14, 2021 at 1:00 PM Dave Airlie <airlied@...il.com> wrote:
>> i915 will no longer be x86-64 only in theory, since Intel now produces
>> PCIe graphics cards using the same hw designs.
> Well, at least in my tree, it still has the "depends on X86", along
> with several other x86-only things (like "select INTEL_GTT", which is
> also x86-only)
>
> So by the time that non-x86 theory becomes reality, hopefully the i915
> people will also have figured out how to do the cache flushing
> properly.
>
> And hopefully that "do it properly" ends up being simply that the
> particular configuration that ends up being portable simply doesn't
> need to do it at all and can statically just not build it,
> sidestepping the issue entirely.
>
> Fingers crossed.

For non-x86 / discrete graphics, plan is only coherent mappings, 
although the "Just not build it" part hasn't been properly figured out 
yet I guess. But point taken.

Thanks,

/Thomas