All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Matthew Auld <matthew.auld@intel.com>
Cc: x86@kernel.org, Paulo Zanoni <paulo.r.zanoni@intel.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"H . Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
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: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 12:14 [PATCH 0/8] make stolen resource centric Matthew Auld
2017-12-11 12:14 ` [PATCH 1/8] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Matthew Auld
2017-12-11 12:14   ` Matthew Auld
2017-12-11 13:29   ` Chris Wilson
2017-12-11 14:33   ` Joonas Lahtinen
2017-12-11 14:38   ` Ingo Molnar [this message]
2017-12-11 14:38     ` Ingo Molnar
2017-12-11 12:14 ` [PATCH 2/8] x86/early-quirks: replace the magical increment start values Matthew Auld
2017-12-11 12:14   ` Matthew Auld
2017-12-11 14:39   ` Ingo Molnar
2017-12-11 12:14 ` [PATCH 3/8] drm/i915: nuke the duplicated stolen discovery Matthew Auld
2017-12-11 12:14 ` [PATCH 4/8] drm/i915: make dsm struct resource centric Matthew Auld
2017-12-11 12:14 ` [PATCH 5/8] drm/i915: make reserved " Matthew Auld
2017-12-11 12:14 ` [PATCH 6/8] drm/i915: make mappable " Matthew Auld
2017-12-11 12:14 ` [PATCH 7/8] drm/i915: give stolen_usable_size a more suitable home Matthew Auld
2017-12-11 12:14 ` [PATCH 8/8] drm/i915: prefer resource_size_t for everything stolen Matthew Auld
2017-12-11 14:01 ` ✓ Fi.CI.BAT: success for make stolen resource centric (rev7) Patchwork
2017-12-11 15:20 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2017-11-24 16:42 [PATCH 0/8] make stolen resource centric Matthew Auld
2017-11-24 16:42 ` [PATCH 1/8] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Matthew Auld

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=hpa@zytor.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.auld@intel.com \
    --cc=paulo.r.zanoni@intel.com \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.