public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tools/intel_gpu_top: Include total package power
Date: Tue, 24 Nov 2020 16:01:03 +0000	[thread overview]
Message-ID: <95e7c59a-4b2c-6406-f92d-fed75edea006@linux.intel.com> (raw)
In-Reply-To: <160623299271.28476.1503734847384709621@build.alporthouse.com>


On 24/11/2020 15:49, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2020-11-24 15:30:53)
>>
>> On 24/11/2020 14:19, Chris Wilson wrote:
>>> -static const char *rapl_gpu_power_unit(void)
>>> -{
>>> -     char buf[32];
>>> -
>>> -     if (filename_to_buf(RAPL_EVENT "energy-gpu.unit",
>>> -                         buf, sizeof(buf)) == 0)
>>> -             if (!strcmp(buf, "Joules"))
>>> -                     return strdup("Watts");
>>> -             else
>>> -                     return strdup(buf);
>>
>> We lose this handling of unexpected changes. Hard to decide if that is
>> very important. Should be possible to keep by a simple addition to
>> rapl_parse I think.
> 
> Do you think we need more than a fprintf(stderr) ?
> 
> 	snprintf(buf, sizeof(buf), "events/energy-%s.unit", str);
>          units = igt_sysfs_get(dir, buf);
>          if (units && strcmp(units, "Joules"))
>                  fprintf(stderr, "Unexpected units for RAPL %s: found %s\n",
>                          str, units);
> 	free(units);

That sounds fine to me. "if (!units || strcmp)" probably.

Regards,

Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-11-24 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 14:19 [igt-dev] [PATCH i-g-t] tools/intel_gpu_top: Include total package power Chris Wilson
2020-11-24 15:30 ` Tvrtko Ursulin
2020-11-24 15:49   ` Chris Wilson
2020-11-24 16:01     ` Tvrtko Ursulin [this message]
2020-11-24 15:45 ` [igt-dev] ✓ Fi.CI.BAT: success for tools/intel_gpu_top: Include total package power (rev2) Patchwork
2020-11-24 19:34 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2020-05-20 10:38 [igt-dev] [PATCH i-g-t] tools/intel_gpu_top: Include total package power Chris Wilson
2020-05-20 11:54 ` Tvrtko Ursulin

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=95e7c59a-4b2c-6406-f92d-fed75edea006@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tvrtko.ursulin@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