public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Shuo Liu <shuo.a.liu@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH v4 1/3] drm/i915/gvt: Add gvt_debug in i915_params for GVT-g log classification
Date: Tue, 19 Sep 2017 18:03:37 +0800	[thread overview]
Message-ID: <20170919100337.GA22243@shuo-intel.sh.intel.com> (raw)
In-Reply-To: <1505812288.8679.11.camel@linux.intel.com>

On Tue 19.Sep'17 at 12:11:28 +0300, Joonas Lahtinen wrote:
>The title should begin with "drm/i915:" not "drm/i915/gvt:".
My fault. Will correct it.
>
>On Tue, 2017-09-19 at 15:54 +0800, Shuo Liu wrote:
>
>Commit message is always needed.
OK, will add it.
>
>> Signed-off-by: Shuo Liu <shuo.a.liu@intel.com>
>
><SNIP>
>
>> @@ -65,6 +65,7 @@ struct i915_params i915 __read_mostly = {
>>  	.inject_load_failure = 0,
>>  	.enable_dpcd_backlight = false,
>>  	.enable_gvt = false,
>> +	.debug_gvt = 0,
>
>Let's try to keep the struct ordered.
What's the order? I see it's different with struct definition.
>
>> @@ -257,3 +258,15 @@ struct i915_params i915 __read_mostly = {
>>  module_param_named(enable_gvt, i915.enable_gvt, bool, 0400);
>>  MODULE_PARM_DESC(enable_gvt,
>>  	"Enable support for Intel GVT-g graphics virtualization host support(default:false)");
>> +
>> +module_param_named(debug_gvt, i915.debug_gvt, int, 0600);
>> +MODULE_PARM_DESC(debug_gvt, "Enable GVT-g debug output, where each bit enables a category.\n"
>> +		"\t\tBit 0 (0x01) will enable CORE messages (GVT-g core message)\n"
>> +		"\t\tBit 1 (0x02) will enable IRQ messages (GVT-g interrupt message)\n"
>> +		"\t\tBit 2 (0x04) will enable MM messages (GVT-g memory management message)\n"
>> +		"\t\tBit 3 (0x08) will enable MMIO messages (GVT-g MMIO message)\n"
>> +		"\t\tBit 4 (0x10) will enable DPY messages (GVT-g display message)\n"
>> +		"\t\tBit 5 (0x20) will enable EL messages (GVT-g execlist message)\n"
>> +		"\t\tBit 6 (0x40) will enable SCHED messages (GVT-g schedule message)\n"
>> +		"\t\tBit 7 (0x80) will enable RENDER messages (GVT-g render message)\n"
>> +		"\t\tBit 8 (0x100) will enable CMD messages (GVT-g command message)");
>
>s/message/code/ for the description in braces, like the drm
>counterpart. Or change them to be just "GVT-g core", "GVT-g
>scheduling", "GVT-g commands" etc.
Will change to "code".
>
>One tab indent is enough like mostly used in the file.
OK.

Thanks.
Shuo
>
>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

  reply	other threads:[~2017-09-19 10:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19  7:54 [PATCH v4 1/3] drm/i915/gvt: Add gvt_debug in i915_params for GVT-g log classification Shuo Liu
2017-09-19  7:54 ` [PATCH v4 2/3] drm/i915/gvt: Change log function of kvmgt to common ones Shuo Liu
2017-09-19  7:54 ` [PATCH v4 3/3] drm/i915/gvt: Use debug_gvt to classify GVT-g log messages Shuo Liu
2017-09-19  9:11 ` [PATCH v4 1/3] drm/i915/gvt: Add gvt_debug in i915_params for GVT-g log classification Joonas Lahtinen
2017-09-19 10:03   ` Shuo Liu [this message]
2017-09-19 13:20     ` Joonas Lahtinen
2017-09-19  9:22 ` Chris Wilson
2017-09-19 10:17   ` Shuo Liu
2017-09-19 20:45     ` Zhenyu Wang
2017-09-20  2:21       ` Shuo Liu
2017-09-19 17:18 ` ✗ Fi.CI.BAT: failure for series starting with [v4,1/3] " 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=20170919100337.GA22243@shuo-intel.sh.intel.com \
    --to=shuo.a.liu@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=joonas.lahtinen@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