[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1Fyuh12g/gt3Izn@intel.com>
Date: Thu, 20 Oct 2022 19:09:30 +0300
From: Ville Syrjälä <ville.syrjala@...ux.intel.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Jim Cromie <jim.cromie@...il.com>, daniel.vetter@...ll.ch,
intel-gfx@...ts.freedesktop.org, linux@...musvillemoes.dk,
linux-kernel@...r.kernel.org, amd-gfx@...ts.freedesktop.org,
jbaron@...mai.com, seanpaul@...omium.org,
dri-devel@...ts.freedesktop.org, joe@...ches.com,
intel-gvt-dev@...ts.freedesktop.org
Subject: Re: [PATCH v7 0/9] dyndbg: drm.debug adaptation
On Sat, Sep 24, 2022 at 03:02:34PM +0200, Greg KH wrote:
> On Sun, Sep 11, 2022 at 11:28:43PM -0600, Jim Cromie wrote:
> > hi Greg, Dan, Jason, DRM-folk,
> >
> > heres follow-up to V6:
> > rebased on driver-core/driver-core-next for -v6 applied bits (thanks)
> > rework drm_debug_enabled{_raw,_instrumented,} per Dan.
> >
> > It excludes:
> > nouveau parts (immature)
> > tracefs parts (I missed --to=Steve on v6)
> > split _ddebug_site and de-duplicate experiment (way unready)
> >
> > IOW, its the remaining commits of V6 on which Dan gave his Reviewed-by.
> >
> > If these are good to apply, I'll rebase and repost the rest separately.
>
> All now queued up, thanks.
This stuff broke i915 debugs. When I first load i915 no debug prints are
produced. If I then go fiddle around in /sys/module/drm/parameters/debug
the debug prints start to suddenly work.
--
Ville Syrjälä
Intel
Powered by blists - more mailing lists