From: "Christian König" <deathsimple@vodafone.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/radeon: add semaphore trace point
Date: Thu, 14 Nov 2013 16:40:55 +0100 [thread overview]
Message-ID: <5284EF07.2010502@vodafone.de> (raw)
In-Reply-To: <CADnq5_OxbCS0sEQu8207c8N2dRRUkApLySqJ0vhCpv-zxgbVOw@mail.gmail.com>
Am 14.11.2013 16:37, schrieb Alex Deucher:
> Added the series to my queue for 3.13.
Please drop [PATCH 3/3] drm/radeon: disable CIK CP semaphores for now.
With the recent discovery that's an alignment issue that doesn't seems
to be necessary any more.
Christian.
>
> Thanks,
>
> Alex
>
> On Tue, Nov 12, 2013 at 6:58 AM, Christian König
> <deathsimple@vodafone.de> wrote:
>> From: Christian König <christian.koenig@amd.com>
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> ---
>> drivers/gpu/drm/radeon/radeon_semaphore.c | 6 +++++-
>> drivers/gpu/drm/radeon/radeon_trace.h | 36 +++++++++++++++++++++++++++++++
>> 2 files changed, 41 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/radeon/radeon_semaphore.c b/drivers/gpu/drm/radeon/radeon_semaphore.c
>> index 8dcc20f..97d73bf 100644
>> --- a/drivers/gpu/drm/radeon/radeon_semaphore.c
>> +++ b/drivers/gpu/drm/radeon/radeon_semaphore.c
>> @@ -29,7 +29,7 @@
>> */
>> #include <drm/drmP.h>
>> #include "radeon.h"
>> -
>> +#include "radeon_trace.h"
>>
>> int radeon_semaphore_create(struct radeon_device *rdev,
>> struct radeon_semaphore **semaphore)
>> @@ -56,6 +56,8 @@ int radeon_semaphore_create(struct radeon_device *rdev,
>> void radeon_semaphore_emit_signal(struct radeon_device *rdev, int ring,
>> struct radeon_semaphore *semaphore)
>> {
>> + trace_radeon_semaphore_signale(ring, semaphore);
>> +
>> --semaphore->waiters;
>> radeon_semaphore_ring_emit(rdev, ring, &rdev->ring[ring], semaphore, false);
>> }
>> @@ -63,6 +65,8 @@ void radeon_semaphore_emit_signal(struct radeon_device *rdev, int ring,
>> void radeon_semaphore_emit_wait(struct radeon_device *rdev, int ring,
>> struct radeon_semaphore *semaphore)
>> {
>> + trace_radeon_semaphore_wait(ring, semaphore);
>> +
>> ++semaphore->waiters;
>> radeon_semaphore_ring_emit(rdev, ring, &rdev->ring[ring], semaphore, true);
>> }
>> diff --git a/drivers/gpu/drm/radeon/radeon_trace.h b/drivers/gpu/drm/radeon/radeon_trace.h
>> index 811bca6..9f0e181 100644
>> --- a/drivers/gpu/drm/radeon/radeon_trace.h
>> +++ b/drivers/gpu/drm/radeon/radeon_trace.h
>> @@ -111,6 +111,42 @@ DEFINE_EVENT(radeon_fence_request, radeon_fence_wait_end,
>> TP_ARGS(dev, seqno)
>> );
>>
>> +DECLARE_EVENT_CLASS(radeon_semaphore_request,
>> +
>> + TP_PROTO(int ring, struct radeon_semaphore *sem),
>> +
>> + TP_ARGS(ring, sem),
>> +
>> + TP_STRUCT__entry(
>> + __field(int, ring)
>> + __field(signed, waiters)
>> + __field(uint64_t, gpu_addr)
>> + ),
>> +
>> + TP_fast_assign(
>> + __entry->ring = ring;
>> + __entry->waiters = sem->waiters;
>> + __entry->gpu_addr = sem->gpu_addr;
>> + ),
>> +
>> + TP_printk("ring=%u, waiters=%d, addr=%010Lx", __entry->ring,
>> + __entry->waiters, __entry->gpu_addr)
>> +);
>> +
>> +DEFINE_EVENT(radeon_semaphore_request, radeon_semaphore_signale,
>> +
>> + TP_PROTO(int ring, struct radeon_semaphore *sem),
>> +
>> + TP_ARGS(ring, sem)
>> +);
>> +
>> +DEFINE_EVENT(radeon_semaphore_request, radeon_semaphore_wait,
>> +
>> + TP_PROTO(int ring, struct radeon_semaphore *sem),
>> +
>> + TP_ARGS(ring, sem)
>> +);
>> +
>> #endif
>>
>> /* This part must be outside protection */
>> --
>> 1.8.1.2
>>
prev parent reply other threads:[~2013-11-14 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 11:58 [PATCH 1/3] drm/radeon: add semaphore trace point Christian König
2013-11-12 11:58 ` [PATCH 2/3] drm/radeon: allow semaphore emission to fail Christian König
2013-11-12 11:58 ` [PATCH 3/3] drm/radeon: disable CIK CP semaphores for now Christian König
2013-11-14 15:37 ` [PATCH 1/3] drm/radeon: add semaphore trace point Alex Deucher
2013-11-14 15:40 ` Christian König [this message]
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=5284EF07.2010502@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/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.