Attachment 9631 Details for Bug 10542 – Mesa debugging output

[patch] Mesa debugging output

i915-vsync-debug.diff (text/plain), 1.45 KB, created by Michel Dänzer on 2007-04-17 03:42:28 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michel Dänzer

Created: 2007-04-17 03:42:28 UTC

Size: 1.45 KB

patch

obsolete

>diff --git a/src/mesa/drivers/dri/i915/intel_context.c b/src/mesa/drivers/dri/i915/intel_context.c
>index d201fcf..464e4fc 100644
>--- a/src/mesa/drivers/dri/i915/intel_context.c
>+++ b/src/mesa/drivers/dri/i915/intel_context.c
>@@ -576,6 +576,14 @@ void intelWindowMoved( intelContextPtr intel )
> 	 }
> 
> 	 if (flags != intel->vblank_flags) {
>+	    if (1 /*INTEL_DEBUG & DEBUG_LOCK*/) {
>+	       if (flags & VBLANK_FLAG_SECONDARY) {
>+		  fprintf(stderr, "Vsync to pipe B\n");
>+	       } else {
>+		  fprintf(stderr, "Vsync to pipe A\n");
>+	       }
>+	    }
>+
> 	    intel->vblank_flags = flags;
> 	    driGetCurrentVBlank(dPriv, intel->vblank_flags, &intel->vbl_seq);
> 	 }
>diff --git a/src/mesa/drivers/dri/i915/intel_context.h b/src/mesa/drivers/dri/i915/intel_context.h
>index 05195e7..baa5883 100644
>--- a/src/mesa/drivers/dri/i915/intel_context.h
>+++ b/src/mesa/drivers/dri/i915/intel_context.h
>@@ -327,10 +327,13 @@ do {							\
>     if ((intel)->swap_scheduled) {			\
>         drmVBlank vbl;					\
>         vbl.request.type = DRM_VBLANK_ABSOLUTE;		\
>+fprintf(stderr, "Waiting for sequence %u on pipe ", (intel)->vbl_seq);\
>         if ((intel)->vblank_flags &			\
>             VBLANK_FLAG_SECONDARY) {			\
>             vbl.request.type |= DRM_VBLANK_SECONDARY;	\
>+fprintf(stderr, "B\n");\
>         }						\
>+else fprintf(stderr, "A\n");			\
>         vbl.request.sequence = (intel)->vbl_seq;	\
>         drmWaitVBlank((intel)->driFd, &vbl);		\
>         (intel)->swap_scheduled = 0;			\

Actions: View | Splinter Review

Attachments on bug 10542: 9500 | 9549 | 9562 | 9563 | 9628 | 9629 | 9630 | 9631

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.