From: Daniel Mrzyglod <daniel.t.mrzyglod@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v3 0/5] Remove global igt_global_mmio
Date: Mon, 15 Apr 2019 10:59:32 +0200 [thread overview]
Message-ID: <20190415085937.5110-1-daniel.t.mrzyglod@intel.com> (raw)
This patchset remove global igt_global_mmio pointer and structures.
Motivation for this patch is to move global pointers. Current behaviour
limit number of concurrent PCI device. There is a need to run multiple
devices.
v2: fixed bugs pointed out in review
v3: divide series to more patches - fix bugs
Cc: Katarzyna Dec <katarzyna.dec@intel.com>
Cc: Michal Winiarski <michal.winiarski@intel.com>
Daniel Mrzyglod (4):
lib/igt_device: add igt_device_map_pci_bar_region
lib/intel_mmio: different functions are used for mapping if fd is
known.
lib/intel_mmio: extend read write registers functions by a pointer for
mmaped area
lib/intel_mmio: remove igt_global_mmio and move pointer to mmio_data
structure
Michał Winiarski (1):
lib/igt_device: add igt_device_get_pci_addr by fd
benchmarks/gem_latency.c | 5 +-
benchmarks/gem_wsim.c | 6 +-
lib/igt_device.c | 160 ++++++++++++++++++
lib/igt_device.h | 3 +
lib/intel_io.h | 90 +++++++----
lib/intel_iosf.c | 80 +++++----
lib/intel_mmio.c | 178 ++++++++++----------
tests/i915/gem_exec_latency.c | 7 +-
tests/i915/gem_exec_parse.c | 14 +-
tests/i915/i915_pm_lpsp.c | 9 +-
tools/intel_audio_dump.c | 296 +++++++++++++++++++---------------
tools/intel_backlight.c | 15 +-
tools/intel_display_poller.c | 15 +-
tools/intel_forcewaked.c | 14 +-
tools/intel_gpu_time.c | 11 +-
tools/intel_infoframes.c | 75 ++++-----
tools/intel_l3_parity.c | 14 +-
tools/intel_lid.c | 8 +-
tools/intel_panel_fitter.c | 31 ++--
tools/intel_perf_counters.c | 17 +-
tools/intel_reg.c | 41 +++--
tools/intel_reg_checker.c | 8 +-
tools/intel_watermark.c | 46 +++---
23 files changed, 731 insertions(+), 412 deletions(-)
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-04-15 8:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 8:59 Daniel Mrzyglod [this message]
2019-04-15 8:59 ` [igt-dev] [PATCH i-g-t v3 1/5] lib/igt_device: add igt_device_get_pci_addr by fd Daniel Mrzyglod
2019-04-15 13:24 ` Katarzyna Dec
2019-04-15 15:28 ` Mrzyglod, Daniel T
2019-04-15 8:59 ` [igt-dev] [PATCH i-g-t v3 2/5] lib/igt_device: add igt_device_map_pci_bar_region Daniel Mrzyglod
2019-04-15 13:37 ` Katarzyna Dec
2019-04-15 8:59 ` [igt-dev] [PATCH i-g-t v3 3/5] lib/intel_mmio: different functions are used for mapping if fd is known Daniel Mrzyglod
2019-04-15 13:50 ` Katarzyna Dec
2019-04-15 8:59 ` [igt-dev] [PATCH i-g-t v3 4/5] lib/intel_mmio: extend read write registers functions by a pointer for mmaped area Daniel Mrzyglod
2019-04-17 10:20 ` Katarzyna Dec
2019-04-15 8:59 ` [igt-dev] [PATCH i-g-t v3 5/5] lib/intel_mmio: remove igt_global_mmio and move pointer to mmio_data structure Daniel Mrzyglod
2019-04-17 10:55 ` Katarzyna Dec
2019-04-15 10:34 ` [igt-dev] ✓ Fi.CI.BAT: success for Remove global igt_global_mmio (rev3) Patchwork
2019-04-15 11:33 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190415085937.5110-1-daniel.t.mrzyglod@intel.com \
--to=daniel.t.mrzyglod@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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