From: Felix Kuehling <felix.kuehling@amd.com>
To: James Zhu <James.Zhu@amd.com>, amd-gfx@lists.freedesktop.org
Cc: jamesz@amd.com
Subject: Re: [PATCH v4 3/5] drm/amdkfd: set activated flag true when event age unmatchs
Date: Fri, 9 Jun 2023 16:22:52 -0400 [thread overview]
Message-ID: <5936e919-b9b4-067e-4cdb-e818bff865d0@amd.com> (raw)
In-Reply-To: <20230609201328.2350231-1-James.Zhu@amd.com>
On 2023-06-09 16:13, James Zhu wrote:
> Set waiter's activated flag true when event age unmatchs with last_event_age.
>
> -v4: add event type check
>
> Signed-off-by: James Zhu <James.Zhu@amd.com>
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_events.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_events.c b/drivers/gpu/drm/amd/amdkfd/kfd_events.c
> index c7689181cc22..2cc1a7e976f4 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_events.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_events.c
> @@ -41,6 +41,7 @@ struct kfd_event_waiter {
> wait_queue_entry_t wait;
> struct kfd_event *event; /* Event to wait for */
> bool activated; /* Becomes true when event is signaled */
> + bool event_age_enabled; /* set to true when last_event_age is non-zero */
> };
>
> /*
> @@ -797,9 +798,9 @@ static struct kfd_event_waiter *alloc_event_waiters(uint32_t num_events)
>
> static int init_event_waiter(struct kfd_process *p,
> struct kfd_event_waiter *waiter,
> - uint32_t event_id)
> + struct kfd_event_data *event_data)
> {
> - struct kfd_event *ev = lookup_event_by_id(p, event_id);
> + struct kfd_event *ev = lookup_event_by_id(p, event_data->event_id);
>
> if (!ev)
> return -EINVAL;
> @@ -808,6 +809,13 @@ static int init_event_waiter(struct kfd_process *p,
> waiter->event = ev;
> waiter->activated = ev->signaled;
> ev->signaled = ev->signaled && !ev->auto_reset;
> +
> + /* last_event_age = 0 reserved for backward compatible */
> + waiter->event_age_enabled = !!event_data->signal_event_data.last_event_age;
This should also be inside the "if (waiter->event->type ==
KFD_EVENT_TYPE_SIGNAL)". I'd do something like this:
if (waiter->event->type == KFD_EVENT_TYPE_SIGNAL &&
event_data->signal_event_data.last_event_age) {
waiter->event_age_enabled = true;
if (ev->event_age != event_data->signal_event_data.last_event_age)
waiter->activated = true;
}
You don't need WRITE_ONCE here because there can be no concurrent access
before you add the waiter to the wait queue.
Regards,
Felix
> + if (waiter->event->type == KFD_EVENT_TYPE_SIGNAL && waiter->event_age_enabled &&
> + ev->event_age != event_data->signal_event_data.last_event_age)
> + WRITE_ONCE(waiter->activated, true);
> +
> if (!waiter->activated)
> add_wait_queue(&ev->wq, &waiter->wait);
> spin_unlock(&ev->lock);
> @@ -948,8 +956,7 @@ int kfd_wait_on_events(struct kfd_process *p,
> goto out_unlock;
> }
>
> - ret = init_event_waiter(p, &event_waiters[i],
> - event_data.event_id);
> + ret = init_event_waiter(p, &event_waiters[i], &event_data);
> if (ret)
> goto out_unlock;
> }
next prev parent reply other threads:[~2023-06-09 20:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 17:07 [PATCH v3 0/5] new event wait support James Zhu
2023-06-08 17:07 ` [PATCH v3 1/5] drm/amdkfd: add event age tracking James Zhu
2023-06-08 17:07 ` [PATCH v3 2/5] drm/amdkfd: add event_age tracking when receiving interrupt James Zhu
2023-06-08 17:07 ` [PATCH v3 3/5] drm/amdkfd: set activated flag true when event age unmatchs James Zhu
2023-06-09 19:43 ` Felix Kuehling
2023-06-09 19:47 ` James Zhu
2023-06-09 20:13 ` [PATCH v4 " James Zhu
2023-06-09 20:22 ` Felix Kuehling [this message]
2023-06-09 20:27 ` James Zhu
2023-06-09 20:43 ` [PATCH v5 " James Zhu
2023-06-09 22:44 ` Felix Kuehling
2023-06-12 16:19 ` Yat Sin, David
2023-06-12 16:31 ` Felix Kuehling
2023-06-08 17:07 ` [PATCH v3 4/5] drm/amdkfd: update user space last_event_age James Zhu
2023-06-08 17:07 ` [PATCH v3 5/5] drm/amdkfd: bump kfd ioctl minor version for event age availability James Zhu
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=5936e919-b9b4-067e-4cdb-e818bff865d0@amd.com \
--to=felix.kuehling@amd.com \
--cc=James.Zhu@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=jamesz@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox