Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org,
	Jiao Pengyuan <pengyuan.jiao@intel.com>
Subject: Re: [PATCH v2 1/2] drm/i915: Add perf property support for context HW id
Date: Tue, 25 Jul 2017 12:04:38 +0100	[thread overview]
Message-ID: <067533ac-926a-29dc-dfa2-02089a5ccc39@intel.com> (raw)
In-Reply-To: <20170725042627.3lam656etitdiq4v@zhen-hp.sh.intel.com>

On 25/07/17 05:26, Zhenyu Wang wrote:
> On 2017.07.21 14:01:01 +0100, Lionel Landwerlin wrote:
>> I think Chris' comments show this isn't actually tested.
> It turned out that's true...so currently Pengyuan just tried to
> filter by exposed vGPU ctx_hw_id with global mode in gputop. Would
> that be ok with you? If yes, then we don't need i915 perf change.
>
If that works for you, it's great.
I kind of like to have the hw_id in userspace too, it's pretty handy to 
debug IGT tests :)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-07-25 11:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19  5:39 [PATCH v2 1/2] drm/i915: Add perf property support for context HW id Zhenyu Wang
2017-07-19  5:39 ` [PATCH v2 2/2] drm/i915/gvt: expose vGPU context hw id Zhenyu Wang
2017-07-19  6:10 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915: Add perf property support for context HW id Patchwork
2017-07-21 10:50 ` [PATCH v2 1/2] " Lionel Landwerlin
2017-07-21 11:04 ` Chris Wilson
2017-07-21 13:01   ` Lionel Landwerlin
2017-07-25  4:26     ` Zhenyu Wang
2017-07-25 11:04       ` Lionel Landwerlin [this message]

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=067533ac-926a-29dc-dfa2-02089a5ccc39@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=pengyuan.jiao@intel.com \
    --cc=zhenyuw@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