From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Oscar Mateo <oscar.mateo@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/cnl: Do not add an extra page for precaution in the Gen10 LRC size
Date: Tue, 03 Oct 2017 15:25:43 +0300 [thread overview]
Message-ID: <1507033543.4728.51.camel@linux.intel.com> (raw)
In-Reply-To: <1506976313-1144-1-git-send-email-oscar.mateo@intel.com>
On Mon, 2017-10-02 at 13:31 -0700, Oscar Mateo wrote:
> BSpec indicates exactly 16750 DWORDs (17 pages), plus one page for PPHWSP.
Assuming this is;
Bspec: 1383
I'm actually getting 16801 DWORDs by copy-pasting to spreadsheet and
summing up. Are we looking from different places?
Both lead to the same amount of pages, but I'd like the commit message
to be correct for easier double-checking :) With commit message
corrected and the Bspec: tag added (or more correct Bspec: tag
specified), this is;
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
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-10-03 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 20:31 [PATCH] drm/i915/cnl: Do not add an extra page for precaution in the Gen10 LRC size Oscar Mateo
2017-10-02 21:10 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-02 22:31 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-03 12:25 ` Joonas Lahtinen [this message]
2017-10-03 15:46 ` [PATCH] " Oscar Mateo
2017-10-04 10:44 ` Joonas Lahtinen
-- strict thread matches above, loose matches on Subject: below --
2017-10-03 15:49 Oscar Mateo
2017-10-04 15:39 Oscar Mateo
2017-10-05 17:05 ` Chris Wilson
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=1507033543.4728.51.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@intel.com \
--cc=rodrigo.vivi@intel.com \
/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