All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Katarzyna Dec <katarzyna.dec@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] lib/igt_device: Add information why cannot drop drm master
Date: Mon, 14 May 2018 13:39:19 +0100	[thread overview]
Message-ID: <152630155962.18532.14957894070207895837@mail.alporthouse.com> (raw)
In-Reply-To: <20180514113722.28594-1-katarzyna.dec@intel.com>

Quoting Katarzyna Dec (2018-05-14 12:37:22)
> Let's add additional information to igt_device_drop_master
> in case we try to run tests with e.g. x11 enabled.
> 
> v2: Changed comment and added listing clients.
> 
> Signed-off-by: Katarzyna Dec <katarzyna.dec@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  lib/igt_device.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/igt_device.c b/lib/igt_device.c
> index 8a2dd0e3..b2a0a160 100644
> --- a/lib/igt_device.c
> +++ b/lib/igt_device.c
> @@ -74,5 +74,9 @@ int __igt_device_drop_master(int fd)
>   */
>  void igt_device_drop_master(int fd)
>  {
> -       igt_assert_eq(__igt_device_drop_master(fd), 0);
> +       if (__igt_device_drop_master(fd)) {
> +               igt_debugfs_dump(fd, "clients");
> +               igt_require_f(__igt_device_drop_master(fd) == 0,
> +                             "Failed to drop DRM master.\n");
> +       }

I still stand by this should be an assert.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-05-14 12:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 10:19 [igt-dev] [PATCH i-g-t] lib/igt_device: Add information why cannot drop drm master Katarzyna Dec
2018-05-14 10:44 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-05-14 10:52 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2018-05-14 11:37 ` [igt-dev] [PATCH i-g-t v2] " Katarzyna Dec
2018-05-14 12:39   ` Chris Wilson [this message]
2018-05-14 12:44     ` Chris Wilson
2018-05-14 12:51       ` Katarzyna Dec
2018-05-14 12:51   ` [igt-dev] [PATCH i-g-t v3] " Katarzyna Dec
2018-05-15  7:45     ` Chris Wilson
2018-05-15  8:40     ` [igt-dev] [PATCH i-g-t v4] " Katarzyna Dec
2018-05-15 10:15       ` Chris Wilson
2018-05-15 11:30         ` Chris Wilson
2018-05-14 14:19 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2018-05-14 14:53 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_device: Add information why cannot drop drm master (rev3) Patchwork
2018-05-14 22:32 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-05-15 10:12 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-05-15 11:14 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_device: Add information why cannot drop drm master (rev4) Patchwork
2018-05-15 14:52 ` Patchwork
2018-05-15 16:01 ` [igt-dev] ✓ Fi.CI.IGT: success for lib/igt_device: Add information why cannot drop drm master (rev3) Patchwork
2018-05-15 18:09 ` [igt-dev] ✓ Fi.CI.IGT: success for lib/igt_device: Add information why cannot drop drm master (rev4) Patchwork
2018-05-16  0:40 ` 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=152630155962.18532.14957894070207895837@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=katarzyna.dec@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.