Date: Mon, 11 Dec 2017 15:38:45 +0100
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 =?iso-8859-1?Q?Syrj=E4l=E4?= 
        <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
Message-ID: <20171211143845.sq3riyeffl3l5f52@gmail.com>
References: <20171211121427.26205-1-matthew.auld@intel.com>
 <20171211121427.26205-2-matthew.auld@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171211121427.26205-2-matthew.auld@intel.com>
User-Agent: NeoMutt/20170609 (1.8.3)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 545
Lines: 16


* 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