Displaying 19 results from an estimated 19 matches for "i915_gem".
2013 Jun 24
3
[konrad.wilk@oracle.com: [PATCH] drm/i915: make compact dma scatter lists creation work with SWIOTLB backend.]
...that are not always
correct.
On a ThinkPad X230 with an Intel HD 4000 with Xen during the bootup
I see:
[drm:intel_pipe_set_base] *ERROR* pin & fence failed
[drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:3], err = -28
Bit of debugging traced it down to dma_map_sg failing (in
i915_gem_gtt_prepare_object) as some of the SG entries were huge (3MB).
That unfortunately are sizes that the SWIOTLB is incapable of handling -
the maximum it can handle is a an entry of 512KB of virtual contiguous
memory for its bounce buffer. (See IO_TLB_SEGSIZE).
Previous to the above mention git comm...
2019 Nov 01
0
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
On 10/28/19 1:10 PM, Jason Gunthorpe wrote:
> From: Jason Gunthorpe <jgg at mellanox.com>
>
> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
> scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
> they only use invalidate_range_start/end and immediately check the
> invalidating range against some driver data structure to tell if the
> driver is interested. Half of them use an in...
2019 Sep 13
1
[PATCH 0/9] drm/print: add and use drm_debug_enabled()
...drivers/gpu/drm/etnaviv/etnaviv_buffer.c | 8 +++----
drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
drivers/gpu/drm/i915/display/intel_display.c | 4 ++--
drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_gem.h | 2 +-
drivers/gpu/drm/i915/i915_utils.c | 2 +-
drivers/gpu/drm/i915/intel_pm.c | 2 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 4 ++--
drivers/gpu/drm/nouveau/dispnv50/disp.h | 4 ++--
drivers/gpu/drm/nouveau/nouveau_drv.h | 4 ++--...
2019 Oct 29
1
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
...Jason Gunthorpe wrote:
> From: Jason Gunthorpe <jgg at mellanox.com>
>
> Of the 13 users of mmu_notifiers, 8 of them use only
> invalidate_range_start/end() and immediately intersect the
> mmu_notifier_range with some kind of internal list of VAs. 4 use an
> interval tree (i915_gem, radeon_mn, umem_odp, hfi1). 4 use a linked list
> of some kind (scif_dma, vhost, gntdev, hmm)
>
> And the remaining 5 either don't use invalidate_range_start() or do some
> special thing with it.
>
> It turns out that building a correct scheme with an interval tree is
> pr...
2019 Sep 24
4
[PATCH v2 0/9] drm/print: add and use drm_debug_enabled()
...drivers/gpu/drm/etnaviv/etnaviv_buffer.c | 8 +++----
drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
drivers/gpu/drm/i915/display/intel_display.c | 4 ++--
drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_gem.h | 2 +-
drivers/gpu/drm/i915/i915_utils.c | 2 +-
drivers/gpu/drm/i915/intel_pm.c | 2 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 4 ++--
drivers/gpu/drm/nouveau/dispnv50/disp.h | 4 ++--
drivers/gpu/drm/nouveau/nouveau_drv.h | 4 ++--...
2020 Nov 03
45
[patch V3 00/37] mm/highmem: Preemptible variant of kmap_atomic & friends
...| 57 ---
b/arch/xtensa/Kconfig | 1
b/arch/xtensa/include/asm/fixmap.h | 4
b/arch/xtensa/include/asm/highmem.h | 12
b/arch/xtensa/mm/highmem.c | 46 --
b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 7
b/drivers/gpu/drm/i915/i915_gem.c | 40 --
b/drivers/gpu/drm/i915/selftests/i915_gem.c | 4
b/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 8
b/drivers/gpu/drm/nouveau/nvkm/subdev/devinit/fbmem.h | 8
b/drivers/gpu/drm/...
2020 Nov 03
45
[patch V3 00/37] mm/highmem: Preemptible variant of kmap_atomic & friends
...| 57 ---
b/arch/xtensa/Kconfig | 1
b/arch/xtensa/include/asm/fixmap.h | 4
b/arch/xtensa/include/asm/highmem.h | 12
b/arch/xtensa/mm/highmem.c | 46 --
b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 7
b/drivers/gpu/drm/i915/i915_gem.c | 40 --
b/drivers/gpu/drm/i915/selftests/i915_gem.c | 4
b/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 8
b/drivers/gpu/drm/nouveau/nvkm/subdev/devinit/fbmem.h | 8
b/drivers/gpu/drm/...
2020 Nov 03
45
[patch V3 00/37] mm/highmem: Preemptible variant of kmap_atomic & friends
...| 57 ---
b/arch/xtensa/Kconfig | 1
b/arch/xtensa/include/asm/fixmap.h | 4
b/arch/xtensa/include/asm/highmem.h | 12
b/arch/xtensa/mm/highmem.c | 46 --
b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 7
b/drivers/gpu/drm/i915/i915_gem.c | 40 --
b/drivers/gpu/drm/i915/selftests/i915_gem.c | 4
b/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 8
b/drivers/gpu/drm/nouveau/nvkm/subdev/devinit/fbmem.h | 8
b/drivers/gpu/drm/...
2019 Jan 16
1
[PATCH] drm: Split out drm_probe_helper.h
...+-
drivers/gpu/drm/i2c/ch7006_priv.h | 1 +
drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
drivers/gpu/drm/i915/i915_debugfs.c | 3 ++-
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_gem.c | 2 ++
drivers/gpu/drm/i915/i915_ioc32.c | 1 +
drivers/gpu/drm/i915/i915_irq.c | 2 ++
drivers/gpu/drm/i915/i915_pci.c | 2 ++
drivers/gpu/drm/i915/i915_trace.h | 2 ++
drivers/gpu/drm/i915/intel_crt.c | 2 +-...
2019 Jan 15
0
[PATCH] drm: Split out drm_probe_helper.h
...ch7006_priv.h | 1 +
> drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
> drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
> drivers/gpu/drm/i915/i915_debugfs.c | 3 +-
> drivers/gpu/drm/i915/i915_drv.c | 2 +-
> drivers/gpu/drm/i915/i915_gem.c | 2 +
> drivers/gpu/drm/i915/i915_ioc32.c | 1 +
> drivers/gpu/drm/i915/i915_irq.c | 2 +
> drivers/gpu/drm/i915/i915_pci.c | 2 +
> drivers/gpu/drm/i915/i915_trace.h | 2 +
> drivers/gpu/drm/i915/intel_crt.c...
2019 Jan 15
0
[PATCH] drm: Split out drm_probe_helper.h
...| 1 +
>> drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
>> drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
>> drivers/gpu/drm/i915/i915_debugfs.c | 3 +-
>> drivers/gpu/drm/i915/i915_drv.c | 2 +-
>> drivers/gpu/drm/i915/i915_gem.c | 2 +
>> drivers/gpu/drm/i915/i915_ioc32.c | 1 +
>> drivers/gpu/drm/i915/i915_irq.c | 2 +
>> drivers/gpu/drm/i915/i915_pci.c | 2 +
>> drivers/gpu/drm/i915/i915_trace.h | 2 +
>> drivers/g...
2019 Jan 15
6
[PATCH] drm: Split out drm_probe_helper.h
...+-
drivers/gpu/drm/i2c/ch7006_priv.h | 1 +
drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
drivers/gpu/drm/i915/i915_debugfs.c | 3 +-
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_gem.c | 2 +
drivers/gpu/drm/i915/i915_ioc32.c | 1 +
drivers/gpu/drm/i915/i915_irq.c | 2 +
drivers/gpu/drm/i915/i915_pci.c | 2 +
drivers/gpu/drm/i915/i915_trace.h | 2 +
drivers/gpu/drm/i915/intel_crt.c | 2 +-
driv...
2019 Jan 16
0
[PATCH] drm: Split out drm_probe_helper.h
...ch7006_priv.h | 1 +
> drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
> drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
> drivers/gpu/drm/i915/i915_debugfs.c | 3 +-
> drivers/gpu/drm/i915/i915_drv.c | 2 +-
> drivers/gpu/drm/i915/i915_gem.c | 2 +
> drivers/gpu/drm/i915/i915_ioc32.c | 1 +
> drivers/gpu/drm/i915/i915_irq.c | 2 +
> drivers/gpu/drm/i915/i915_pci.c | 2 +
> drivers/gpu/drm/i915/i915_trace.h | 2 +
> drivers/gpu/drm/i915/intel_crt.c...
2019 Jan 17
3
[PATCH] drm: Split out drm_probe_helper.h
...--
drivers/gpu/drm/i2c/ch7006_priv.h | 1 +
drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
drivers/gpu/drm/i915/i915_debugfs.c | 3 ++-
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_gem.c | 2 ++
drivers/gpu/drm/i915/i915_ioc32.c | 1 +
drivers/gpu/drm/i915/i915_irq.c | 2 ++
drivers/gpu/drm/i915/i915_pci.c | 2 ++
drivers/gpu/drm/i915/i915_trace.h | 2 ++
drivers/gpu/drm/i915/intel_crt.c | 2 +-...
2019 Jan 16
3
[PATCH] drm: Split out drm_probe_helper.h
...--
drivers/gpu/drm/i2c/ch7006_priv.h | 1 +
drivers/gpu/drm/i2c/sil164_drv.c | 2 +-
drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
drivers/gpu/drm/i915/i915_debugfs.c | 3 ++-
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_gem.c | 2 ++
drivers/gpu/drm/i915/i915_ioc32.c | 1 +
drivers/gpu/drm/i915/i915_irq.c | 2 ++
drivers/gpu/drm/i915/i915_pci.c | 2 ++
drivers/gpu/drm/i915/i915_trace.h | 2 ++
drivers/gpu/drm/i915/intel_crt.c | 2 +-...
2019 Oct 28
0
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
From: Jason Gunthorpe <jgg at mellanox.com>
Of the 13 users of mmu_notifiers, 8 of them use only
invalidate_range_start/end() and immediately intersect the
mmu_notifier_range with some kind of internal list of VAs. 4 use an
interval tree (i915_gem, radeon_mn, umem_odp, hfi1). 4 use a linked list
of some kind (scif_dma, vhost, gntdev, hmm)
And the remaining 5 either don't use invalidate_range_start() or do some
special thing with it.
It turns out that building a correct scheme with an interval tree is
pretty complicated, particularly if...
2019 Nov 12
0
[PATCH v3 02/14] mm/mmu_notifier: add an interval tree notifier
From: Jason Gunthorpe <jgg at mellanox.com>
Of the 13 users of mmu_notifiers, 8 of them use only
invalidate_range_start/end() and immediately intersect the
mmu_notifier_range with some kind of internal list of VAs. 4 use an
interval tree (i915_gem, radeon_mn, umem_odp, hfi1). 4 use a linked list
of some kind (scif_dma, vhost, gntdev, hmm)
And the remaining 5 either don't use invalidate_range_start() or do some
special thing with it.
It turns out that building a correct scheme with an interval tree is
pretty complicated, particularly if...
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the oth...
2019 Nov 12
20
[PATCH hmm v3 00/14] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the oth...