public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	hpa@zytor.com, mingo@elte.hu, torvalds@linux-foundation.org,
	tglx@linutronix.de
Subject: Re: [Intel-gfx] Ugly patches for stolen reservation
Date: Fri, 26 Jul 2013 00:10:25 +0200	[thread overview]
Message-ID: <20130725221025.GA1998@phenom.ffwll.local> (raw)
In-Reply-To: <20130725131648.561cc63c@jbarnes-desktop>

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@kernel.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

  reply	other threads:[~2013-07-25 22:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 16:37 Ugly patches for stolen reservation Jesse Barnes
2013-07-25 16:37 ` [PATCH 1/2] drm/i915: split PCI IDs out into i915_drm.h v3 Jesse Barnes
2013-07-25 23:06   ` Chris Wilson
2013-07-25 16:37 ` [PATCH 2/2] x86: add early quirk for reserving Intel graphics stolen memory v3 Jesse Barnes
2013-07-25 22:42   ` Chris Wilson
2013-07-25 22:59     ` Chris Wilson
2013-07-25 23:18       ` Jesse Barnes
2013-07-26  8:10   ` [Intel-gfx] " Daniel Vetter
2013-07-26 16:58   ` H. Peter Anvin
2013-07-26 17:12     ` Jesse Barnes
2013-07-25 20:05 ` Ugly patches for stolen reservation Ingo Molnar
2013-07-25 20:16   ` Jesse Barnes
2013-07-25 22:10     ` Daniel Vetter [this message]
2013-07-25 22:42   ` H. Peter Anvin
2013-07-25 23:17     ` Jesse Barnes
2013-07-26  0:49       ` H. Peter Anvin
2013-07-26  0:31     ` Linus Torvalds
2013-07-26  0:48       ` H. Peter Anvin
2013-07-26 17:52         ` [Intel-gfx] " Daniel Vetter
2013-07-26 15:51       ` Jesse Barnes
     [not found] <rddfy5e894xuv6d47gu7hbuh.1374804892449@email.android.com>
2013-07-26  3:31 ` H. Peter Anvin
2013-07-26 15:33   ` Jesse Barnes
2013-07-26 20:24     ` Ingo Molnar
2013-07-26 20:28       ` H. Peter Anvin
2013-07-26 20:45         ` [Intel-gfx] " Daniel Vetter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130725221025.GA1998@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=hpa@zytor.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox