From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/oa: Call xe_oa_emit_oa_config() with new config when updating config
Date: Thu, 20 Jun 2024 09:16:42 -0700 [thread overview]
Message-ID: <87plsbr3md.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <857cekr2t3.wl-ashutosh.dixit@intel.com>
On Wed, 19 Jun 2024 15:22:00 -0700, Dixit, Ashutosh wrote:
>
> On Wed, 19 Jun 2024 12:28:54 -0700, José Roberto de Souza wrote:
> >
>
> Hi Jose,
>
> > When UMD ask config to be updated, xe_oa_config_locked() was calling
> > xe_oa_emit_oa_config() that would use stream->oa_config but that is
> > only changed to the next oa_config after xe_oa_emit_oa_config() finish.
> > So it was setting the same config for all DRM_XE_PERF_IOCTL_CONFIG
> > calls.
> >
> > Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_oa.c | 11 +++++------
> > 1 file changed, 5 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
> > index 34206e0b6a08e..a2da54d49f1ce 100644
> > --- a/drivers/gpu/drm/xe/xe_oa.c
> > +++ b/drivers/gpu/drm/xe/xe_oa.c
> > @@ -887,9 +887,8 @@ __xe_oa_alloc_config_buffer(struct xe_oa_stream *stream, struct xe_oa_config *oa
> > return ERR_CAST(bb);
> > }
> >
> > -static struct xe_oa_config_bo *xe_oa_alloc_config_buffer(struct xe_oa_stream *stream)
> > +static struct xe_oa_config_bo *xe_oa_alloc_config_buffer(struct xe_oa_stream *stream, struct xe_oa_config *oa_config)
>
> Nice catch and thanks for the patch.
>
> Just fix the reported checkpatch warning here ("line length of 117 exceeds
> 100 columns"). With that this is:
>
> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> I think no need for "Fixes" tag(s) because this will get into the same
> kernel version. Thanks.
I fixed up the checkpatch warning and merged the patch to drm-xe-next.
Thanks once again.
--
Ashutosh
next prev parent reply other threads:[~2024-06-20 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 19:28 [PATCH] drm/xe/oa: Call xe_oa_emit_oa_config() with new config when updating config José Roberto de Souza
2024-06-19 20:12 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-19 20:12 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-19 20:13 ` ✓ CI.KUnit: success " Patchwork
2024-06-19 20:25 ` ✓ CI.Build: " Patchwork
2024-06-19 20:27 ` ✗ CI.Hooks: failure " Patchwork
2024-06-19 20:29 ` ✓ CI.checksparse: success " Patchwork
2024-06-19 20:51 ` ✓ CI.BAT: " Patchwork
2024-06-19 22:22 ` [PATCH] " Dixit, Ashutosh
2024-06-20 16:16 ` Dixit, Ashutosh [this message]
2024-06-20 5:28 ` ✗ 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=87plsbr3md.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@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