Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Robert Krzemien <robert.krzemien@intel.com>
Subject: Re: [PATCH] drm/xe/oa: Allow reading after disabling OA stream
Date: Wed, 11 Mar 2026 23:52:38 -0700	[thread overview]
Message-ID: <87wlzhwnd5.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <abI/7h8lOy9NFpBX@soc-5CG1426VCC.clients.intel.com>

On Wed, 11 Mar 2026 21:24:14 -0700, Umesh Nerlige Ramappa wrote:
>

Hi Umesh,

> On Wed, Mar 11, 2026 at 02:01:07PM -0700, Ashutosh Dixit wrote:
> > Some OA data might be present in the OA buffer when OA stream is
> > disabled. Allow UMD's to retrieve this data, so that all data till the
> > point when OA stream is disabled can be retrieved.
> >
> > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_oa.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
> > index 72fc4424017bf..f840827960eab 100644
> > --- a/drivers/gpu/drm/xe/xe_oa.c
> > +++ b/drivers/gpu/drm/xe/xe_oa.c
> > @@ -543,8 +543,7 @@ static ssize_t xe_oa_read(struct file *file, char __user *buf,
> >	size_t offset = 0;
> >	int ret;
> >
> > -	/* Can't read from disabled streams */
> > -	if (!stream->enabled || !stream->sample)
> > +	if (!stream->sample)
> >		return -EINVAL;
>
> What if there is no data to be read when the stream was disabled? In polled
> mode, we are probably fine, but in blocking mode, we may just wait forever
> here.

Yes, correct. There is no problem in non-blocking read() (it will return
-EAGAIN if no data). But poll() or blocking read() can block.

However, as far as I see, the responsibility of unblocking the blocked
thread (e.g. by means of a signal) rests with UMD.

Note: blocking read() cannot return 0 (it can, only on EOF, see 'man 2
read' but I don't want to do it because "what is EOF"). Similarly poll()
cannot return if there's no data, UMD will need to specify a timeout in
poll().

Note, KMD release() method will not get called if UMD thread is blocked in
read(). So stream cannot be closed till the blocked thread is unblocked.

I would imagine UMD will use non-blocking read()'s to retrieve data after
stream is disabled, till non-blocking read() returns -EAGAIN. If they don't
use non-blocking read(), they will have to handle the blocked thread using
one of the methods above. There's nothing KMD can do.

Unless you or Robert (Cc'd) can prove otherwise :-)

> >
> >	if (!(file->f_flags & O_NONBLOCK)) {
> > --
> > 2.48.1
> >

  reply	other threads:[~2026-03-12  6:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 21:01 [PATCH] drm/xe/oa: Allow reading after disabling OA stream Ashutosh Dixit
2026-03-11 21:08 ` ✓ CI.KUnit: success for " Patchwork
2026-03-11 22:07 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-12  4:24 ` [PATCH] " Umesh Nerlige Ramappa
2026-03-12  6:52   ` Dixit, Ashutosh [this message]
2026-03-12 12:25     ` Umesh Nerlige Ramappa
2026-03-12 21:16       ` Dixit, Ashutosh
2026-03-12 16:13 ` ✗ Xe.CI.FULL: failure for " Patchwork

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=87wlzhwnd5.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=robert.krzemien@intel.com \
    --cc=umesh.nerlige.ramappa@intel.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