From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/6] drm/i915: store all subslice masks
Date: Fri, 12 Jan 2018 11:31:17 +0000 [thread overview]
Message-ID: <64a829ac-5573-3544-5e19-4c072388e8fc@intel.com> (raw)
In-Reply-To: <7755a336-30ab-f52f-2008-eff78ebf54ce@linux.intel.com>
On 12/01/18 11:05, Tvrtko Ursulin wrote:
>
> On 12/01/2018 10:58, Lionel Landwerlin wrote:
>> On 12/01/18 10:15, Tvrtko Ursulin wrote:
>
> [snip]
>
>>>
>>>> --- a/drivers/gpu/drm/i915/intel_device_info.c
>>>> +++ b/drivers/gpu/drm/i915/intel_device_info.c
>>>> @@ -80,12 +80,17 @@ void intel_device_info_dump_flags(const struct
>>>> intel_device_info *info,
>>>> static void sseu_dump(const struct sseu_dev_info *sseu, struct
>>>> drm_printer *p)
>>>> {
>>>> + int s;
>>>> +
>>>> drm_printf(p, "slice mask: %04x\n", sseu->slice_mask);
>>>> drm_printf(p, "slice total: %u\n", hweight8(sseu->slice_mask));
>>>> drm_printf(p, "subslice total: %u\n",
>>>> sseu_subslice_total(sseu));
>>>> - drm_printf(p, "subslice mask %04x\n", sseu->subslice_mask);
>>>> - drm_printf(p, "subslice per slice: %u\n",
>>>> - hweight8(sseu->subslice_mask));
>>>> + for (s = 0; s < ARRAY_SIZE(sseu->subslice_mask); s++) {
>>>> + drm_printf(p, "slice%d subslice mask %04x\n",
>>>> + s, sseu->subslice_mask[s]);
>>>> + drm_printf(p, "slice%d subslice per slice: %u\n",
>>>> + s, hweight8(sseu->subslice_mask[s]));
>>>
>>> Cosmetic only but consider condensing this into one line if you
>>> don't have a preference to either.
>>
>> Sure, just conscious about the 80characters.
>
> I wasn't 100% clear here - I meant the kernel log messages, not the
> source code. I think there is no point in logging two lines per slice
> where one only contains a mask, and second a count.
>
> Regards,
>
> Tvrtko
>
Ahaha :)
Okay, done.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-12 12:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 19:53 [PATCH v2 0/6] drm/i915: expose RCS topology to userspace Lionel Landwerlin
2018-01-11 19:53 ` [PATCH v2 1/6] drm/i915: store all subslice masks Lionel Landwerlin
2018-01-12 10:15 ` Tvrtko Ursulin
2018-01-12 10:58 ` Lionel Landwerlin
2018-01-12 11:05 ` Tvrtko Ursulin
2018-01-12 11:31 ` Lionel Landwerlin [this message]
2018-01-12 12:01 ` Tvrtko Ursulin
2018-01-12 13:53 ` Lionel Landwerlin
2018-01-12 17:37 ` Tvrtko Ursulin
2018-01-11 19:53 ` [PATCH v2 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2018-01-11 19:53 ` [PATCH v2 3/6] drm/i915/debugfs: add rcs topology entry Lionel Landwerlin
2018-01-12 10:21 ` Tvrtko Ursulin
2018-01-12 11:02 ` Lionel Landwerlin
2018-01-11 19:53 ` [PATCH v2 4/6] drm/i915: add rcs topology to error state Lionel Landwerlin
2018-01-11 19:53 ` [PATCH v2 5/6] drm/i915: add query uAPI Lionel Landwerlin
2018-01-12 12:06 ` Tvrtko Ursulin
2018-01-11 19:53 ` [PATCH v2 6/6] drm/i915: expose rcs topology through " Lionel Landwerlin
2018-01-12 12:27 ` Tvrtko Ursulin
2018-01-12 14:04 ` Lionel Landwerlin
2018-01-12 10:06 ` ✓ Fi.CI.BAT: success for drm/i915: expose RCS topology to userspace Patchwork
2018-01-12 11:49 ` ✗ Fi.CI.IGT: warning " 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=64a829ac-5573-3544-5e19-4c072388e8fc@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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