public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Chris Wilson" <chris@chris-wilson.co.uk>,
	"Paulo Zanoni" <paulo.r.zanoni@intel.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit
Date: Mon, 11 Dec 2017 15:38:45 +0100	[thread overview]
Message-ID: <20171211143845.sq3riyeffl3l5f52@gmail.com> (raw)
In-Reply-To: <20171211121427.26205-2-matthew.auld@intel.com>


* Matthew Auld <matthew.auld@intel.com> wrote:

> From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> 
> To give upcoming SKU BIOSes more flexibility in placing the Intel
> graphics stolen memory, make all variables storing the placement or size
> compatible with full 64 bit range. Also by exporting the stolen region
> as a resource, we can then nuke the duplicated stolen discovery in i915.

I'd suggest splitting this into two parts: the first one does the resource_size_t 
extension, the second one the other change.

Thanks,

	Ingo

  parent reply	other threads:[~2017-12-11 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171211121427.26205-1-matthew.auld@intel.com>
2017-12-11 12:14 ` [PATCH 1/8] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Matthew Auld
2017-12-11 14:33   ` Joonas Lahtinen
2017-12-11 14:38   ` Ingo Molnar [this message]
2017-12-11 12:14 ` [PATCH 2/8] x86/early-quirks: replace the magical increment start values Matthew Auld
2017-12-11 14:39   ` Ingo Molnar

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=20171211143845.sq3riyeffl3l5f52@gmail.com \
    --to=mingo@kernel.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=hpa@zytor.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.auld@intel.com \
    --cc=paulo.r.zanoni@intel.com \
    --cc=tglx@linutronix.de \
    --cc=ville.syrjala@linux.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