linux-kernel - Re: [Intel-gfx] Ugly patches for stolen reservation

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: <20130725221025.GA1998@phenom.ffwll.local>
Date:	Fri, 26 Jul 2013 00:10:25 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Ingo Molnar <mingo@...nel.org>, intel-gfx@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...e.hu,
	torvalds@...ux-foundation.org, tglx@...utronix.de
Subject: Re: [Intel-gfx] Ugly patches for stolen reservation

On Thu, Jul 25, 2013 at 01:16:48PM -0700, Jesse Barnes wrote:
> On Thu, 25 Jul 2013 22:05:51 +0200
> Ingo Molnar <mingo@...nel.org> wrote:
> > > Chris has some patches on top to add a new E820 type so 
> > > we can look up the region later, which removes some 
> > > redundant code in the i915 driver at least.
> > > 
> > > Any comments?  I assume no one likes this, but maybe it's 
> > > just another early quirk we'll have to live with...
> > 
> > No strong feelings against it - my only suggestion would be 
> > to make this more visible - right now it's added as e820 
> > reserved which hides amongst other areas already marked 
> > reserved - would a low-key printk() of the range added make 
> > it more apparent that a kernel quirk activated here?
> 
> Sounds good, I think Chris's patches should satisfy there.  They make
> it a new E820 type so it's clear in /proc/iomem too.

I think it'd be good to get it all in in one go, since with Chris' patches
i915 will also use the detection logic from the quirk code, so more
testing for it. And imo the i915 cleanups shouldn't conflict really with
ongoing work in drm/i915, so could all go in through x86 trees.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/