dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
	intel-gfx@lists.freedesktop.org, x86@kernel.org,
	dri-devel@lists.freedesktop.org,
	Matthew Auld <matthew.auld@intel.com>,
	"H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/6] drm/i915: export the stolen region as a resource
Date: Thu, 23 Nov 2017 08:59:43 +0100	[thread overview]
Message-ID: <20171123075943.bubo566x2j7jfxl3@gmail.com> (raw)
In-Reply-To: <1511423284.4641.9.camel@linux.intel.com>


* Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:

> + Dave as a heads-up
> 
> On Thu, 2017-11-23 at 07:17 +0100, Ingo Molnar wrote:
> > * Matthew Auld <matthew.auld@intel.com> wrote:
> > 
> > > We duplicate the stolen discovery code in early-quirks and in i915,
> > > however if we just export the region as a resource from early-quirks we
> > > can nuke the duplication.
> > > 
> > > Suggested-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > > Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > > Cc: Ingo Molnar <mingo@kernel.org>
> > > Cc: H. Peter Anvin <hpa@zytor.com>
> > > Cc: dri-devel@lists.freedesktop.org
> > > Cc: x86@kernel.org
> > > ---
> > >  arch/x86/kernel/early-quirks.c         |   6 ++
> > >  drivers/gpu/drm/i915/i915_gem_gtt.c    |  51 +--------------
> > >  drivers/gpu/drm/i915/i915_gem_stolen.c | 109 +--------------------------------
> > >  include/drm/i915_drm.h                 |   3 +
> > >  4 files changed, 13 insertions(+), 156 deletions(-)
> > 
> > If it's truly identical:
> > 
> >   Acked-by: Ingo Molnar <mingo@kernel.org>
> 
> Are you fine with us merging this together with the rest of the series
> through the DRM tree once it's all reviewed?
> 
> That'd help not requiring so many backmerges.

Yes, sure, feel free - that's also where most of the relevant testing is done for 
the affected hardware.

Thanks,

	Ingo
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-23  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171122211920.20993-1-matthew.auld@intel.com>
2017-11-22 21:19 ` [PATCH 1/6] drm/i915: export the stolen region as a resource Matthew Auld
2017-11-23  6:17   ` Ingo Molnar
2017-11-23  7:48     ` Joonas Lahtinen
2017-11-23  7:59       ` Ingo Molnar [this message]
2017-11-24  7:52   ` Joonas Lahtinen

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=20171123075943.bubo566x2j7jfxl3@gmail.com \
    --to=mingo@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hpa@zytor.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=paulo.r.zanoni@intel.com \
    --cc=x86@kernel.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