From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/8] drm/i915: Fix cmdparser drm.debug
Date: Thu, 02 Jan 2020 10:53:18 +0000 [thread overview]
Message-ID: <157796239857.3681.2122815227159366558@skylake-alporthouse-com> (raw)
In-Reply-To: <87k16atc5m.fsf@intel.com>
Quoting Jani Nikula (2020-01-02 09:56:05)
> On Sat, 07 Dec 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > The cmdparser rejection debug is not for driver development, but for the
> > user, for which we use a plain DRM_DEBUG().
>
> ...
>
> > - DRM_DEBUG_DRIVER("CMD: Abnormal rcs cmd length! 0x%08X\n", cmd_header);
> > + DRM_DEBUG("CMD: Abnormal rcs cmd length! 0x%08X\n", cmd_header);
>
> That's not what the documentation says about the difference between
> DRM_DEBUG and DRM_DEBUG_DRIVER.
The documentation seems to be a misconception.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-02 10:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 17:01 [Intel-gfx] [PATCH 1/8] drm/i915: Fix cmdparser drm.debug Chris Wilson
2019-12-07 17:01 ` [Intel-gfx] [PATCH 2/8] drm/i915: Remove redundant parameters from intel_engine_cmd_parser Chris Wilson
2019-12-11 9:41 ` Joonas Lahtinen
2019-12-07 17:01 ` [Intel-gfx] [PATCH 3/8] drm/i915: Simplify error escape from cmdparser Chris Wilson
2019-12-11 9:44 ` Joonas Lahtinen
2019-12-07 17:01 ` [Intel-gfx] [PATCH 4/8] drm/i915/gem: Tidy up error handling for eb_parse() Chris Wilson
2019-12-11 9:51 ` Joonas Lahtinen
2019-12-07 17:01 ` [Intel-gfx] [PATCH 5/8] drm/i915: Align start for memcpy_from_wc Chris Wilson
2019-12-11 10:03 ` Joonas Lahtinen
2019-12-07 17:01 ` [Intel-gfx] [PATCH 6/8] drm/i915: Prepare gen7 cmdparser for async execution Chris Wilson
2019-12-11 11:27 ` Joonas Lahtinen
2019-12-11 11:46 ` Chris Wilson
2019-12-07 17:01 ` [Intel-gfx] [PATCH 7/8] drm/i915: Asynchronous cmdparser Chris Wilson
2019-12-07 17:17 ` Chris Wilson
2019-12-07 17:18 ` Chris Wilson
2019-12-11 13:16 ` Joonas Lahtinen
2019-12-07 17:01 ` [Intel-gfx] [PATCH 8/8] HAX: Use aliasing-ppgtt for gen7 Chris Wilson
2019-12-07 17:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] drm/i915: Fix cmdparser drm.debug Patchwork
2019-12-07 17:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-07 20:12 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2019-12-11 9:25 ` [Intel-gfx] [PATCH 1/8] " Joonas Lahtinen
2020-01-02 9:56 ` Jani Nikula
2020-01-02 10:53 ` Chris Wilson [this message]
2020-01-02 12:26 ` Jani Nikula
2020-01-02 10:54 ` Chris Wilson
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=157796239857.3681.2122815227159366558@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 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.