Igt-dev 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: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 08/14] tests/intel/xe_oa: Simplify the buffer-fill test
Date: Tue, 04 Mar 2025 07:11:05 -0800	[thread overview]
Message-ID: <85a5a06dbq.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <87cyextzaf.wl-ashutosh.dixit@intel.com>

On Mon, 03 Mar 2025 16:28:08 -0800, Dixit, Ashutosh wrote:
>
> On Mon, 03 Mar 2025 15:14:56 -0800, Umesh Nerlige Ramappa wrote:
> >
> >  static struct intel_xe_perf_metric_set *metric_set(const struct drm_xe_engine_class_instance *hwe)
> >  {
> > @@ -1092,6 +1093,7 @@ init_sys_info(void)
> >
> >	rc_width = 1920;
> >	rc_height = 1080;
> > +	buffer_fill_size = SZ_16M;
>
> Sorry, missed this earlier. Note that there is a default_oa_buffer_size,
> just below. Can we use that or we need this new buffer_fill_size variable?
>
> The kernel will return a constant default_oa_buffer_size of 16 M (at least
> for now).
>
> We can fix this later too if needed, so not need to spin a new version for
> now for this. We can do this if we see any other reason for a new version,
> till now doesn't look like it.

Sorry, this is not an issue, buffer_fill_size is used to set an OA buffer
size. So presumably it can be reduced for slower platforms.

>
> >	oa_exponent_default = max_oa_exponent_for_period_lte(1000000);
> >
> >	default_oa_buffer_size = get_default_oa_buffer_size(drm_fd);

  reply	other threads:[~2025-03-04 15:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 23:14 [PATCH i-g-t v2 00/14] Some refactor, rewrite and fixes for OA tests Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 01/14] tests/intel/xe_oa: Use static for global variables Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 02/14] tests/intel/xe_oa: Drop unused macro Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 03/14] tests/intel/xe_oa: Use period_ns in max_oa_exponent_for_period_lte Umesh Nerlige Ramappa
2025-03-03 23:38   ` Dixit, Ashutosh
2025-03-03 23:14 ` [PATCH i-g-t v2 04/14] tests/intel/xe_oa: Rename oa_exp_1_millisec to oa_exponent_default Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 05/14] tests/intel/xe_oa: Use default exponent for some tests Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 06/14] tests/intel/xe_oa: Use same render copy width and height across tests Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 07/14] tests/intel/xe_oa: Rewrite the polling small buf test Umesh Nerlige Ramappa
2025-03-04  0:05   ` Dixit, Ashutosh
2025-03-03 23:14 ` [PATCH i-g-t v2 08/14] tests/intel/xe_oa: Simplify the buffer-fill test Umesh Nerlige Ramappa
2025-03-04  0:17   ` Dixit, Ashutosh
2025-03-04  0:28   ` Dixit, Ashutosh
2025-03-04 15:11     ` Dixit, Ashutosh [this message]
2025-03-03 23:14 ` [PATCH i-g-t v2 09/14] tests/intel/xe_oa: Use default buffer size for non-zero reason Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 10/14] tests/intel/xe_oa: Test oa buffer sizes Umesh Nerlige Ramappa
2025-03-03 23:14 ` [PATCH i-g-t v2 11/14] tests/intel/xe_oa: Rewrite enable-disable test Umesh Nerlige Ramappa
2025-03-04  0:51   ` Dixit, Ashutosh
2025-03-04 15:04     ` Dixit, Ashutosh
2025-03-03 23:15 ` [PATCH i-g-t v2 12/14] tests/intel/xe_oa: Enable unprivileged-single-ctx-counters and fix it Umesh Nerlige Ramappa
2025-03-03 23:15 ` [PATCH i-g-t v2 13/14] tests/intel/xe_oa: Fix mmio_trigger_reports testing Umesh Nerlige Ramappa
2025-03-03 23:15 ` [PATCH i-g-t v2 14/14] tests/intel/xe_oa: Set boundaries for OA exponent test Umesh Nerlige Ramappa
2025-03-04  1:56 ` ✓ Xe.CI.BAT: success for Some refactor, rewrite and fixes for OA tests (rev2) Patchwork
2025-03-04  2:09 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-04  6:07 ` ✗ Xe.CI.Full: " 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=85a5a06dbq.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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