Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Sai Teja Pottumuttu <sai.teja.pottumuttu@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 1/1] tests/intel/xe_oa: Fetch OA buffer size from observation IOCTL
Date: Thu, 21 Nov 2024 09:13:54 -0800	[thread overview]
Message-ID: <85wmgwjyr1.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <85zflu6c24.wl-ashutosh.dixit@intel.com>

On Tue, 19 Nov 2024 15:25:39 -0800, Dixit, Ashutosh wrote:
>
> On Tue, 19 Nov 2024 01:04:05 -0800, Sai Teja Pottumuttu wrote:
> >
> > Currently, the OA buffer size is hardcoded to 16MB in IGT. The patch
> > refactors it to get the default oa buffer size using
> > DRM_XE_OBSERVATION_IOCTL_INFO ioctl. This way if we decide to increase
> > the default OA buffer size, it wouldn't need IGT modification every time.
> >
> > v2:
> > - Rename the oa_buffer_size global variable [Ashutosh]
> > - Use size_t instead of u64 [Ashutosh]
>
> Looks good now:
>
> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> I will merge this after CI completes. Thanks for the patch :)

Merged!

  reply	other threads:[~2024-11-21 17:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19  9:04 [PATCH i-g-t v2 0/1] tests/intel/xe_oa: Refactors related to OA buffer size Sai Teja Pottumuttu
2024-11-19  9:04 ` [PATCH i-g-t v2 1/1] tests/intel/xe_oa: Fetch OA buffer size from observation IOCTL Sai Teja Pottumuttu
2024-11-19 23:25   ` Dixit, Ashutosh
2024-11-21 17:13     ` Dixit, Ashutosh [this message]
2024-11-19 23:24 ` ✗ CI.xeBAT: failure for tests/intel/xe_oa: Refactors related to OA buffer size (rev2) Patchwork
2024-11-19 23:37 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-20 13:01 ` ✗ CI.xeFULL: failure " 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=85wmgwjyr1.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sai.teja.pottumuttu@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