[patch] libdrm_intel: intel: get rid of the .data section

2013-06-16 Thread Arjan van de Ven
>From 8e61934c3918484bae10d9ff771c93ad1fa73e29 Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 11:12:53 -0700 Subject: [PATCH 2/2] intel: get rid of the .data section head_offset and tail_offset are the only two global variables in the whole library that are no

[Patch] libdrm_intel: Mark large read only local arrays as static const

2013-06-16 Thread Arjan van de Ven
>From 27eef3eba293163a0c2348566d2470978c3f6c0e Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 10:56:35 -0700 Subject: [PATCH 1/2] intel: Mark large read only local arrays as static const In the instruction decoder, various arrays that are local to functions, but are r

[libdrm] intel: get rid of the .data section

2013-06-16 Thread Arjan van de Ven
>From 8e61934c3918484bae10d9ff771c93ad1fa73e29 Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 11:12:53 -0700 Subject: [PATCH 2/2] intel: get rid of the .data section head_offset and tail_offset are the only two global variables in the whole library that are no

[libdrm] intel: Mark large read only local arrays as static const

2013-06-16 Thread Arjan van de Ven
>From 27eef3eba293163a0c2348566d2470978c3f6c0e Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 10:56:35 -0700 Subject: [PATCH 1/2] intel: Mark large read only local arrays as static const In the instruction decoder, various arrays that are local to functions, but are r

[libdrm] intel: get rid of the .data section

2013-06-16 Thread Arjan van de Ven
>From 8e61934c3918484bae10d9ff771c93ad1fa73e29 Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 11:12:53 -0700 Subject: [PATCH 2/2] intel: get rid of the .data section head_offset and tail_offset are the only two global variables in the whole library that are no

[libdrm] intel: Mark large read only local arrays as static const

2013-06-16 Thread Arjan van de Ven
>From 27eef3eba293163a0c2348566d2470978c3f6c0e Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 10:56:35 -0700 Subject: [PATCH 1/2] intel: Mark large read only local arrays as static const In the instruction decoder, various arrays that are local to functions, but are r

[patch] libdrm_intel: intel: get rid of the .data section

2013-06-16 Thread Arjan van de Ven
>From 8e61934c3918484bae10d9ff771c93ad1fa73e29 Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 11:12:53 -0700 Subject: [PATCH 2/2] intel: get rid of the .data section head_offset and tail_offset are the only two global variables in the whole library that are no

[Patch] libdrm_intel: Mark large read only local arrays as static const

2013-06-16 Thread Arjan van de Ven
>From 27eef3eba293163a0c2348566d2470978c3f6c0e Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 16 Jun 2013 10:56:35 -0700 Subject: [PATCH 1/2] intel: Mark large read only local arrays as static const In the instruction decoder, various arrays that are local to functions, but are r

Re: [Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes

2012-09-02 Thread Arjan van de Ven
On 9/1/2012 8:05 PM, Ben Widawsky wrote: > , from a single trace event you should know the current frequency and the > previous frequency. but if you're doing a heavy game or whatever... you may stay at the highest all the time, and I get no information... same for getting stuck or being always l

Re: [Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes

2012-09-02 Thread Arjan van de Ven
On 9/1/2012 6:36 PM, Ben Widawsky wrote: > It depends on what you're trying to measure. I think this patch is quite > useful but I think I'll make you defend your patch now since you're the > maintainer and you took > your own patch and you're shooting down my idea. So please tell me what > Pow

[Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes

2012-09-01 Thread Arjan van de Ven
On 9/1/2012 8:05 PM, Ben Widawsky wrote: > , from a single trace event you should know the current frequency and the > previous frequency. but if you're doing a heavy game or whatever... you may stay at the highest all the time, and I get no information... same for getting stuck or being always l

[Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes

2012-09-01 Thread Arjan van de Ven
On 9/1/2012 6:36 PM, Ben Widawsky wrote: > It depends on what you're trying to measure. I think this patch is quite > useful but I think I'll make you defend your patch now since you're the > maintainer and you took > your own patch and you're shooting down my idea. So please tell me what > Pow

Re: [Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes

2012-09-01 Thread Arjan van de Ven
has >> happened in the past) and hence for integration into powertop and >> similar tools. >> >> Cc: Arjan van de Ven >> Signed-off-by: Daniel Vetter > > I can't help but think it's equally interesting to know when the queue the > work as well. >

[Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes

2012-09-01 Thread Arjan van de Ven
has >> happened in the past) and hence for integration into powertop and >> similar tools. >> >> Cc: Arjan van de Ven >> Signed-off-by: Daniel Vetter > > I can't help but think it's equally interesting to know when the queue the > work as well. >

[PATCH] drm: Make the per-driver file_operations struct const

2011-10-31 Thread Arjan van de Ven
>From fdf1fdebaa00f81de18c227f32f8074c8b352d50 Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 30 Oct 2011 19:06:07 -0700 Subject: [PATCH] drm: Make the per-driver file_operations struct const The DRM layer keeps a copy of struct file_operations inside its big driver struct... wh

[PATCH] drm: Make the per-driver file_operations struct const

2011-10-31 Thread Arjan van de Ven

[PATCH] drm: Make the per-driver file_operations struct const

2011-10-30 Thread Arjan van de Ven
tions field to its own struct, which is then "static const", and just stick a pointer to this into the driver struct, making it more consistent with how the rest of the kernel does this. Signed-off-by: Arjan van de Ven --- drivers/gpu/drm/drm_fops.c|2 +- drivers/gpu/drm/