From: Daniel Mrzyglod <daniel.t.mrzyglod@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v5 0/5] Remove global igt_global_mmio
Date: Thu, 9 May 2019 14:38:04 +0200 [thread overview]
Message-ID: <20190509123809.15507-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
v4: reword fix bugs
v5: removed patch 03/06 from the previous series due to sugestions
add fd to gem_mappable_aperture_size()
Daniel Mrzyglod (4):
lib/igt_device: add igt_device_map_pci_bar_region
lib/intel_mmio: add pointer for read/write register funtions
lib/intel_mmio: remove igt_global_mmio and move it to mmio_data
lib/ioctl_wrappers: add fd to aperture_mmap
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 | 168 ++++++++++++++++++
lib/igt_device.h | 2 +
lib/intel_io.h | 90 ++++++----
lib/intel_iosf.c | 74 ++++----
lib/intel_mmio.c | 152 ++++++++--------
lib/ioctl_wrappers.c | 12 +-
lib/ioctl_wrappers.h | 2 +-
tests/i915/gem_concurrent_all.c | 12 +-
tests/i915/gem_cpu_reloc.c | 4 +-
tests/i915/gem_exec_latency.c | 7 +-
tests/i915/gem_exec_parse.c | 14 +-
tests/i915/gem_mmap.c | 4 +-
tests/i915/gem_mmap_gtt.c | 10 +-
tests/i915/gem_pwrite.c | 4 +-
tests/i915/gem_shrink.c | 2 +-
tests/i915/i915_pm_lpsp.c | 9 +-
tests/i915/i915_pm_rpm.c | 4 +-
tests/kms_flip.c | 2 +-
tests/prime_mmap.c | 4 +-
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 +++--
34 files changed, 745 insertions(+), 433 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-05-09 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 12:38 Daniel Mrzyglod [this message]
2019-05-09 12:38 ` [igt-dev] [PATCH i-g-t v5 1/5] lib/igt_device: add igt_device_get_pci_addr by fd Daniel Mrzyglod
2019-05-09 12:38 ` [igt-dev] [PATCH i-g-t v5 2/5] lib/igt_device: add igt_device_map_pci_bar_region Daniel Mrzyglod
2019-05-09 12:38 ` [igt-dev] [PATCH i-g-t v5 3/5] lib/intel_mmio: add pointer for read/write register funtions Daniel Mrzyglod
2019-05-09 12:38 ` [igt-dev] [PATCH i-g-t v5 4/5] lib/intel_mmio: remove igt_global_mmio and move it to mmio_data Daniel Mrzyglod
2019-05-09 13:52 ` Jani Nikula
2019-05-09 12:38 ` [igt-dev] [PATCH i-g-t v5 5/5] lib/ioctl_wrappers: add fd to aperture_mmap Daniel Mrzyglod
2019-05-09 14:55 ` [igt-dev] ✓ Fi.CI.BAT: success for Remove global igt_global_mmio (rev5) Patchwork
2019-05-09 22:41 ` [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=20190509123809.15507-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