public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@intel.com>
Cc: igt-dev@lists.freedesktop.org, simon.b.lee@intel.com
Subject: Re: [igt-dev] [PATCH] tests: Add a new test for driver/device hot remove
Date: Fri, 29 Mar 2019 12:47:32 +0200	[thread overview]
Message-ID: <20190329104732.GC4038@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190328164719.16602-1-janusz.krzysztofik@intel.com>

On Thu, Mar 28, 2019 at 05:47:19PM +0100, Janusz Krzysztofik wrote:
> Run a dummy load in background to put some workload on a device, then try
> to either remove (unplug) the device from its bus, or unbind the device's
> driver from it, depending on which subtest has been selected.
> 
> The driver hot unbind / device hot unplug operation is expected to succeed
> in a reasonable time, however long timeouts are used to allow kernel
> level timeouts pop up first if any.
> 
> Please note that if running both subtests consecutively, the second one
> is always skipped as the device is no longer available as soon as the
> first subtest is completed.  The most reliable way to run another subtest
> is to reboot the system first, then select next subtest to be run.

This is a requirement that won't fly for CI use. Is the
rebinding/whatever of the device not possible to do? By the test?

Does it also apply to running other test binaries after running the
first subtest? As in, is it just a timing issue?


> +	igt_subtest("unplug") {
> +		igt_spin_t *spin;
> +
> +		/* Verify if a suitable DRM device/driver exists */
> +		igt_skip_on(device < 0);
> +
> +		/* Run background workload */
> +		spin = igt_spin_batch_new(device, .flags = IGT_SPIN_POLL_RUN);


igt_spin_batch_new requires DRIVER_INTEL, doesn't it?


> +		igt_spin_busywait_until_running(spin);
> +
> +		/* Make the device disappear */
> +		igt_set_timeout(60, "Device unplug timeout!");
> +		device_unplug(device);
> +		igt_reset_timeout();
> +
> +		close(device);
> +		device = -1;
> +	}
> +
> +	igt_subtest("unbind") {
> +		igt_spin_t *spin;
> +
> +		/* Verify if a suitable DRM device/driver exists */
> +		igt_skip_on(device < 0);


Ah, I see. The skip if running consecutively is because the previous
subtest closed the fd.

Another fixture before this subtest, get the device plugged back,
reopen driver?



-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-03-29 10:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 16:47 [igt-dev] [PATCH] tests: Add a new test for driver/device hot remove Janusz Krzysztofik
2019-03-28 17:20 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-03-29  3:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-03-29 10:47 ` Petri Latvala [this message]
2019-03-29 12:06   ` [igt-dev] [PATCH] " Krzysztofik, Janusz
2019-04-01  7:22   ` Daniel Vetter
2019-04-01  7:41     ` Daniel Vetter
2019-04-01  8:55     ` Krzysztofik, Janusz
2019-04-01 10:16       ` Petri Latvala
2019-04-02  8:47       ` Daniel Vetter

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=20190329104732.GC4038@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=janusz.krzysztofik@intel.com \
    --cc=simon.b.lee@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