From: John Harrison <john.c.harrison@intel.com>
To: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915/guc: Fix GuC error capture sizing estimation and reporting
Date: Mon, 3 Oct 2022 18:51:43 -0700 [thread overview]
Message-ID: <669a599a-a5d1-4357-c27c-f3e17bc1b4f5@intel.com> (raw)
In-Reply-To: <e76198c741918fbdcc9a4d6b504c4929007e2a78.camel@intel.com>
On 10/3/2022 17:46, Teres Alexis, Alan Previn wrote:
> So as per the last response and the offline conversation we had we agreed that:
>
> 1. we shall stick with drm_warn( ... maybe too small...) if the allocation didn't meet min_size.
> 2. I'll model for PVC (since its better to look at the spec as opposed to trying to hunt for a free machine with the
> most engines and DSS (for those steering registers that are counted multiple times).
> 3. If #2 yields us with substantial headroom (i.e. a model's PVC would be less than 700K min_size), then lets drop to
> 1MB allocation.
>
> ...alan
Sounds good to me.
John.
>
>
> On Mon, 2022-10-03 at 16:51 -0700, Harrison, John C wrote:
>> On 10/3/2022 14:10, Teres Alexis, Alan Previn wrote:
>>> On Mon, 2022-10-03 at 12:47 -0700, Harrison, John C wrote:
>>>> On 10/3/2022 11:28, Teres Alexis, Alan Previn wrote:
>>>>> On Fri, 2022-09-30 at 15:35 -0700, Harrison, John C wrote:
>>>>>> On 9/30/2022 14:08, Teres Alexis, Alan Previn wrote:
>>>>>>
next prev parent reply other threads:[~2022-10-04 1:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 1:05 [Intel-gfx] [PATCH 0/1] Fix Guc-Err-Capture sizing warning Alan Previn
2022-09-30 1:05 ` [Intel-gfx] [PATCH 1/1] drm/i915/guc: Fix GuC error capture sizing estimation and reporting Alan Previn
2022-09-30 17:48 ` John Harrison
2022-09-30 21:08 ` Teres Alexis, Alan Previn
2022-09-30 22:35 ` John Harrison
2022-10-03 18:28 ` Teres Alexis, Alan Previn
2022-10-03 19:47 ` John Harrison
2022-10-03 21:10 ` Teres Alexis, Alan Previn
2022-10-03 23:51 ` John Harrison
2022-10-04 0:46 ` Teres Alexis, Alan Previn
2022-10-04 1:51 ` John Harrison [this message]
2022-10-05 23:31 ` Teres Alexis, Alan Previn
2022-09-30 2:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fix Guc-Err-Capture sizing warning Patchwork
2022-10-01 3:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=669a599a-a5d1-4357-c27c-f3e17bc1b4f5@intel.com \
--to=john.c.harrison@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@lists.freedesktop.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.