From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org, Leo Liu <Leo.Liu@amd.com>,
Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 0/4] device selection && lsgpu
Date: Mon, 2 Dec 2019 14:37:41 +0200 [thread overview]
Message-ID: <20191202123741.qnook2re7bcadvbt@ahiler-desk1.fi.intel.com> (raw)
In-Reply-To: <58d24738-3f84-fcaf-ba74-4719d3d887fc@linux.intel.com>
On Tue, Nov 12, 2019 at 10:14:13AM +0000, Tvrtko Ursulin wrote:
>
> On 24/10/2019 12:05, Arkadiusz Hiler wrote:
> > Hey,
> >
> > This series aims to make running IGT on hosts with multiple GPUs manageable
> > without the need to unload modules / unbind devices.
> >
> > Suggested reviewing order:
> > * lsgpu
> > * igt_core && drm_test changes
> > * implementation internals in igt_device_scan.c
> >
> > Changes since Zbigniew's last revision:
> > * rewritten most of the parts that were using glib
> > * removed multiple filter support - this will be added back when the need
> > arises
> > * we don't second guess the "chipset" of the device and just let the underlying
> > open to fail if it has to
> > * extra looging around opening device when filter is set
> > * sysfs filter now has it's own prefix
> > * no "platform" filter - sysfs should suffice for now, it can be added by
> > someone more knowledgeable if the need arises
> >
> > TODO:
> > * API for opening multiple devices in a single test (e.g. for prime) - I don't
> > want to design this upfront
> >
> > Example usage:
> > $ build/tools/lsgpu
> > sys:/sys/devices/pci0000:00/0000:00:02.0/drm/card0
> > subsystem : drm
> > drm card : /dev/dri/card0
> > parent : sys:/sys/devices/pci0000:00/0000:00:02.0
> >
> > sys:/sys/devices/pci0000:00/0000:00:02.0/drm/renderD128
> > subsystem : drm
> > drm render : /dev/dri/renderD128
> > parent : sys:/sys/devices/pci0000:00/0000:00:02.0
> >
> > sys:/sys/devices/platform/vgem/drm/card1
> > subsystem : drm
> > drm card : /dev/dri/card1
> > parent : sys:/sys/devices/platform/vgem
> >
> > sys:/sys/devices/platform/vgem/drm/renderD129
> > subsystem : drm
> > drm render : /dev/dri/renderD129
> > parent : sys:/sys/devices/platform/vgem
> >
> > sys:/sys/devices/pci0000:00/0000:00:02.0
> > subsystem : pci
> > drm card : /dev/dri/card0
> > drm render : /dev/dri/renderD128
> > vendor : 8086
> > device : 5927
> >
> > sys:/sys/devices/platform/vgem
> > subsystem : platform
> > drm card : /dev/dri/card1
> > drm render : /dev/dri/renderD129
> >
> > $ build/tools/lsgpu -d "sys:/sys/devices/pci0000:00/0000:00:02.0"
> > Notice: Using --device filters
> > === Device filter ===
> > sys:/sys/devices/pci0000:00/0000:00:02.0
> >
> > === Testing device open ===
> > Device detail:
> > subsystem : pci
> > drm card : /dev/dri/card0
> > drm render : /dev/dri/renderD128
> > Device /dev/dri/card0 successfully opened
> > Device /dev/dri/renderD128 successfully opened
> > -------------------------------------------
> >
> > # build/tests/core_auth --run-subtest getclient-simple --device "pci:vendor=intel"
> > IGT-Version: 1.24-g64068440 (x86_64) (Linux: 5.3.7-250.vanilla.knurd.1.fc30.x86_64 x86_64)
> > Starting subtest: getclient-simple
> > Looking for devices to open using filter: pci:vendor=intel
> > Filter matched /dev/dri/card0 | /dev/dri/renderD128
> > Looking for devices to open using filter: pci:vendor=intel
> > Filter matched /dev/dri/card0 | /dev/dri/renderD128 > Subtest getclient-simple: SUCCESS (0.007s)
>
> Looks very usable!
>
> Can I be cheeky and ask if you could also cover the existing tools
> (especially intel_gpu_top (VLK-5588))?
I am happy to do this but I would prefer to do that in the folowup
patches to not bloat this series any more.
https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/51
> Plus I would need a helper to get the selected device PCI string to use with
> i915 PMU? There I'd need to get a string like "0000:01:00.0" since the i915
> PMU registers the device as either:
>
>
> "/sys/bus/event_source/devices/i915" for integrated.
>
> Or:
>
> "/sys/bus/event_source/devices/i915-0000:01:00.0" for discrete.
>
> So I am thinking something like igt_device_get_pci_string() could work for
> lib/igt_perf.c/i915_type_id().
same as above
https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/52
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-12-02 12:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:05 [igt-dev] [PATCH i-g-t 0/4] device selection && lsgpu Arkadiusz Hiler
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 1/4] lib/igt_list: Update, clean-up and document igt_list Arkadiusz Hiler
2019-10-24 11:16 ` Chris Wilson
2019-10-24 11:20 ` Arkadiusz Hiler
2019-10-24 11:23 ` Chris Wilson
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 2/4] Introduce device selection API Arkadiusz Hiler
[not found] ` <20191024164030.GA7823@zkempczy-mobl2>
2019-10-28 13:06 ` Arkadiusz Hiler
2019-11-15 13:31 ` Petri Latvala
2019-11-18 11:55 ` Petri Latvala
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 3/4] Introduce device selection lsgpu tool Arkadiusz Hiler
2019-10-24 13:06 ` Chris Wilson
2019-10-28 11:21 ` Arkadiusz Hiler
2019-11-18 11:58 ` Petri Latvala
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 4/4] Add device selection in IGT Arkadiusz Hiler
2019-11-18 12:14 ` Petri Latvala
2019-11-19 14:18 ` Arkadiusz Hiler
2019-11-20 9:31 ` Petri Latvala
2019-10-24 13:00 ` [igt-dev] ✓ Fi.CI.BAT: success for device selection && lsgpu Patchwork
2019-10-25 17:07 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-11-12 10:14 ` [igt-dev] [PATCH i-g-t 0/4] " Tvrtko Ursulin
2019-12-02 12:37 ` Arkadiusz Hiler [this message]
2019-12-03 13:59 ` Tvrtko Ursulin
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=20191202123741.qnook2re7bcadvbt@ahiler-desk1.fi.intel.com \
--to=arkadiusz.hiler@intel.com \
--cc=Leo.Liu@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=tvrtko.ursulin@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