From: Ramalingam C <ramalingam.c@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] kms_fence_pin_leak: check for availabile fences
Date: Fri, 7 Feb 2020 19:52:04 +0530 [thread overview]
Message-ID: <20200207142204.GG11460@intel.com> (raw)
In-Reply-To: <20200207140829.GZ13686@intel.com>
On 2020-02-07 at 16:08:29 +0200, Ville Syrjälä wrote:
> On Fri, Feb 07, 2020 at 07:26:06PM +0530, Ramalingam C wrote:
> > On 2020-02-06 at 21:26:52 -0800, Ashutosh Dixit wrote:
> > > Need fences to leak fences.
> > >
> > > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > > ---
> > > tests/kms_fence_pin_leak.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/tests/kms_fence_pin_leak.c b/tests/kms_fence_pin_leak.c
> > > index 8c9e10a56..1ac65e8a1 100644
> > > --- a/tests/kms_fence_pin_leak.c
> > > +++ b/tests/kms_fence_pin_leak.c
> > > @@ -200,6 +200,7 @@ igt_simple_main
> > >
> > > data.drm_fd = drm_open_driver_master(DRIVER_INTEL);
> > > igt_require_gem(data.drm_fd);
> > > + igt_require(gem_available_fences(data.drm_fd) > 0);
> > >From documentation, seams this gem_available_fences is Only relevant for pre-gen4.
> > after the gen4 we dont use the fences or we can't use this method to get the fence
> > count?
>
> These days it just returns the total number of fences, so should work
> on everything. There used to be a way userspace could reserve some
> fences for itself (I think for UMS). I believe that's what the
> documentation is referring to. That stuff got removed years ago.
Thanks ville for the details.
With that, this looks good to me for the purpose.
Reviewed-by: Ramalingam C <ramlaingam.c@intel.com>
>
> --
> Ville Syrjälä
> Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-07 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 5:26 [igt-dev] [PATCH i-g-t] kms_fence_pin_leak: check for availabile fences Ashutosh Dixit
2020-02-07 6:04 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-07 13:56 ` [igt-dev] [PATCH i-g-t] " Ramalingam C
2020-02-07 14:08 ` Ville Syrjälä
2020-02-07 14:22 ` Ramalingam C [this message]
2020-02-10 6:18 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2020-02-18 15:55 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_fence_pin_leak: check for availabile fences (rev2) Patchwork
2020-02-19 23:02 ` [igt-dev] ✗ Fi.CI.IGT: 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=20200207142204.GG11460@intel.com \
--to=ramalingam.c@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox