From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org,
Chris Wilson <chris.p.wilson@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] i915/perf: Make __perf_open() and friends public
Date: Tue, 07 Feb 2023 12:15:26 -0800 [thread overview]
Message-ID: <87zg9pmdup.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <111723403.nniJfEyVGO@jkrzyszt-mobl1.ger.corp.intel.com>
On Tue, 07 Feb 2023 12:04:17 -0800, Janusz Krzysztofik wrote:
>
> Hi Umesh,
>
> On Tuesday, 7 February 2023 20:33:50 CET Umesh Nerlige Ramappa wrote:
> > On Tue, Feb 07, 2023 at 11:25:00AM -0800, Umesh Nerlige Ramappa wrote:
> > >I wouldn't do this. Please keep the changes local to the specific test
> > >that you implemented in your first rev. While it is a good idea to
> > >have the some of the perf capabilities in the library, this is way too
> > >much churn to implement a specific test for the original failure.
> > >Unless multiple IGT subsytems area already dependent on perf APIs to
> > >implement multiple tests, let's not do this.
> > >
> >
> > Also note that the perf library implemented in IGT is not entirely used
> > by IGT tests alone. The library is also linked to GPUvis software. Only
> > a few pieces of reusable code in the perf library is used by IGT tests.
>
> Do you think that my changes will break other users? How?
>
> Also, it looks like there are somehow conflicting expectations from different
> reviewers. Ashutosh wanted the new subtest to be implemented outside of i915/
> perf test. That's why I proposed to extend the library with open/close and
> related helpers, just to avoid code duplication, and I'm about to resend it in
> series with the new subtest implemented inside gem_ctx_exec. Now, after I
> submitted this patch for initial review, you say that a specific test is not
> the way to go. What are you afraid of?
>
> Whose expectations should I try to satisfy in order to have a subtest accepted
> and merged? Or should I just give up and duplicate the code from i915/perf in
> another test? Or maybe you can have a look at the whole series before you
> decide?
Hi Janusz,
I agree with Umesh. Given that here perf is just being used as a 'dummy
workload' let's just duplicate the minimal code required for perf
open/close wherever we are adding the new test. This will keep the real
perf functionality undisturbed for reasons Umesh cited.
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2023-02-07 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:11 [igt-dev] [PATCH i-g-t] i915/perf: Make __perf_open() and friends public Janusz Krzysztofik
2023-02-07 11:38 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-02-07 18:16 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-02-07 19:45 ` Janusz Krzysztofik
2023-02-07 19:25 ` Umesh Nerlige Ramappa
2023-02-07 19:33 ` Umesh Nerlige Ramappa
2023-02-07 20:04 ` Janusz Krzysztofik
2023-02-07 20:15 ` Dixit, Ashutosh [this message]
2023-02-08 10:09 ` Janusz Krzysztofik
2023-02-08 19:34 ` Umesh Nerlige Ramappa
2023-02-09 9:56 ` Janusz Krzysztofik
2023-02-09 18:46 ` Umesh Nerlige Ramappa
2023-02-09 20:23 ` Janusz Krzysztofik
2023-02-08 14:35 ` Kamil Konieczny
2023-02-08 17:53 ` Dixit, Ashutosh
2023-02-08 18:23 ` Janusz Krzysztofik
2023-02-09 6:30 ` Dixit, Ashutosh
2023-02-09 10:02 ` Janusz Krzysztofik
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=87zg9pmdup.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.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.