public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: intel-xe@lists.freedesktop.org, LMKL <linux-kernel@vger.kernel.org>
Subject: Watch queue maintainer? WAS:[RFC PATCH RESEND 1/2] watch_queue: Add a DRM_XE_NOTIFY watch type and export init_watch()
Date: Wed, 18 Mar 2026 20:54:54 +0100	[thread overview]
Message-ID: <749015b83d776d38329034a8e639ef2daa3a3a2a.camel@linux.intel.com> (raw)
In-Reply-To: <20260310155741.87191-2-thomas.hellstrom@linux.intel.com>

Hi Christian,

I saw you relatively recently commited some patches to the
watch_queue implementation. We're drafting the below change that
probably is going to use it but at this time it's only RFC.

Do you think the below would be acceptable? If so could you help acking
for merge once the series as a whole is ready to go?

Any feedback appreciated,

Thanks,
Thomas


On Tue, 2026-03-10 at 16:57 +0100, Thomas Hellström wrote:
> Add a DRM_XE_NOTIFY watch type for asynchronous error notifications
> from the DRM_XE kernel module.
> 
> Also export the init_watch() function for use from kernel drivers.
> Use EXPORT_SYMBOL() to align with other exports from the same file.
> 
> Assisted-by: GitHub Copilot:claude-sonnet-4.6
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
>  include/uapi/linux/watch_queue.h |  3 ++-
>  kernel/watch_queue.c             | 13 ++++++++++---
>  2 files changed, 12 insertions(+), 4 deletions(-)
> 
> diff --git a/include/uapi/linux/watch_queue.h
> b/include/uapi/linux/watch_queue.h
> index c3d8320b5d3a..c800c153989d 100644
> --- a/include/uapi/linux/watch_queue.h
> +++ b/include/uapi/linux/watch_queue.h
> @@ -14,7 +14,8 @@
>  enum watch_notification_type {
>  	WATCH_TYPE_META		= 0,	/* Special record */
>  	WATCH_TYPE_KEY_NOTIFY	= 1,	/* Key change event
> notification */
> -	WATCH_TYPE__NR		= 2
> +	WATCH_TYPE_DRM_XE_NOTIFY	= 2,	/* DRM device event
> notification */
> +	WATCH_TYPE__NR		= 3
>  };
>  
>  enum watch_meta_notification_subtype {
> diff --git a/kernel/watch_queue.c b/kernel/watch_queue.c
> index 538520861e8b..701b5c388808 100644
> --- a/kernel/watch_queue.c
> +++ b/kernel/watch_queue.c
> @@ -445,11 +445,17 @@ static void put_watch(struct watch *watch)
>  }
>  
>  /**
> - * init_watch - Initialise a watch
> + * init_watch() - Initialise a watch subscription
>   * @watch: The watch to initialise.
> - * @wqueue: The queue to assign.
> + * @wqueue: The watch queue (notification pipe) to associate with
> the watch.
>   *
> - * Initialise a watch and set the watch queue.
> + * Initialise a newly allocated watch object and associate it with
> @wqueue.
> + * The caller must subsequently set @watch->id and @watch->info_id
> before
> + * calling add_watch_to_object() to subscribe the watch to a
> notification
> + * source.
> + *
> + * The watch queue reference is held internally; call
> put_watch_queue() if
> + * the watch is not successfully passed to add_watch_to_object().
>   */
>  void init_watch(struct watch *watch, struct watch_queue *wqueue)
>  {
> @@ -458,6 +464,7 @@ void init_watch(struct watch *watch, struct
> watch_queue *wqueue)
>  	INIT_HLIST_NODE(&watch->queue_node);
>  	rcu_assign_pointer(watch->queue, wqueue);
>  }
> +EXPORT_SYMBOL(init_watch);
>  
>  static int add_one_watch(struct watch *watch, struct watch_list
> *wlist, struct watch_queue *wqueue)
>  {

  reply	other threads:[~2026-03-18 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 15:57 [RFC PATCH RESEND 0/2] Xe driver asynchronous notification mechanism Thomas Hellström
2026-03-10 15:57 ` [RFC PATCH RESEND 1/2] watch_queue: Add a DRM_XE_NOTIFY watch type and export init_watch() Thomas Hellström
2026-03-18 19:54   ` Thomas Hellström [this message]
2026-03-10 15:57 ` [RFC PATCH RESEND 2/2] drm/xe: Add watch_queue-based device event notification Thomas Hellström

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=749015b83d776d38329034a8e639ef2daa3a3a2a.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=brauner@kernel.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox