From: "Grzegorzek, Dominik" <dominik.grzegorzek@intel.com>
To: "Kempczynski, Zbigniew" <zbigniew.kempczynski@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 2/9] meson: Introduce xe_staging build option
Date: Fri, 26 May 2023 10:59:53 +0000 [thread overview]
Message-ID: <8970c716f621d227d84d4dfc5f2a9ca7ce4a9328.camel@intel.com> (raw)
In-Reply-To: <20230526105100.6wxkiwov2mzyxipa@zkempczy-mobl2>
On Fri, 2023-05-26 at 12:51 +0200, Zbigniew Kempczyński wrote:
> On Wed, May 24, 2023 at 04:29:24PM +0200, Dominik Grzegorzek wrote:
> > There are some major features, which in a current state cannot be merged
> > upstream. A good example here in an EU debugger, which does not
> > meet the requirement of having an opensourced client. While those
> > features are in the development we need a way of providing them
> > validation. So introduce xe_staging build option under which
> > we can keep tests of features that are under haevy development and not
> > yet accepted upstream or not yet completed.
> >
> > Signed-off-by: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
> > Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> > Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> > ---
> > meson.build | 1 +
> > meson_options.txt | 5 +++++
> > tests/meson.build | 16 ++++++++++++++++
> > 3 files changed, 22 insertions(+)
> >
> > diff --git a/meson.build b/meson.build
> > index 1c872cc9c..ae2206d6e 100644
> > --- a/meson.build
> > +++ b/meson.build
> > @@ -86,6 +86,7 @@ build_chamelium = get_option('chamelium')
> > build_docs = get_option('docs')
> > build_tests = not get_option('tests').disabled()
> > build_xe = not get_option('xe_driver').disabled()
> > +build_xe_staging = not get_option('xe_staging').disabled()
> > with_libdrm = get_option('libdrm_drivers')
> >
> > build_info = ['Build type: ' + get_option('buildtype')]
> > diff --git a/meson_options.txt b/meson_options.txt
> > index 7b5a818cb..46ee91fe6 100644
> > --- a/meson_options.txt
> > +++ b/meson_options.txt
> > @@ -46,6 +46,11 @@ option('xe_driver',
> > type : 'feature',
> > description : 'Build tests for Xe driver (experimental)')
> >
> > +option('xe_staging',
> > + type : 'feature',
> > + value : 'disabled',
> > + description : 'Build tests for Xe features that cannot be upstreamed yet (experimental)')
> > +
> > option('libdrm_drivers',
> > type : 'array',
> > value : ['auto'],
> > diff --git a/tests/meson.build b/tests/meson.build
> > index 38f080f7c..8c7055ed9 100644
> > --- a/tests/meson.build
> > +++ b/tests/meson.build
> > @@ -269,6 +269,9 @@ xe_progs = [
> > 'xe_waitfence',
> > ]
> >
> > +xe_staging_progs = [
> > +]
> > +
> > msm_progs = [
> > 'msm_mapping',
> > 'msm_recovery',
> > @@ -330,6 +333,19 @@ if build_xe
> > build_info += 'Xe **experimental** tests enabled.'
> > endif
>
> I got spurious information on 'mesoning':
>
> Message: Xe **experimental** tests enabled.
>
> Configuration looks:
>
> $ meson configure | grep staging
> xe_staging disabled [enabled, disabled, auto] Build tests for Xe features that cannot be upstreamed yet
>
> --
> Zbigniew
The message you pointed, comes from xe_driver param.
If xe_staging is enabled we add 'Work in progress tests enabled.' to that info log.
As I'm looking at it now it could be just "XE staging tests enabled.", will change that!
Regards,
Dominik
>
> >
> > +if build_xe_staging
> > + foreach prog : xe_staging_progs
> > + test_executables += executable(prog,
> > + join_paths('xe/staging', prog + '.c'),
> > + dependencies : test_deps,
> > + install_dir : libexecdir,
> > + install_rpath : libexecdir_rpathdir,
> > + install : true)
> > + test_list += prog
> > + endforeach
> > + build_info += 'Work in progress tests enabled.'
> > +endif
> > +
> > foreach prog : msm_progs
> > test_executables += executable(prog, join_paths('msm', prog + '.c'),
> > dependencies : test_deps,
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2023-05-26 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 14:29 [igt-dev] [RFC v2 i-g-t 0/9] Add initial eudebug coverage Dominik Grzegorzek
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 1/9] xe: sync uapi headers Dominik Grzegorzek
2023-05-26 10:37 ` Zbigniew Kempczyński
2023-05-26 10:57 ` Grzegorzek, Dominik
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 2/9] meson: Introduce xe_staging build option Dominik Grzegorzek
2023-05-26 10:51 ` Zbigniew Kempczyński
2023-05-26 10:59 ` Grzegorzek, Dominik [this message]
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 3/9] xe/staging/xe_eudebug: test eudebug connection Dominik Grzegorzek
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 4/9] lib/staging/xe_eudebug: introduce eu debug testing framework Dominik Grzegorzek
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 5/9] xe/staging/xe_eudebug: test open close events Dominik Grzegorzek
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 6/9] xe/staging/xe_eudebug: exercise read_event ioctl Dominik Grzegorzek
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 7/9] xe/staging/xe_eudebug: add vm events sanity check Dominik Grzegorzek
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 8/9] xe/staging/xe_eudebug: Race discovery against eudebug attach Dominik Grzegorzek
2023-05-24 14:29 ` [igt-dev] [PATCH i-g-t 9/9] xe/staging/xe_eudebug: Add TEST/SUBTEST documentation Dominik Grzegorzek
2023-05-24 16:01 ` [igt-dev] ✓ Fi.CI.BAT: success for Add initial eudebug coverage (rev3) Patchwork
2023-05-25 4:13 ` [igt-dev] ✓ Fi.CI.IGT: " 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=8970c716f621d227d84d4dfc5f2a9ca7ce4a9328.camel@intel.com \
--to=dominik.grzegorzek@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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