From: Ingo Molnar <mingo@kernel.org>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: intel-gfx@lists.freedesktop.org, x86@kernel.org,
linux-kernel@vger.kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH] x86/gpu: GLK uses the same GMS values as SKL
Date: Wed, 25 Jan 2017 08:29:03 +0100 [thread overview]
Message-ID: <20170125072903.GA20432@gmail.com> (raw)
In-Reply-To: <1485283642-14401-1-git-send-email-paulo.r.zanoni@intel.com>
* Paulo Zanoni <paulo.r.zanoni@intel.com> wrote:
> So don't forget to reserve its stolen memory bits.
>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
> Cc: x86@kernel.org
> Reviewed-by: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> ---
> arch/x86/kernel/early-quirks.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Found by code inspection. This is completely untested since I don't have
> GLK hardware.
>
> diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
> index 6a08e25..23c4f1c 100644
> --- a/arch/x86/kernel/early-quirks.c
> +++ b/arch/x86/kernel/early-quirks.c
> @@ -526,6 +526,7 @@ static const struct pci_device_id intel_early_ids[] __initconst = {
> INTEL_SKL_IDS(&gen9_early_ops),
> INTEL_BXT_IDS(&gen9_early_ops),
> INTEL_KBL_IDS(&gen9_early_ops),
> + INTEL_GLK_IDS(&gen9_early_ops),
> };
There's no INTEL_GLK_IDS() upstream - is there any dependency here on other
changes to the i915 GPU driver?
Thanks,
Ingo
next prev parent reply other threads:[~2017-01-25 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 18:47 [PATCH] x86/gpu: GLK uses the same GMS values as SKL Paulo Zanoni
2017-01-25 7:29 ` Ingo Molnar [this message]
2017-01-25 11:31 ` [Intel-gfx] " Jani Nikula
2017-01-25 11:33 ` Jani Nikula
2017-01-25 11:37 ` 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=20170125072903.GA20432@gmail.com \
--to=mingo@kernel.org \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).