From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
pravalika.gurram@intel.com, igt-dev@lists.freedesktop.org,
nishit.sharma@intel.com, himal.prasad.ghimiray@intel.com
Subject: Re: [PATCH v6 2/2] intel-ci: Blocklist compression PAT index for LNL
Date: Mon, 15 Sep 2025 13:39:26 -0700 [thread overview]
Message-ID: <87ms6v78n5.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <871po7k6uq.wl-ashutosh.dixit@intel.com>
On Mon, 15 Sep 2025 09:39:41 -0700, Dixit, Ashutosh wrote:
>
> On Mon, 15 Sep 2025 05:08:29 -0700, Kamil Konieczny wrote:
> >
> > Hi pravalika.gurram,
> > On 2025-09-15 at 16:20:57 +0530, pravalika.gurram@intel.com wrote:
> > > From: Pravalika Gurram <pravalika.gurram@intel.com>
> > >
> > > Madvise does not support compression on LNL.
> > > Therefore, compression-related PAT index
> > > test cases have been blocklisted for this platform.
> > >
> > > Signed-off-by: Pravalika Gurram <pravalika.gurram@intel.com>
> >
> > Acked-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>
> What is the guidance for when we blocklist a test vs. when we skip it,
> using igt_skip or igt_require?
IMO we should skip it in the code, so anyone looking at the code will know
the test doesn't work on LNL, without having to look at the blocklists.
Blocklisting concerns CI, so we may or may not want to blocklist it for CI
(in addition to skipping in code).
>
> >
> > > ---
> > > tests/intel-ci/xe.lnl.core.blocklist.txt | 6 ++++++
> > > 1 file changed, 6 insertions(+)
> > >
> > > diff --git a/tests/intel-ci/xe.lnl.core.blocklist.txt b/tests/intel-ci/xe.lnl.core.blocklist.txt
> > > index 1e69170d8..3a21d7263 100644
> > > --- a/tests/intel-ci/xe.lnl.core.blocklist.txt
> > > +++ b/tests/intel-ci/xe.lnl.core.blocklist.txt
> > > @@ -83,3 +83,9 @@ igt@xe_live_ktest@xe_eudebug
> > > igt@xe_oa@oa-tlb-invalidate
> > > igt@xe_oa@unprivileged-single-ctx-counters
> > > ##################################################################
> > > +# Expected fail as per the current behaviour compression
> > > +# for madvise needs to skipped on LNL
> > > +##################################################################
> > > +igt@xe_exec_system_allocator@pat-index-madvise-pat-idx-wt-.*
> > > +igt@xe_exec_system_allocator@pat-index-madvise-pat-idx-uc-comp-.*
> > > +##################################################################
> > > --
> > > 2.34.1
> > >
next prev parent reply other threads:[~2025-09-15 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 10:50 [PATCH v6 0/2] Add pat-index-madvise pravalika.gurram
2025-09-15 10:50 ` [PATCH v6 1/2] tests/intel/xe_exec_system_allocator: " pravalika.gurram
2025-09-15 10:50 ` [PATCH v6 2/2] intel-ci: Blocklist compression PAT index for LNL pravalika.gurram
2025-09-15 12:08 ` Kamil Konieczny
2025-09-15 16:39 ` Dixit, Ashutosh
2025-09-15 20:39 ` Dixit, Ashutosh [this message]
2025-09-16 10:08 ` Kamil Konieczny
2025-09-15 21:43 ` ✓ Xe.CI.BAT: success for Add pat-index-madvise Patchwork
2025-09-15 21:45 ` ✓ i915.CI.BAT: " Patchwork
2025-09-16 1:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-16 2:47 ` ✗ i915.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=87ms6v78n5.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=nishit.sharma@intel.com \
--cc=pravalika.gurram@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.