From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>, Matthew Auld <matthew.auld@intel.com>
Cc: x86@kernel.org,
Intel graphics driver community testing & development
<intel-gfx@lists.freedesktop.org>,
"H . Peter Anvin" <hpa@zytor.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit
Date: Fri, 24 Nov 2017 12:58:41 +0200 [thread overview]
Message-ID: <1511521121.3566.9.camel@linux.intel.com> (raw)
In-Reply-To: <20171124073547.eibdntn7bjjavcem@gmail.com>
On Fri, 2017-11-24 at 08:35 +0100, Ingo Molnar wrote:
> * Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:
>
> > In preparation for upcoming SKUs, allow more freedom in placement
> > of the Intel graphics stolen memory by BIOS to full 64bit range.
> >
> > Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Matthew Auld <matthew.auld@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: x86@kernel.org
> > ---
> > arch/x86/kernel/early-quirks.c | 75 +++++++++++++++++++++---------------------
> > 1 file changed, 38 insertions(+), 37 deletions(-)
>
> So I'm wondering how this interacts with:
>
> drm/i915: export the stolen region as a resource
I replied in the other mail thread. My suggestion is to squash the
early-quirks portion of that other patch here for a clean split, then
we can iterate purely on the i915 as necessary.
Sorry for confusion :)
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-24 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 7:30 [PATCH] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Joonas Lahtinen
2017-11-24 7:35 ` Ingo Molnar
2017-11-24 10:58 ` Joonas Lahtinen [this message]
2017-11-24 7:50 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-11-24 12:36 ` [PATCH] " Chris Wilson
2017-11-24 13:55 ` Ville Syrjälä
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=1511521121.3566.9.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=mingo@kernel.org \
--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 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.