Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	Jonathan Cavitt <jonathan.cavitt@intel.com>
Subject: Re: [PATCH] drm/xe/configfs: Fix engine class parsing
Date: Wed, 24 Sep 2025 10:28:59 +0200	[thread overview]
Message-ID: <aNOry3gcJ4kqkEvk@black.igk.intel.com> (raw)
In-Reply-To: <z5ajmlwhcqfifll7xenysqh22h6ys5xwv3ec6gswl47zeawr2v@ln4s7ssok74g>

On Tue, Sep 23, 2025 at 10:06:25AM -0500, Lucas De Marchi wrote:
> On Tue, Sep 23, 2025 at 01:33:39PM +0200, Raag Jadav wrote:
> > On Mon, Sep 22, 2025 at 03:12:10PM -0700, Lucas De Marchi wrote:
> > > If mask is NULL, only the engine class should be accepted, so the
> > > pattern string should be completely parsed. This should fix passing e.g.
> > > rcs0 to ctx_restore_post_bb when it's only expecting the engine class.
> > 
> > Should we add to the doc so we don't mix up expectations between different
> > attributes?
> 
> afaics it's already there... it's just the parsing that had a bug for an
> invalid input.
> 
> > 
> > Or do we care about the rest of pattern of mask is NULL? Perhaps it'll
> > allow us to have common expectations between attributes.
> 
> I'm not sure I follow... if mask is NULL, it should only accept the
> engine class. If mask is not null, then it should continue parsing the
> instance (or glob).
> 
> attributes like ctx_restore_post_bb and ctx_restore_mid_bb, use only the
> class, as mentioned in the doc:
> 
>  *      # echo 'rcs cmd 11000001 4F100 DEADBEEF' \                       *

Yes, the "only" part will probably help make it clear, aleast for the folks
who don't have the required "context" :D

Upto you.

Raag

      reply	other threads:[~2025-09-24  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 22:12 [PATCH] drm/xe/configfs: Fix engine class parsing Lucas De Marchi
2025-09-22 22:27 ` Lucas De Marchi
2025-09-22 23:22 ` ✓ CI.KUnit: success for " Patchwork
2025-09-22 23:54 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-23  3:47 ` [PATCH] " Cavitt, Jonathan
2025-09-23  5:51 ` ✓ Xe.CI.Full: success for " Patchwork
2025-09-23 11:33 ` [PATCH] " Raag Jadav
2025-09-23 15:06   ` Lucas De Marchi
2025-09-24  8:28     ` Raag Jadav [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=aNOry3gcJ4kqkEvk@black.igk.intel.com \
    --to=raag.jadav@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=lucas.demarchi@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