remove alloc_vm_area v2
Subsystems (10)
Hi Andrew,
this series removes alloc_vm_area, which was left over from the big vmalloc interface rework. It is a rather arkane interface, basicaly the equivalent of get_vm_area + actually faulting in all PTEs in the allocated area. It was originally addeds for Xen (which isn't modular to start with), and then grew users in zsmalloc and i915 which seems to mostly qualify as abuses of the interface, especially for i915 as a random driver should not set up PTE bits directly.
Note that the i915 patches apply to the drm-tip branch of the drm-tip tree, as that tree has recent conflicting commits in the same area.
A git tree is also available here:
git://git.infradead.org/users/hch/misc.git alloc_vm_area
Gitweb:
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/alloc_vm_area
Changes since v1:
- fix a bug in the zsmalloc changes
- fix a bug and rebase to include the recent changes in i915
- add a new vmap flag that allows to free the page array and pages using vfree
- add a vfree documentation updated from Matthew
Diffstat:
arch/x86/xen/grant-table.c | 27 ++++-- drivers/gpu/drm/i915/Kconfig | 1 drivers/gpu/drm/i915/gem/i915_gem_pages.c | 131 +++++++++++++----------------- drivers/gpu/drm/i915/gt/shmem_utils.c | 76 ++++------------- drivers/xen/xenbus/xenbus_client.c | 30 +++--- include/linux/vmalloc.h | 7 - mm/Kconfig | 3 mm/memory.c | 16 ++- mm/nommu.c | 7 - mm/vmalloc.c | 123 ++++++++++++++-------------- mm/zsmalloc.c | 10 +- 11 files changed, 200 insertions(+), 231 deletions(-)
PATCH 1/11 mm: update the documentation for vfree
From: "Matthew Wilcox (Oracle)" <[email protected]>
* Document that you can call vfree() on an address returned from vmap()
* Remove the note about the minimum size -- the minimum size of a vmalloc allocation is one page
* Add a Context: section
* Fix capitalisation
* Reword the prohibition on calling from NMI context to avoid a double negative
--- mm/vmalloc.c | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-)
mm/vmalloc.c +11 -10
@@ -2321,20 +2321,21 @@ static void __vfree(const void *addr) }/** -* vfree - release memory allocated by vmalloc() -* @addr: memory base address +* vfree - Release memory allocated by vmalloc() +* @addr: Memory base address * -* Free the virtually continuous memory area starting at @addr, as -* obtained from vmalloc(), vmalloc_32() or __vmalloc(). If @addr is -* NULL, no operation is performed. +* Free the virtually continuous memory area starting at @addr, as obtained +* from one of the vmalloc() family of APIs. This will usually also free the +* physical memory underlying the virtual allocation, but that memory is +* reference counted, so it will not be freed until the last user goes away. * -* Must not be called in NMI context (strictly speaking, only if we don't -* have CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG, but making the calling -* conventions for vfree() arch-depenedent would be a really bad idea) +* If @addr is NULL, no operation is performed. * +* Context: * May sleep if called *not* from interrupt context. -* -* NOTE: assumes that the object at @addr has a size >= sizeof(llist_node) +* Must not be called in NMI context (strictly speaking, it could be +* if we have CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG, but making the calling +* conventions for vfree() arch-depenedent would be a really bad idea). */ void vfree (const void *addr) {
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/11 mm: add a VM_MAP_PUT_PAGES flag for vmap
In reply to Christoph HellwigAdd a flag so that vmap takes ownership of the passed in page array. When vfree is called on such an allocation it will put one reference on each page, and free the page array itself.
--- include/linux/vmalloc.h | 1 + mm/vmalloc.c | 9 +++++++-- 2 files changed, 8 insertions(+), 2 deletions(-)
include/linux/vmalloc.h +1 -0
@@ -24,6 +24,7 @@ struct notifier_block; /* in notifier.h */#define VM_UNINITIALIZED 0x00000020/* vm_struct is not fully initialized */ #define VM_NO_GUARD 0x00000040/* don't add guard page */ #define VM_KASAN 0x00000080/* has allocated kasan shadow memory */ +#define VM_MAP_PUT_PAGES 0x00000100/* put pages and free array in vfree */ /* * VM_KASAN is used slighly differently depending on CONFIG_KASAN_VMALLOC.
mm/vmalloc.c +7 -2
@@ -2377,8 +2377,11 @@ EXPORT_SYMBOL(vunmap);* @flags: vm_area->flags * @prot: page protection for the mapping * -* Maps @count pages from @pages into contiguous kernel virtual -* space. +* Maps @count pages from @pages into contiguous kernel virtual space. +* If @flags contains %VM_MAP_PUT_PAGES the ownership of the pages array itself +* (which must be kmalloc or vmalloc memory) and one reference per pages in it +* are transferred from the caller to vmap(), and will be freed / dropped when +* vfree() is called on the return value. * * Return: the address of the area or %NULL on failure */
@@ -2404,6 +2407,8 @@ void *vmap(struct page **pages, unsigned int count,return NULL ; } +if (flags &VM_MAP_PUT_PAGES ) + area->pages = pages;return area->addr; }EXPORT_SYMBOL (vmap);
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 3/11 mm: add a vmap_pfn function
In reply to Christoph HellwigAdd a proper helper to remap PFNs into kernel virtual space so that drivers don't have to abuse alloc_vm_area and open coded PTE manipulation for it.
--- include/linux/vmalloc.h | 1 + mm/Kconfig | 3 +++ mm/vmalloc.c | 45 +++++++++++++++++++++++++++++++++++++++++ 3 files changed, 49 insertions(+)
include/linux/vmalloc.h +1 -0
@@ -122,6 +122,7 @@ extern void vfree_atomic(const void *addr);extern void *vmap (struct page **pages,unsigned int count,unsigned long flags,pgprot_t prot); +void *vmap_pfn (unsigned long *pfns,unsigned int count,pgprot_t prot);extern void vunmap (const void *addr); extern int remap_vmalloc_range_partial(struct vm_area_struct *vma,
mm/Kconfig +3 -0
@@ -815,6 +815,9 @@ config DEVICE_PRIVATE memory; i.e., memory that is only accessible from the device (or group of devices). You likely also want to select HMM_MIRROR. +config VMAP_PFN + bool + config FRAME_VECTOR bool
mm/vmalloc.c +45 -0
51 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH 4/11 mm: allow a NULL fn callback in apply_to_page_range
In reply to Christoph HellwigBesides calling the callback on each page, apply_to_page_range also has the effect of pre-faulting all PTEs for the range. To support callers that only need the pre-faulting, make the callback optional.
Based on a patch from Minchan Kim <[email protected]>.
--- mm/memory.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-)
mm/memory.c +9 -7
@@ -2231,13 +2231,15 @@ static int apply_to_pte_range(struct mm_struct *mm, pmd_t *pmd,arch_enter_lazy_mmu_mode (); -do { -if (create || !pte_none (*pte)) { - err =fn (pte++, addr, data); -if (err) -break ; - } - }while (addr +=PAGE_SIZE , addr != end); +if (fn) { +do { +if (create || !pte_none (*pte)) { + err =fn (pte++, addr, data); +if (err) +break ; + } + }while (addr +=PAGE_SIZE , addr != end); + } *mask |=PGTBL_PTE_MODIFIED ;arch_leave_lazy_mmu_mode ();
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 5/11 zsmalloc: switch from alloc_vm_area to get_vm_area
In reply to Christoph HellwigJust manually pre-fault the PTEs using apply_to_page_range.
--- mm/zsmalloc.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
mm/zsmalloc.c +8 -2
@@ -1122,10 +1122,16 @@ static inline int __zs_cpu_up(struct mapping_area *area)*/ if (area->vm)return 0 ; - area->vm =alloc_vm_area (PAGE_SIZE *2 ,NULL ); + area->vm =get_vm_area (PAGE_SIZE *2 ,0 );if (!area->vm)return -ENOMEM ; -return 0 ; + +/* +* Populate ptes in advance to avoid pte allocation with GFP_KERNEL +* in non-preemtible context of zs_map_object. +*/ +return apply_to_page_range (&init_mm, (unsigned long )area->vm->addr, +PAGE_SIZE *2 ,NULL ,NULL ); }static inline void __zs_cpu_down (struct mapping_area *area)
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 6/11 drm/i915: use vmap in shmem_pin_map
In reply to Christoph Hellwigshmem_pin_map somewhat awkwardly reimplements vmap using alloc_vm_area and manual pte setup. The only practical difference is that alloc_vm_area prefeaults the vmalloc area PTEs, which doesn't seem to be required here (and could be added to vmap using a flag if actually required). Switch to use vmap, and use vfree to free both the vmalloc mapping and the page array, as well as dropping the references to each page.
--- drivers/gpu/drm/i915/gt/shmem_utils.c | 76 +++++++-------------------- 1 file changed, 18 insertions(+), 58 deletions(-)
drivers/gpu/drm/i915/gt/shmem_utils.c +18 -58
@@ -49,80 +49,40 @@ struct file *shmem_create_from_object(struct drm_i915_gem_object *obj)return file; } -static size_t shmem_npte (struct file *file) -{ -return file->f_mapping->host->i_size >>PAGE_SHIFT ; -} - -static void __shmem_unpin_map (struct file *file,void *ptr,size_t n_pte) -{ -unsigned long pfn; - -vunmap (ptr); - -for (pfn =0 ; pfn < n_pte; pfn++) { -struct page *page; - - page =shmem_read_mapping_page_gfp (file->f_mapping, pfn, -GFP_KERNEL ); -if (!WARN_ON (IS_ERR (page))) { -put_page (page); -put_page (page); - } - } -} -void *shmem_pin_map (struct file *file) { -const size_t n_pte =shmem_npte (file); -pte_t *stack[32 ], **ptes, **mem; -struct vm_struct *area; -unsigned long pfn; - - mem = stack; -if (n_pte >ARRAY_SIZE (stack)) { - mem =kvmalloc_array (n_pte,sizeof (*mem),GFP_KERNEL ); -if (!mem) -return NULL ; - } +struct page **pages; +size_t n_pages, i; +void *vaddr; - area =alloc_vm_area (n_pte <<PAGE_SHIFT , mem); -if (!area) { -if (mem != stack) -kvfree (mem); + n_pages = file->f_mapping->host->i_size >>PAGE_SHIFT ; + pages =kvmalloc_array (n_pages,sizeof (*pages),GFP_KERNEL ); +if (!pages)return NULL ; - } - ptes = mem; -for (pfn =0 ; pfn < n_pte; pfn++) { -struct page *page; - - page =shmem_read_mapping_page_gfp (file->f_mapping, pfn, -GFP_KERNEL ); -if (IS_ERR (page)) +for (i =0 ; i < n_pages; i++) { + pages[i] =shmem_read_mapping_page_gfp (file->f_mapping, i, +GFP_KERNEL ); +if (IS_ERR (pages[i])) goto err_page; - - **ptes++ =mk_pte (page,PAGE_KERNEL ); } -if (mem != stack) -kvfree (mem); - + vaddr =vmap (pages, n_pages,VM_MAP_PUT_PAGES ,PAGE_KERNEL ); +if (!vaddr) + goto err_page;mapping_set_unevictable (file->f_mapping); -return area->addr; - +return vaddr; err_page: -if (mem != stack) -kvfree (mem); - -__shmem_unpin_map (file, area->addr, pfn); +while (--i >=0 ) +put_page (pages[i]); +kvfree (pages);return NULL ; }void shmem_unpin_map (struct file *file,void *ptr) {mapping_clear_unevictable (file->f_mapping); -__shmem_unpin_map (file, ptr,shmem_npte (file)); +vfree (ptr); } static int __shmem_rw(struct file *file, loff_t off,
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 06/11] drm/i915: use vmap in shmem_pin_map
Quoted 107 lines · Christoph Hellwig
shmem_pin_mapsomewhat awkwardly reimplements vmap usingalloc_vm_areaand manual pte setup. The only practical difference is thatalloc_vm_areaprefeaults the vmalloc area PTEs, which doesn't seem to be required here (and could be added to vmap using a flag if actually required). Switch to use vmap, and use vfree to free both the vmalloc mapping and the page array, as well as dropping the references to each page.Signed-off-by Christoph Hellwig <[email protected]>--- drivers/gpu/drm/i915/gt/shmem_utils.c | 76 +++++++-------------------- 1 file changed, 18 insertions(+), 58 deletions(-)drivers/gpu/drm/i915/gt/shmem_utils.c +17
-57@@ -49,80 +49,40 @@ struct file *shmem_create_from_object(struct drm_i915_gem_object *obj)return file; } -static size_t shmem_npte (struct file *file) -{ -return file->f_mapping->host->i_size >>PAGE_SHIFT ; -} - -static void __shmem_unpin_map (struct file *file,void *ptr,size_t n_pte) -{ -unsigned long pfn; - -vunmap (ptr); - -for (pfn =0 ; pfn < n_pte; pfn++) { -struct page *page; - - page =shmem_read_mapping_page_gfp (file->f_mapping, pfn, -GFP_KERNEL ); -if (!WARN_ON (IS_ERR (page))) { -put_page (page); -put_page (page); - } - } -} -void *shmem_pin_map (struct file *file) { -const size_t n_pte =shmem_npte (file); -pte_t *stack[32 ], **ptes, **mem; -struct vm_struct *area; -unsigned long pfn; - - mem = stack; -if (n_pte >ARRAY_SIZE (stack)) { - mem =kvmalloc_array (n_pte,sizeof (*mem),GFP_KERNEL ); -if (!mem) -return NULL ; - } +struct page **pages; +size_t n_pages, i; +void *vaddr; - area =alloc_vm_area (n_pte <<PAGE_SHIFT , mem); -if (!area) { -if (mem != stack) -kvfree (mem); + n_pages = file->f_mapping->host->i_size >>PAGE_SHIFT ; + pages =kvmalloc_array (n_pages,sizeof (*pages),GFP_KERNEL ); +if (!pages)return NULL ; - } - ptes = mem; -for (pfn =0 ; pfn < n_pte; pfn++) { -struct page *page; - - page =shmem_read_mapping_page_gfp (file->f_mapping, pfn, -GFP_KERNEL ); -if (IS_ERR (page)) +for (i =0 ; i < n_pages; i++) { + pages[i] =shmem_read_mapping_page_gfp (file->f_mapping, i, +GFP_KERNEL ); +if (IS_ERR (pages[i])) goto err_page; - - **ptes++ =mk_pte (page,PAGE_KERNEL ); } -if (mem != stack) -kvfree (mem); - + vaddr =vmap (pages, n_pages,VM_MAP_PUT_PAGES ,PAGE_KERNEL ); +if (!vaddr) + goto err_page;mapping_set_unevictable (file->f_mapping); -return area->addr; - +return vaddr; err_page: -if (mem != stack) -kvfree (mem); - -__shmem_unpin_map (file, area->addr, pfn); +while (--i >=0 ) +put_page (pages[i]); +kvfree (pages);return NULL ;
drivers/gpu/drm/i915/gt/shmem_utils.c struct file *shmem_create_from_object(struct drm_i915_gem_object *obj) · line 88
Quoted 10 lines
drivers/gpu/drm/i915/gt/shmem_utils.c +1
-1}void shmem_unpin_map (struct file *file,void *ptr) {mapping_clear_unevictable (file->f_mapping); -__shmem_unpin_map (file, ptr,shmem_npte (file)); +vfree (ptr); } static int __shmem_rw(struct file *file, loff_t off,
Regards,
Tvrtko
PATCH 7/11 drm/i915: stop using kmap in i915_gem_object_map
In reply to Christoph Hellwigkmap for !PageHighmem is just a convoluted way to say page_address, and kunmap is a no-op in that case.
--- drivers/gpu/drm/i915/gem/i915_gem_pages.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_pages.c +2 -5
@@ -162,8 +162,6 @@ static void unmap_object(struct drm_i915_gem_object *obj, void *ptr) {if (is_vmalloc_addr (ptr))vunmap (ptr); -else -kunmap (kmap_to_page (ptr)); } struct sg_table *
@@ -277,11 +275,10 @@ static void *i915_gem_object_map(struct drm_i915_gem_object *obj,* forever. * * So if the page is beyond the 32b boundary, make an explicit -* vmap. On 64b, this check will be optimised away as we can -* directly kmap any page on the system. +* vmap. */ if (!PageHighMem (page)) -return kmap (page); +return page_address (page); } mem = stack;
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 07/11] drm/i915: stop using kmap in i915_gem_object_map
Quoted 26 lines · Christoph Hellwig
kmap for !PageHighmem is just a convoluted way to say
page_address, and kunmap is a no-op in that case.Signed-off-by Christoph Hellwig <[email protected]>--- drivers/gpu/drm/i915/gem/i915_gem_pages.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_pages.c +0
-2@@ -162,8 +162,6 @@ static void unmap_object(struct drm_i915_gem_object *obj, void *ptr) {if (is_vmalloc_addr (ptr))vunmap (ptr); -else -kunmap (kmap_to_page (ptr)); } struct sg_table *@@ -277,11 +275,10 @@ static void *i915_gem_object_map(struct drm_i915_gem_object *obj,* forever. * * So if the page is beyond the 32b boundary, make an explicit
drivers/gpu/drm/i915/gem/i915_gem_pages.c static void *i915_gem_object_map(struct drm_i915_gem_object *obj, · line 284
Quoted 10 lines
drivers/gpu/drm/i915/gem/i915_gem_pages.c +2
-3-* vmap. On 64b, this check will be optimised away as we can -* directly kmap any page on the system. +* vmap. */ if (!PageHighMem (page)) -return kmap (page); +return page_address (page); } mem = stack;
Regards,
Tvrtko
PATCH 8/11 drm/i915: use vmap in i915_gem_object_map
In reply to Christoph Hellwigi915_gem_object_map implements fairly low-level vmap functionality in a driver. Split it into two helpers, one for remapping kernel memory which can use vmap, and one for I/O memory that uses vmap_pfn.
The only practical difference is that alloc_vm_area prefeaults the vmalloc area PTEs, which doesn't seem to be required here for the kernel memory case (and could be added to vmap using a flag if actually required).
--- drivers/gpu/drm/i915/Kconfig | 1 + drivers/gpu/drm/i915/gem/i915_gem_pages.c | 126 ++++++++++------------ 2 files changed, 59 insertions(+), 68 deletions(-)
drivers/gpu/drm/i915/Kconfig +1 -0
@@ -25,6 +25,7 @@ config DRM_I915 select CRC32 select SND_HDA_I915 if SND_HDA_CORE select CEC_CORE if CEC_NOTIFIER + select VMAP_PFN help Choose this option if you have a system that has "Intel Graphics Media Accelerator" or "HD Graphics" integrated graphics,
drivers/gpu/drm/i915/gem/i915_gem_pages.c +58 -68
159 lines not on this page · raw message
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 08/11] drm/i915: use vmap in i915_gem_object_map
Quoted 185 lines · Christoph Hellwig
i915_gem_object_mapimplements fairly low-level vmap functionality in a driver. Split it into two helpers, one for remapping kernel memory which can use vmap, and one for I/O memory that usesvmap_pfn.The only practical difference is that
alloc_vm_areaprefeaults the vmalloc area PTEs, which doesn't seem to be required here for the kernel memory case (and could be added to vmap using a flag if actually required).Signed-off-by Christoph Hellwig <[email protected]>--- drivers/gpu/drm/i915/Kconfig | 1 + drivers/gpu/drm/i915/gem/i915_gem_pages.c | 126 ++++++++++------------ 2 files changed, 59 insertions(+), 68 deletions(-)drivers/gpu/drm/i915/Kconfig +1
-0@@ -25,6 +25,7 @@ config DRM_I915 select CRC32 select SND_HDA_I915 if SND_HDA_CORE select CEC_CORE if CEC_NOTIFIER + select VMAP_PFN help Choose this option if you have a system that has "Intel Graphics Media Accelerator" or "HD Graphics" integrated graphics,drivers/gpu/drm/i915/gem/i915_gem_pages.c +51
-68@@ -232,34 +232,21 @@ int __i915_gem_object_put_pages(struct drm_i915_gem_object *obj)return err; } -static inline pte_t iomap_pte (resource_size_t base, -dma_addr_t offset, -pgprot_t prot) -{ -return pte_mkspecial (pfn_pte ((base + offset) >>PAGE_SHIFT , prot)); -} -/* The 'mapping' part of i915_gem_object_pin_map() below */ -static void *i915_gem_object_map (struct drm_i915_gem_object *obj, -enum i915_map_type type) +static void *i915_gem_object_map_page (struct drm_i915_gem_object *obj, +enum i915_map_type type) { -unsigned long n_pte = obj->base.size >>PAGE_SHIFT ; -struct sg_table *sgt = obj->mm.pages; -pte_t *stack[32 ], **mem; -struct vm_struct *area; +unsigned long n_pages = obj->base.size >>PAGE_SHIFT , i; +struct page *stack[32 ], **pages = stack, *page; +struct sgt_iter iter;pgprot_t pgprot; +void *vaddr; -if (!i915_gem_object_has_struct_page (obj) && type !=I915_MAP_WC ) -return NULL ; - -if (GEM_WARN_ON (type ==I915_MAP_WC && - !static_cpu_has (X86_FEATURE_PAT ))) -return NULL ; - -/* A single page can always be kmapped */ -if (n_pte ==1 && type ==I915_MAP_WB ) { -struct page *page =sg_page (sgt->sgl); - +switch (type) { +default : +MISSING_CASE (type); + fallthrough;/* to use PAGE_KERNEL anyway */ +case I915_MAP_WB :/* * On 32b, highmem using a finite set of indirect PTE (i.e. * vmap) to provide virtual mappings of the high pages. @@ -277,30 +264,8 @@ static void *i915_gem_object_map(struct drm_i915_gem_object *obj,* So if the page is beyond the 32b boundary, make an explicit * vmap. */ -if (!PageHighMem (page)) -return page_address (page); - } - - mem = stack; -if (n_pte >ARRAY_SIZE (stack)) { -/* Too big for stack -- allocate temporary array instead */ - mem =kvmalloc_array (n_pte,sizeof (*mem),GFP_KERNEL ); -if (!mem) -return NULL ; - } - - area =alloc_vm_area (obj->base.size, mem); -if (!area) { -if (mem != stack) -kvfree (mem); -return NULL ; - } - -switch (type) { -default : -MISSING_CASE (type); - fallthrough;/* to use PAGE_KERNEL anyway */ -case I915_MAP_WB : +if (n_pages ==1 && !PageHighMem (sg_page (obj->mm.pages->sgl))) +return page_address (sg_page (obj->mm.pages->sgl)); pgprot =PAGE_KERNEL ;break ;case I915_MAP_WC :@@ -308,30 +273,49 @@ static void *i915_gem_object_map(struct drm_i915_gem_object *obj,break ; } -if (i915_gem_object_has_struct_page (obj)) { -struct sgt_iter iter; -struct page *page; -pte_t **ptes = mem; +if (n_pages >ARRAY_SIZE (stack)) { +/* Too big for stack -- allocate temporary array instead */ + pages =kvmalloc_array (n_pages,sizeof (*pages),GFP_KERNEL ); +if (!pages) +return NULL ; + } -for_each_sgt_page (page, iter, sgt) - **ptes++ =mk_pte (page, pgprot); - }else { -resource_size_t iomap; -struct sgt_iter iter; -pte_t **ptes = mem; -dma_addr_t addr; + i =0 ; +for_each_sgt_page (page, iter, obj->mm.pages) + pages[i++] = page; + vaddr =vmap (pages, n_pages,0 , pgprot); +if (pages != stack) +kvfree (pages); +return vaddr; +} - iomap = obj->mm.region->iomap.base; - iomap -= obj->mm.region->region.start; +static void *i915_gem_object_map_pfn (struct drm_i915_gem_object *obj, +enum i915_map_type type) +{ +resource_size_t iomap = obj->mm.region->iomap.base - + obj->mm.region->region.start; +unsigned long n_pfn = obj->base.size >>PAGE_SHIFT ; +unsigned long stack[32 ], *pfns = stack, i; +struct sgt_iter iter; +dma_addr_t addr; +void *vaddr; + +if (type !=I915_MAP_WC ) +return NULL ; -for_each_sgt_daddr (addr, iter, sgt) - **ptes++ =iomap_pte (iomap, addr, pgprot); +if (n_pfn >ARRAY_SIZE (stack)) { +/* Too big for stack -- allocate temporary array instead */ + pfns =kvmalloc_array (n_pfn,sizeof (*pfns),GFP_KERNEL ); +if (!pfns) +return NULL ; } -if (mem != stack) -kvfree (mem); - -return area->addr; +for_each_sgt_daddr (addr, iter, obj->mm.pages) + pfns[i++] = (iomap + addr) >>PAGE_SHIFT ; + vaddr =vmap_pfn (pfns, n_pfn,pgprot_writecombine (PAGE_KERNEL_IO )); +if (pfns != stack) +kvfree (pfns); +return vaddr; }/* get, pin, and map the pages of the object into kernel space */ @@ -383,7 +367,13 @@ void *i915_gem_object_pin_map(struct drm_i915_gem_object *obj, }if (!ptr) { - ptr =i915_gem_object_map (obj, type);
drivers/gpu/drm/i915/gem/i915_gem_pages.c void *i915_gem_object_pin_map(struct drm_i915_gem_object *obj, · line 379
Quoted 10 lines
drivers/gpu/drm/i915/gem/i915_gem_pages.c +7
-0+if (GEM_WARN_ON (type ==I915_MAP_WC && + !static_cpu_has (X86_FEATURE_PAT ))) + ptr =NULL ; +else if (i915_gem_object_has_struct_page (obj)) + ptr =i915_gem_object_map_page (obj, type); +else + ptr =i915_gem_object_map_pfn (obj, type);if (!ptr) { err = -ENOMEM ; goto err_unpin;
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 08/11] drm/i915: use vmap in i915_gem_object_map
In reply to Christoph HellwigQuoted 163 lines · Christoph Hellwig
i915_gem_object_mapimplements fairly low-level vmap functionality in a driver. Split it into two helpers, one for remapping kernel memory which can use vmap, and one for I/O memory that usesvmap_pfn.The only practical difference is that
alloc_vm_areaprefeaults the vmalloc area PTEs, which doesn't seem to be required here for the kernel memory case (and could be added to vmap using a flag if actually required).Signed-off-by Christoph Hellwig <[email protected]>--- drivers/gpu/drm/i915/Kconfig | 1 + drivers/gpu/drm/i915/gem/i915_gem_pages.c | 126 ++++++++++------------ 2 files changed, 59 insertions(+), 68 deletions(-)drivers/gpu/drm/i915/Kconfig +1
-0@@ -25,6 +25,7 @@ config DRM_I915 select CRC32 select SND_HDA_I915 if SND_HDA_CORE select CEC_CORE if CEC_NOTIFIER + select VMAP_PFN help Choose this option if you have a system that has "Intel Graphics Media Accelerator" or "HD Graphics" integrated graphics,drivers/gpu/drm/i915/gem/i915_gem_pages.c +43
-63@@ -232,34 +232,21 @@ int __i915_gem_object_put_pages(struct drm_i915_gem_object *obj)return err; } -static inline pte_t iomap_pte (resource_size_t base, -dma_addr_t offset, -pgprot_t prot) -{ -return pte_mkspecial (pfn_pte ((base + offset) >>PAGE_SHIFT , prot)); -} -/* The 'mapping' part of i915_gem_object_pin_map() below */ -static void *i915_gem_object_map (struct drm_i915_gem_object *obj, -enum i915_map_type type) +static void *i915_gem_object_map_page (struct drm_i915_gem_object *obj, +enum i915_map_type type) { -unsigned long n_pte = obj->base.size >>PAGE_SHIFT ; -struct sg_table *sgt = obj->mm.pages; -pte_t *stack[32 ], **mem; -struct vm_struct *area; +unsigned long n_pages = obj->base.size >>PAGE_SHIFT , i; +struct page *stack[32 ], **pages = stack, *page; +struct sgt_iter iter;pgprot_t pgprot; +void *vaddr; -if (!i915_gem_object_has_struct_page (obj) && type !=I915_MAP_WC ) -return NULL ; - -if (GEM_WARN_ON (type ==I915_MAP_WC && - !static_cpu_has (X86_FEATURE_PAT ))) -return NULL ; - -/* A single page can always be kmapped */ -if (n_pte ==1 && type ==I915_MAP_WB ) { -struct page *page =sg_page (sgt->sgl); - +switch (type) { +default : +MISSING_CASE (type); + fallthrough;/* to use PAGE_KERNEL anyway */ +case I915_MAP_WB :/* * On 32b, highmem using a finite set of indirect PTE (i.e. * vmap) to provide virtual mappings of the high pages. @@ -277,30 +264,8 @@ static void *i915_gem_object_map(struct drm_i915_gem_object *obj,* So if the page is beyond the 32b boundary, make an explicit * vmap. */ -if (!PageHighMem (page)) -return page_address (page); - } - - mem = stack; -if (n_pte >ARRAY_SIZE (stack)) { -/* Too big for stack -- allocate temporary array instead */ - mem =kvmalloc_array (n_pte,sizeof (*mem),GFP_KERNEL ); -if (!mem) -return NULL ; - } - - area =alloc_vm_area (obj->base.size, mem); -if (!area) { -if (mem != stack) -kvfree (mem); -return NULL ; - } - -switch (type) { -default : -MISSING_CASE (type); - fallthrough;/* to use PAGE_KERNEL anyway */ -case I915_MAP_WB : +if (n_pages ==1 && !PageHighMem (sg_page (obj->mm.pages->sgl))) +return page_address (sg_page (obj->mm.pages->sgl)); pgprot =PAGE_KERNEL ;break ;case I915_MAP_WC :@@ -308,30 +273,49 @@ static void *i915_gem_object_map(struct drm_i915_gem_object *obj,break ; } -if (i915_gem_object_has_struct_page (obj)) { -struct sgt_iter iter; -struct page *page; -pte_t **ptes = mem; +if (n_pages >ARRAY_SIZE (stack)) { +/* Too big for stack -- allocate temporary array instead */ + pages =kvmalloc_array (n_pages,sizeof (*pages),GFP_KERNEL ); +if (!pages) +return NULL ; + } -for_each_sgt_page (page, iter, sgt) - **ptes++ =mk_pte (page, pgprot); - }else { -resource_size_t iomap; -struct sgt_iter iter; -pte_t **ptes = mem; -dma_addr_t addr; + i =0 ; +for_each_sgt_page (page, iter, obj->mm.pages) + pages[i++] = page; + vaddr =vmap (pages, n_pages,0 , pgprot); +if (pages != stack) +kvfree (pages); +return vaddr; +} - iomap = obj->mm.region->iomap.base; - iomap -= obj->mm.region->region.start; +static void *i915_gem_object_map_pfn (struct drm_i915_gem_object *obj, +enum i915_map_type type) +{ +resource_size_t iomap = obj->mm.region->iomap.base - + obj->mm.region->region.start; +unsigned long n_pfn = obj->base.size >>PAGE_SHIFT ; +unsigned long stack[32 ], *pfns = stack, i; +struct sgt_iter iter; +dma_addr_t addr; +void *vaddr; + +if (type !=I915_MAP_WC ) +return NULL ; -for_each_sgt_daddr (addr, iter, sgt) - **ptes++ =iomap_pte (iomap, addr, pgprot); +if (n_pfn >ARRAY_SIZE (stack)) { +/* Too big for stack -- allocate temporary array instead */ + pfns =kvmalloc_array (n_pfn,sizeof (*pfns),GFP_KERNEL );
drivers/gpu/drm/i915/gem/i915_gem_pages.c static void *i915_gem_object_map(struct drm_i915_gem_object *obj, · line 314
Quoted 10 lines
drivers/gpu/drm/i915/gem/i915_gem_pages.c +4
-4+if (!pfns) +return NULL ; } -if (mem != stack) -kvfree (mem); - -return area->addr; +for_each_sgt_daddr (addr, iter, obj->mm.pages) + pfns[i++] = (iomap + addr) >>PAGE_SHIFT ;
Missing the i = 0 fix from Dan?
Quoted 29 lines
drivers/gpu/drm/i915/gem/i915_gem_pages.c +11
-2+ vaddr =vmap_pfn (pfns, n_pfn,pgprot_writecombine (PAGE_KERNEL_IO )); +if (pfns != stack) +kvfree (pfns); +return vaddr; }/* get, pin, and map the pages of the object into kernel space */ @@ -383,7 +367,13 @@ void *i915_gem_object_pin_map(struct drm_i915_gem_object *obj, }if (!ptr) { - ptr =i915_gem_object_map (obj, type); +if (GEM_WARN_ON (type ==I915_MAP_WC && + !static_cpu_has (X86_FEATURE_PAT ))) + ptr =NULL ; +else if (i915_gem_object_has_struct_page (obj)) + ptr =i915_gem_object_map_page (obj, type); +else + ptr =i915_gem_object_map_pfn (obj, type);if (!ptr) { err = -ENOMEM ; goto err_unpin; --2.28.0
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 08/11] drm/i915: use vmap in i915_gem_object_map
Quoted 9 lines · Matthew Auld
Quoted 8 lines
drivers/gpu/drm/i915/gem/i915_gem_pages.c +8
-0+ i =0 ; +for_each_sgt_page (page, iter, obj->mm.pages) + pages[i++] = page; + vaddr =vmap (pages, n_pages,0 , pgprot); +if (pages != stack) +kvfree (pages); +return vaddr; +}
Quoted 5 lines
drivers/gpu/drm/i915/gem/i915_gem_pages.c static void *i915_gem_object_map(struct drm_i915_gem_object *obj, · line 314
Quoted 3 lines
drivers/gpu/drm/i915/gem/i915_gem_pages.c +2
-1-return area->addr; +for_each_sgt_daddr (addr, iter, obj->mm.pages) + pfns[i++] = (iomap + addr) >>PAGE_SHIFT ;Missing the i = 0 fix from Dan?
Yeah, looks like I only managed to apply the one in the page based version above.
PATCH 8/11 drm/i915: use vmap in i915_gem_object_map
In reply to Christoph Hellwigi915_gem_object_map implements fairly low-level vmap functionality in a driver. Split it into two helpers, one for remapping kernel memory which can use vmap, and one for I/O memory that uses vmap_pfn.
The only practical difference is that alloc_vm_area prefeaults the vmalloc area PTEs, which doesn't seem to be required here for the kernel memory case (and could be added to vmap using a flag if actually required).
--- drivers/gpu/drm/i915/Kconfig | 1 + drivers/gpu/drm/i915/gem/i915_gem_pages.c | 127 ++++++++++------------ 2 files changed, 60 insertions(+), 68 deletions(-)
drivers/gpu/drm/i915/Kconfig +1 -0
@@ -25,6 +25,7 @@ config DRM_I915 select CRC32 select SND_HDA_I915 if SND_HDA_CORE select CEC_CORE if CEC_NOTIFIER + select VMAP_PFN help Choose this option if you have a system that has "Intel Graphics Media Accelerator" or "HD Graphics" integrated graphics,
drivers/gpu/drm/i915/gem/i915_gem_pages.c +59 -68
160 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH 9/11 xen/xenbus: use apply_to_page_range directly in xenbus_map_ring_pv
In reply to Christoph HellwigReplacing alloc_vm_area with get_vm_area_caller + apply_page_range allows to fill put the phys_addr values directly instead of doing another loop over all addresses.
--- drivers/xen/xenbus/xenbus_client.c | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-)
drivers/xen/xenbus/xenbus_client.c +16 -14
@@ -73,16 +73,13 @@ struct map_ring_valloc {struct xenbus_map_node *node;/* Why do we need two arrays? See comment of __xenbus_map_ring */ -union { -unsigned long addrs[XENBUS_MAX_RING_GRANTS ]; -pte_t *ptes[XENBUS_MAX_RING_GRANTS ]; - }; +unsigned long addrs[XENBUS_MAX_RING_GRANTS ];phys_addr_t phys_addrs[XENBUS_MAX_RING_GRANTS ];struct gnttab_map_grant_ref map[XENBUS_MAX_RING_GRANTS ];struct gnttab_unmap_grant_ref unmap[XENBUS_MAX_RING_GRANTS ]; -unsigned int idx;/* HVM only. */ +unsigned int idx; };static DEFINE_SPINLOCK (xenbus_valloc_lock);
@@ -686,6 +683,14 @@ int xenbus_unmap_ring_vfree(struct xenbus_device *dev, void *vaddr)EXPORT_SYMBOL_GPL (xenbus_unmap_ring_vfree);#ifdef CONFIG_XEN_PV +static int map_ring_apply (pte_t *pte,unsigned long addr,void *data) +{ +struct map_ring_valloc *info = data; + + info->phys_addrs[info->idx++] =arbitrary_virt_to_machine (pte).maddr; +return 0 ; +} + static int xenbus_map_ring_pv(struct xenbus_device *dev, struct map_ring_valloc *info, grant_ref_t *gnt_refs,
@@ -694,18 +699,15 @@ static int xenbus_map_ring_pv(struct xenbus_device *dev, {struct xenbus_map_node *node = info->node;struct vm_struct *area; -int err = GNTST_okay; -int i; -bool leaked; +bool leaked = false; +int err = -ENOMEM ; - area =alloc_vm_area (XEN_PAGE_SIZE * nr_grefs, info->ptes); + area =get_vm_area (XEN_PAGE_SIZE * nr_grefs,VM_IOREMAP );if (!area)return -ENOMEM ; - -for (i =0 ; i < nr_grefs; i++) - info->phys_addrs[i] = -arbitrary_virt_to_machine (info->ptes[i]).maddr; - +if (apply_to_page_range (&init_mm, (unsigned long )area->addr, +XEN_PAGE_SIZE * nr_grefs, map_ring_apply, info)) + goto failed; err =__xenbus_map_ring (dev, gnt_refs, nr_grefs, node->handles, info, GNTMAP_host_map | GNTMAP_contains_pte, &leaked);
Signature · 1 line
2.28.0
Re: [PATCH 09/11] xen/xenbus: use apply_to_page_range directly in xenbus_map_ring_pv
Quoted 5 lines · Christoph Hellwig
Replacing
alloc_vm_areawithget_vm_area_caller+apply_page_rangeallows to fill put thephys_addrvalues directly instead of doing another loop over all addresses.Signed-off-by Christoph Hellwig <[email protected]>
-boris
PATCH 10/11 x86/xen: open code alloc_vm_area in arch_gnttab_valloc
In reply to Christoph HellwigReplace the last call to alloc_vm_area with an open coded version using an iterator in struct gnttab_vm_area instead of the triple indirection magic in alloc_vm_area.
--- arch/x86/xen/grant-table.c | 27 ++++++++++++++++++++------- 1 file changed, 20 insertions(+), 7 deletions(-)
arch/x86/xen/grant-table.c +20 -7
@@ -25,6 +25,7 @@static struct gnttab_vm_area {struct vm_struct *area;pte_t **ptes; +int idx; } gnttab_shared_vm_area, gnttab_status_vm_area; int arch_gnttab_map_shared(unsigned long *frames, unsigned long nr_gframes,
@@ -90,19 +91,31 @@ void arch_gnttab_unmap(void *shared, unsigned long nr_gframes) } } +static int gnttab_apply (pte_t *pte,unsigned long addr,void *data) +{ +struct gnttab_vm_area *area = data; + + area->ptes[area->idx++] = pte; +return 0 ; +} +static int arch_gnttab_valloc (struct gnttab_vm_area *area,unsigned nr_frames) { area->ptes =kmalloc_array (nr_frames,sizeof (*area->ptes),GFP_KERNEL );if (area->ptes ==NULL )return -ENOMEM ; - - area->area =alloc_vm_area (PAGE_SIZE * nr_frames, area->ptes); -if (area->area ==NULL ) { -kfree (area->ptes); -return -ENOMEM ; - } - + area->area =get_vm_area (PAGE_SIZE * nr_frames,VM_IOREMAP ); +if (!area->area) + goto out_free_ptes; +if (apply_to_page_range (&init_mm, (unsigned long )area->area->addr, +PAGE_SIZE * nr_frames, gnttab_apply, area)) + goto out_free_vm_area;return 0 ; +out_free_vm_area: +free_vm_area (area->area); +out_free_ptes: +kfree (area->ptes); +return -ENOMEM ; }static void arch_gnttab_vfree (struct gnttab_vm_area *area)
Signature · 1 line
2.28.0
Re: [PATCH 10/11] x86/xen: open code alloc_vm_area in arch_gnttab_valloc
Quoted 5 lines · Christoph Hellwig
Replace the last call to
alloc_vm_areawith an open coded version using an iterator in structgnttab_vm_areainstead of the triple indirection magic inalloc_vm_area.Signed-off-by Christoph Hellwig <[email protected]>
PATCH 11/11 mm: remove alloc_vm_area
In reply to Christoph HellwigAll users are gone now.
--- include/linux/vmalloc.h | 5 +---- mm/nommu.c | 7 ------ mm/vmalloc.c | 48 ----------------------------------------- 3 files changed, 1 insertion(+), 59 deletions(-)
include/linux/vmalloc.h +1 -4
@@ -169,6 +169,7 @@ extern struct vm_struct *__get_vm_area_caller(unsigned long size,unsigned long flags, unsigned long start, unsigned long end, const void *caller); +void free_vm_area (struct vm_struct *area);extern struct vm_struct *remove_vm_area (const void *addr);extern struct vm_struct *find_vm_area (const void *addr);
@@ -204,10 +205,6 @@ static inline void set_vm_flush_reset_perms(void *addr) }#endif -/* Allocate/destroy a 'vmalloc' VM area. */ -extern struct vm_struct *alloc_vm_area (size_t size,pte_t **ptes); -extern void free_vm_area (struct vm_struct *area); -/* for /dev/kmem */ extern long vread (char *buf,char *addr,unsigned long count);extern long vwrite (char *buf,char *addr,unsigned long count);
mm/nommu.c +0 -7
@@ -354,13 +354,6 @@ void vm_unmap_aliases(void) }EXPORT_SYMBOL_GPL (vm_unmap_aliases); -struct vm_struct *alloc_vm_area (size_t size,pte_t **ptes) -{ -BUG (); -return NULL ; -} -EXPORT_SYMBOL_GPL (alloc_vm_area); -void free_vm_area (struct vm_struct *area) {BUG ();
mm/vmalloc.c +0 -48
54 lines not on this page · raw message
Signature · 6 lines
2.28.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] mm: update the documentation for vfree
In reply to Christoph Hellwig== Series Details ==
== Series Details ==
Series: series starting with [01/11] mm: update the documentation for vfree
URL : https://patchwork.freedesktop.org/series/82063/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 5e88ddacdd34 mm: update the documentation for vfree 90f3c1ba13d1 mm: add a VM_MAP_PUT_PAGES flag for vmap d41a24c9aa63 mm: add a vmap_pfn function -:78: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #78: FILE: mm/vmalloc.c:2448: + area = get_vm_area_caller(count * PAGE_SIZE, VM_IOREMAP, + __builtin_return_address(0));
-:82: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #82: FILE: mm/vmalloc.c:2452:
+ if (apply_to_page_range(&init_mm, (unsigned long)area->addr,
+ count * PAGE_SIZE, vmap_pfn_apply, &data)) {
total: 0 errors, 0 warnings, 2 checks, 67 lines checked5a2e6e88ce76 mm: allow a NULL fn callback in apply_to_page_range 140abd5e7d29 zsmalloc: switch from alloc_vm_area to get_vm_area
-:8: WARNING:BAD_SIGN_OFF: Co-developed-by and Signed-off-by: name/email do not match #8:
total: 0 errors, 1 warnings, 0 checks, 18 lines checked 56b3f4b2f183 drm/i915: use vmap in shmem_pin_mapa037e6a84cf4 drm/i915: stop using kmap in i915_gem_object_map 1b6df0a418db drm/i915: use vmap in i915_gem_object_map
-:48: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #48: FILE: drivers/gpu/drm/i915/gem/i915_gem_pages.c:237:
+static void *i915_gem_object_map_page(struct drm_i915_gem_object *obj,
+ enum i915_map_type type)
-:146: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #146: FILE: drivers/gpu/drm/i915/gem/i915_gem_pages.c:293:
+static void *i915_gem_object_map_pfn(struct drm_i915_gem_object *obj,
+ enum i915_map_type type)
total: 0 errors, 0 warnings, 2 checks, 166 lines checked cad740b44a07 xen/xenbus: use apply_to_page_range directly in xenbus_map_ring_pv 15518d083ba6 x86/xen: open code alloc_vm_area in arch_gnttab_valloc -:52: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #52: FILE: arch/x86/xen/grant-table.c:111:
+ if (apply_to_page_range(&init_mm, (unsigned long)area->area->addr,
+ PAGE_SIZE * nr_frames, gnttab_apply, area))
total: 0 errors, 0 warnings, 1 checks, 45 lines checked 18c3303e9cc0 mm: remove alloc_vm_area
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [01/11] mm: update the documentation for vfree
In reply to Christoph Hellwig== Series Details ==
== Series Details ==
Series: series starting with [01/11] mm: update the documentation for vfree
URL : https://patchwork.freedesktop.org/series/82063/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9049 -> Patchwork_18563
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/index.html
Known issues
------------
Here are the changes found in Patchwork_18563 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_tiled_blits@basic:
- fi-tgl-y: [PASS][1] -> [DMESG-WARN][2] ([i915#402]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-tgl-y/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-tgl-y/igt@[email protected]
* igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
- fi-icl-u2: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-icl-u2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-icl-u2/igt@[email protected]
#### Possible fixes ####
* igt@gem_flink_basic@double-flink:
- fi-tgl-y: [DMESG-WARN][5] ([i915#402]) -> [PASS][6] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-tgl-y/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-tgl-y/igt@[email protected]
* igt@i915_selftest@live@coherency:
- fi-gdg-551: [DMESG-FAIL][7] ([i915#1748]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-gdg-551/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-gdg-551/igt@i915_selftest@[email protected]
* igt@kms_busy@basic@modeset:
- {fi-tgl-dsi}: [DMESG-WARN][9] ([i915#1982]) -> [PASS][10] +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-tgl-dsi/igt@kms_busy@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-tgl-dsi/igt@kms_busy@[email protected]
- fi-tgl-y: [DMESG-WARN][11] ([i915#1982]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-tgl-y/igt@kms_busy@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-tgl-y/igt@kms_busy@[email protected]
* igt@vgem_basic@unload:
- fi-skl-guc: [DMESG-WARN][13] ([i915#2203]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-skl-guc/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-skl-guc/igt@[email protected]
#### Warnings ####
* igt@i915_pm_rpm@module-reload:
- fi-tgl-y: [DMESG-WARN][15] ([i915#1982] / [i915#2411]) -> [DMESG-WARN][16] ([i915#2411])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-tgl-y/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-tgl-y/igt@[email protected]
* igt@kms_cursor_legacy@basic-flip-before-cursor-varying-size:
- fi-kbl-x1275: [DMESG-WARN][17] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][18] ([i915#62] / [i915#92]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-kbl-x1275/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-kbl-x1275/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-kbl-x1275: [DMESG-WARN][19] ([i915#62] / [i915#92]) -> [DMESG-WARN][20] ([i915#62] / [i915#92] / [i915#95]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/fi-kbl-x1275/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/fi-kbl-x1275/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1748]: https://gitlab.freedesktop.org/drm/intel/issues/1748
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2203]: https://gitlab.freedesktop.org/drm/intel/issues/2203
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#289]: https://gitlab.freedesktop.org/drm/intel/issues/289
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (46 -> 40)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9049 -> Patchwork_18563
CI-20190529: 20190529
CI_DRM_9049: 6a36f5cbd72a6547eb096c2dcd130fc38861c649 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5787: 0ec962017c8131de14e0cb038f7f76b1f17ed637 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18563: 18c3303e9cc0a187606713181f8a87199d90d2d7 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
18c3303e9cc0 mm: remove alloc_vm_area15518d083ba6 x86/xen: open code alloc_vm_area in arch_gnttab_valloc cad740b44a07 xen/xenbus: use apply_to_page_range directly in xenbus_map_ring_pv 1b6df0a418db drm/i915: use vmap in i915_gem_object_map a037e6a84cf4 drm/i915: stop using kmap in i915_gem_object_map 56b3f4b2f183 drm/i915: use vmap in shmem_pin_map140abd5e7d29 zsmalloc: switch from alloc_vm_area to get_vm_area 5a2e6e88ce76 mm: allow a NULL fn callback in apply_to_page_range d41a24c9aa63 mm: add a vmap_pfn function90f3c1ba13d1 mm: add a VM_MAP_PUT_PAGES flag for vmap5e88ddacdd34 mm: update the documentation for vfree
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [01/11] mm: update the documentation for vfree
In reply to Christoph Hellwig== Series Details ==
== Series Details ==
Series: series starting with [01/11] mm: update the documentation for vfree
URL : https://patchwork.freedesktop.org/series/82063/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9049_full -> Patchwork_18563_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_18563_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@psr2:
- shard-iclb: [PASS][1] -> [SKIP][2] ([i915#658])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-iclb2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-iclb7/igt@[email protected]
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-glk: [PASS][3] -> [FAIL][4] ([i915#2389]) +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-glk4/igt@gem_exec_reloc@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-glk3/igt@gem_exec_reloc@[email protected]
* igt@gem_exec_whisper@basic-fds-forked-all:
- shard-glk: [PASS][5] -> [DMESG-WARN][6] ([i915#118] / [i915#95])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-glk6/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-glk9/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][7] -> [SKIP][8] ([i915#2190])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-tglb1/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-tglb6/igt@[email protected]
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-skl: [PASS][9] -> [TIMEOUT][10] ([i915#1958] / [i915#2424])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl4/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl5/igt@[email protected]
* igt@i915_selftest@mock@requests:
- shard-skl: [PASS][11] -> [INCOMPLETE][12] ([i915#198] / [i915#2278])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl2/igt@i915_selftest@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl9/igt@i915_selftest@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- shard-skl: [PASS][13] -> [DMESG-WARN][14] ([i915#1982]) +6 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl8/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl10/igt@[email protected]
* igt@kms_flip@flip-vs-suspend@b-edp1:
- shard-skl: [PASS][15] -> [INCOMPLETE][16] ([i915#198])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl10/igt@kms_flip@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl1/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-render:
- shard-tglb: [PASS][17] -> [DMESG-WARN][18] ([i915#1982]) +2 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-tglb7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-render.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-tglb1/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-render.html
* igt@kms_psr@psr2_suspend:
- shard-iclb: [PASS][19] -> [SKIP][20] ([fdo#109441]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-iclb2/igt@kms_psr@psr2_suspend.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-iclb7/igt@kms_psr@psr2_suspend.html
#### Possible fixes ####
* igt@gem_exec_whisper@basic-queues-priority:
- shard-glk: [DMESG-WARN][21] ([i915#118] / [i915#95]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-glk5/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-glk4/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [DMESG-WARN][23] ([i915#1436] / [i915#716]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-kbl1/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-kbl7/igt@[email protected]
* igt@i915_module_load@reload:
- shard-apl: [DMESG-WARN][25] ([i915#1635] / [i915#1982]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-apl3/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-apl6/igt@[email protected]
* igt@i915_selftest@mock@contexts:
- shard-apl: [INCOMPLETE][27] ([i915#1635] / [i915#2278]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-apl8/igt@i915_selftest@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-apl7/igt@i915_selftest@[email protected]
* igt@i915_suspend@fence-restore-untiled:
- shard-skl: [INCOMPLETE][29] ([i915#198]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl10/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl2/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [DMESG-WARN][31] ([i915#180]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-kbl7/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-kbl7/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-b-128x128-bottom-edge:
- shard-kbl: [DMESG-WARN][33] ([i915#1982]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-kbl6/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-kbl2/igt@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1:
- shard-skl: [FAIL][35] ([i915#2122]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl5/igt@kms_flip@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][37] ([i915#1188]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl1/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl3/igt@[email protected]
* igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping:
- shard-skl: [DMESG-WARN][39] ([i915#1982]) -> [PASS][40] +8 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl6/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl8/igt@[email protected]
* igt@kms_psr2_su@page_flip:
- shard-iclb: [SKIP][41] ([fdo#109642] / [fdo#111068]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-iclb5/igt@kms_psr2_su@page_flip.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-iclb2/igt@kms_psr2_su@page_flip.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][43] ([fdo#109441]) -> [PASS][44] +3 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-iclb5/igt@kms_psr@psr2_sprite_plane_move.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_vblank@pipe-d-wait-idle:
- shard-tglb: [DMESG-WARN][45] ([i915#1982]) -> [PASS][46] +2 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-tglb1/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-tglb6/igt@[email protected]
* igt@perf@polling-small-buf:
- shard-iclb: [FAIL][47] ([i915#1722]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-iclb3/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-iclb5/igt@[email protected]
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][49] ([i915#588]) -> [SKIP][50] ([i915#658])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-iclb2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-iclb4/igt@[email protected]
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][51] ([fdo#110321] / [fdo#110336] / [i915#1635]) -> [TIMEOUT][52] ([i915#1319] / [i915#1635] / [i915#1958])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-apl4/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-apl1/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [TIMEOUT][53] ([i915#1319] / [i915#1635]) -> [TIMEOUT][54] ([i915#1319] / [i915#1635] / [i915#1958])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-apl6/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-apl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [DMESG-FAIL][55] ([fdo#108145] / [i915#1982]) -> [FAIL][56] ([fdo#108145] / [i915#265])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9049/shard-skl4/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/shard-skl5/igt@[email protected]
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2278]: https://gitlab.freedesktop.org/drm/intel/issues/2278
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#2424]: https://gitlab.freedesktop.org/drm/intel/issues/2424
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_9049 -> Patchwork_18563
CI-20190529: 20190529
CI_DRM_9049: 6a36f5cbd72a6547eb096c2dcd130fc38861c649 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5787: 0ec962017c8131de14e0cb038f7f76b1f17ed637 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18563: 18c3303e9cc0a187606713181f8a87199d90d2d7 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18563/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [01/11] mm: update the documentation for vfree (rev2)
In reply to Christoph Hellwig== Series Details ==
== Series Details ==
Series: series starting with [01/11] mm: update the documentation for vfree (rev2)
URL : https://patchwork.freedesktop.org/series/82063/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9057 -> Patchwork_18576
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/index.html
Known issues
------------
Here are the changes found in Patchwork_18576 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/fi-bsw-kefka/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/fi-bsw-kefka/igt@[email protected]
#### Possible fixes ####
* igt@debugfs_test@read_all_entries:
- fi-bsw-nick: [INCOMPLETE][3] ([i915#1250] / [i915#1436]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/fi-bsw-nick/igt@debugfs_test@read_all_entries.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/fi-bsw-nick/igt@debugfs_test@read_all_entries.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-bsw-kefka: [INCOMPLETE][5] -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/fi-bsw-kefka/igt@i915_selftest@live@gt_heartbeat.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/fi-bsw-kefka/igt@i915_selftest@live@gt_heartbeat.html
#### Warnings ####
* igt@i915_pm_rpm@module-reload:
- fi-kbl-x1275: [DMESG-FAIL][7] ([i915#62] / [i915#95]) -> [DMESG-FAIL][8] ([i915#62])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/fi-kbl-x1275/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/fi-kbl-x1275/igt@[email protected]
* igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size:
- fi-kbl-x1275: [DMESG-WARN][9] ([i915#62] / [i915#92]) -> [DMESG-WARN][10] ([i915#62] / [i915#92] / [i915#95]) +3 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/fi-kbl-x1275/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/fi-kbl-x1275/igt@[email protected]
* igt@kms_force_connector_basic@prune-stale-modes:
- fi-kbl-x1275: [DMESG-WARN][11] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][12] ([i915#62] / [i915#92]) +2 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/fi-kbl-x1275/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/fi-kbl-x1275/igt@[email protected]
* igt@vgem_basic@unload:
- fi-kbl-x1275: [DMESG-WARN][13] ([i915#62] / [i915#92]) -> [DMESG-WARN][14] ([i915#95])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/fi-kbl-x1275/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/fi-kbl-x1275/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1250]: https://gitlab.freedesktop.org/drm/intel/issues/1250
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#289]: https://gitlab.freedesktop.org/drm/intel/issues/289
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (45 -> 39)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9057 -> Patchwork_18576
CI-20190529: 20190529
CI_DRM_9057: f812e3c53df08387b5b322aef7f911f21e77aa05 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5788: a7520973a210b7268c3039902789f433ee0f5ef7 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18576: c11fe008f1751502cedfffb96abe32165940beae @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
c11fe008f175 mm: remove alloc_vm_areae6569a322009 x86/xen: open code alloc_vm_area in arch_gnttab_valloc ee890e84c9e2 xen/xenbus: use apply_to_page_range directly in xenbus_map_ring_pv df7c4a828c36 drm/i915: use vmap in i915_gem_object_map fd8fa2d72d09 drm/i915: stop using kmap in i915_gem_object_map 179e795ffba4 drm/i915: use vmap in shmem_pin_map1dae0eeec9bf zsmalloc: switch from alloc_vm_area to get_vm_area 4b84416af184 mm: allow a NULL fn callback in apply_to_page_range b9e9e60819f1 mm: add a vmap_pfn functioncae4673f131a mm: add a VM_MAP_PUT_PAGES flag for vmap7433a994ce52 mm: update the documentation for vfree
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [01/11] mm: update the documentation for vfree (rev2)
In reply to Christoph Hellwig== Series Details ==
== Series Details ==
Series: series starting with [01/11] mm: update the documentation for vfree (rev2)
URL : https://patchwork.freedesktop.org/series/82063/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9057_full -> Patchwork_18576_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_18576_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@psr2:
- shard-iclb: [PASS][1] -> [SKIP][2] ([i915#658])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb8/igt@[email protected]
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-skl: [PASS][3] -> [TIMEOUT][4] ([i915#1958] / [i915#2424])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl3/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl1/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [PASS][5] -> [DMESG-WARN][6] ([i915#1436] / [i915#716])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl5/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl3/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [PASS][7] -> [FAIL][8] ([i915#454])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb8/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb4/igt@[email protected]
* igt@i915_selftest@mock@contexts:
- shard-skl: [PASS][9] -> [INCOMPLETE][10] ([i915#198] / [i915#2278])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl4/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl7/igt@i915_selftest@[email protected]
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-kbl: [PASS][11] -> [DMESG-WARN][12] ([i915#180])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-kbl1/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-kbl4/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-skl: [PASS][13] -> [INCOMPLETE][14] ([i915#300])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl3/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl1/igt@[email protected]
* igt@kms_flip@2x-flip-vs-dpms-off-vs-modeset-interruptible@ab-vga1-hdmi-a1:
- shard-hsw: [PASS][15] -> [DMESG-WARN][16] ([i915#1982])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-hsw4/igt@kms_flip@2x-flip-vs-dpms-off-vs-modeset-interruptible@ab-vga1-hdmi-a1.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-hsw6/igt@kms_flip@2x-flip-vs-dpms-off-vs-modeset-interruptible@ab-vga1-hdmi-a1.html
* igt@kms_flip@flip-vs-suspend@a-edp1:
- shard-skl: [PASS][17] -> [DMESG-WARN][18] ([i915#1982]) +8 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl7/igt@kms_flip@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite:
- shard-kbl: [PASS][19] -> [DMESG-WARN][20] ([i915#1982])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [PASS][21] -> [FAIL][22] ([i915#1188])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-kbl7/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-kbl7/igt@[email protected]
* igt@kms_psr2_su@page_flip:
- shard-iclb: [PASS][23] -> [SKIP][24] ([fdo#109642] / [fdo#111068])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb2/igt@kms_psr2_su@page_flip.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb7/igt@kms_psr2_su@page_flip.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb1/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@perf@polling-parameterized:
- shard-kbl: [PASS][27] -> [FAIL][28] ([i915#1542])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-kbl1/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-kbl4/igt@[email protected]
#### Possible fixes ####
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [SKIP][29] ([i915#2190]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-tglb6/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-tglb8/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [FAIL][31] ([i915#644]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-glk5/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-glk5/igt@[email protected]
* igt@gem_userptr_blits@unsync-unmap-cycles:
- shard-skl: [TIMEOUT][33] ([i915#1958]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl6/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl2/igt@[email protected]
* igt@i915_selftest@mock@contexts:
- shard-apl: [INCOMPLETE][35] ([i915#1635] / [i915#2278]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-apl2/igt@i915_selftest@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-apl2/igt@i915_selftest@[email protected]
* igt@i915_suspend@forcewake:
- shard-kbl: [DMESG-WARN][37] ([i915#180]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-kbl6/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-kbl2/igt@[email protected]
* igt@kms_big_fb@x-tiled-64bpp-rotate-180:
- shard-apl: [DMESG-WARN][39] ([i915#1635] / [i915#1982]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-apl2/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-apl2/igt@[email protected]
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
- shard-hsw: [FAIL][41] ([i915#96]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-hsw6/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-hsw4/igt@[email protected]
* igt@kms_cursor_legacy@cursor-vs-flip-toggle:
- shard-skl: [DMESG-WARN][43] ([i915#1982]) -> [PASS][44] +2 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl6/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl2/igt@[email protected]
* igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions:
- shard-tglb: [DMESG-WARN][45] ([i915#1982]) -> [PASS][46] +3 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-tglb2/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-tglb2/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions.html
* igt@kms_draw_crc@fill-fb:
- shard-skl: [FAIL][47] ([i915#52]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl1/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl10/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-skl: [FAIL][49] ([i915#79]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl7/igt@kms_flip@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][51] ([fdo#108145] / [i915#265]) -> [PASS][52] +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl5/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl7/igt@[email protected]
* igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping:
- shard-iclb: [DMESG-WARN][53] ([i915#1982]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb3/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb5/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][55] ([fdo#109642] / [fdo#111068]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb2/igt@[email protected]
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][57] ([fdo#109441]) -> [PASS][58] +3 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb1/igt@kms_psr@psr2_sprite_plane_move.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][59] ([i915#588]) -> [SKIP][60] ([i915#658])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-iclb2/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-iclb7/igt@[email protected]
* igt@kms_color@pipe-c-ctm-max:
- shard-skl: [DMESG-WARN][61] ([i915#1982]) -> [DMESG-FAIL][62] ([i915#1982])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9057/shard-skl10/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/shard-skl6/igt@[email protected]
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2278]: https://gitlab.freedesktop.org/drm/intel/issues/2278
[i915#2424]: https://gitlab.freedesktop.org/drm/intel/issues/2424
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#300]: https://gitlab.freedesktop.org/drm/intel/issues/300
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#52]: https://gitlab.freedesktop.org/drm/intel/issues/52
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#96]: https://gitlab.freedesktop.org/drm/intel/issues/96
Participating hosts (10 -> 11)
------------------------------
Additional (1): pig-icl-1065g7
Build changes
-------------
* Linux: CI_DRM_9057 -> Patchwork_18576
CI-20190529: 20190529
CI_DRM_9057: f812e3c53df08387b5b322aef7f911f21e77aa05 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5788: a7520973a210b7268c3039902789f433ee0f5ef7 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18576: c11fe008f1751502cedfffb96abe32165940beae @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18576/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Andrew Morton
maintainerQuoted 10 lines · On Thu, 24 Sep 2020 15:58:42 +0200 Christoph Hellwig <[email protected]> wrote:
this series removes
alloc_vm_area, which was left over from the big vmalloc interface rework. It is a rather arkane interface, basicaly the equivalent ofget_vm_area+ actually faulting in all PTEs in the allocated area. It was originally addeds for Xen (which isn't modular to start with), and then grew users in zsmalloc and i915 which seems to mostly qualify as abuses of the interface, especially for i915 as a random driver should not set up PTE bits directly.Note that the i915 patches apply to the drm-tip branch of the drm-tip tree, as that tree has recent conflicting commits in the same area.
Is the drm-tip material in linux-next yet? I'm still seeing a non-trivial reject in there at present.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 10 lines · Andrew Morton
Quoted 8 lines · On Thu, 24 Sep 2020 15:58:42 +0200 Christoph Hellwig <[email protected]> wrote:
this series removes
alloc_vm_area, which was left over from the big vmalloc interface rework. It is a rather arkane interface, basicaly the equivalent ofget_vm_area+ actually faulting in all PTEs in the allocated area. It was originally addeds for Xen (which isn't modular to start with), and then grew users in zsmalloc and i915 which seems to mostly qualify as abuses of the interface, especially for i915 as a random driver should not set up PTE bits directly.
Quoted 5 lines
Quoted 2 lines
Note that the i915 patches apply to the drm-tip branch of the drm-tip tree, as that tree has recent conflicting commits in the same area.
Is the drm-tip material in linux-next yet? I'm still seeing a non-trivial reject in there at present.
I assumed it was, but the reject imply that they aren't. Tvrtko, do you know the details?
Joonas Lahtinen
maintainer+ Dave and Daniel
+ Stephen
Quoting Christoph Hellwig (2020-09-26 09:29:59)
Quoted 11 lines · Andrew Morton
Quoted 10 lines · On Thu, 24 Sep 2020 15:58:42 +0200 Christoph Hellwig <[email protected]> wrote:
Quoted 9 lines
this series removes
alloc_vm_area, which was left over from the big vmalloc interface rework. It is a rather arkane interface, basicaly the equivalent ofget_vm_area+ actually faulting in all PTEs in the allocated area. It was originally addeds for Xen (which isn't modular to start with), and then grew users in zsmalloc and i915 which seems to mostly qualify as abuses of the interface, especially for i915 as a random driver should not set up PTE bits directly.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Note that the i915 patches apply to the drm-tip branch of the drm-tip tree, as that tree has recent conflicting commits in the same area.
Is the drm-tip material in linux-next yet? I'm still seeing a non-trivial reject in there at present.
I assumed it was, but the reject imply that they aren't. Tvrtko, do you know the details?
I think we have a gap that after splitting the drm-intel-next pull requests into two the drm-intel/for-linux-next branch is now missing material from drm-intel/drm-intel-gt-next.
I think a simple course of action might be to start including drm-intel-gt-next in linux-next, which would mean that we should update DIM tooling to add extra branch "drm-intel/gt-for-linux-next" or so.
Which specific patches are missing in this case?
Regards, Joonas
Quoted 9 lines · Joonas Lahtinen
I think we have a gap that after splitting the drm-intel-next pull requests into two the drm-intel/for-linux-next branch is now missing material from drm-intel/drm-intel-gt-next.
I think a simple course of action might be to start including drm-intel-gt-next in linux-next, which would mean that we should update DIM tooling to add extra branch "drm-intel/gt-for-linux-next" or so.
Which specific patches are missing in this case?
The two dependencies required by my series not in mainline are:
drm/i915/gem: Avoid implicit vmap for highmem on x86-32 drm/i915/gem: Prevent using pgprot_writecombine() if PAT is not supported
so it has to be one or both of those.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Joonas Lahtinen
maintainerQuoting Christoph Hellwig (2020-09-28 15:37:41)
Quoted 9 lines · Joonas Lahtinen
Quoted 8 lines
I think we have a gap that after splitting the drm-intel-next pull requests into two the drm-intel/for-linux-next branch is now missing material from drm-intel/drm-intel-gt-next.
I think a simple course of action might be to start including drm-intel-gt-next in linux-next, which would mean that we should update DIM tooling to add extra branch "drm-intel/gt-for-linux-next" or so.
Quoted 8 lines
Quoted 1 line
Which specific patches are missing in this case?
The two dependencies required by my series not in mainline are:
drm/i915/gem: Avoid implicit vmap for highmem on x86-32 drm/i915/gem: Prevent using
pgprot_writecombine()if PAT is not supportedso it has to be one or both of those.
Hmm, those are both committed after our last -next pull request, so they would normally only target next merge window. drm-next closes the merge window around -rc5 already.
But, in this specific case those are both Fixes: patches with Cc: stable, so they should be pulled into drm-intel-next-fixes PR.
Rodrigo, can you cherry-pick those patches to -next-fixes that you send to Dave?
Regards, Joonas
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 9 lines · Joonas Lahtinen
Hmm, those are both committed after our last -next pull request, so they would normally only target next merge window. drm-next closes the merge window around -rc5 already.
But, in this specific case those are both Fixes: patches with Cc: stable, so they should be pulled into drm-intel-next-fixes PR.
Rodrigo, can you cherry-pick those patches to -next-fixes that you send to Dave?
They still haven't made it to linux-next. I think for now I'll just rebase without them again and then you can handle the conflicts for 5.11.
Quoted 9 lines · Christoph Hellwig
Quoted 7 lines · Joonas Lahtinen
Hmm, those are both committed after our last -next pull request, so they would normally only target next merge window. drm-next closes the merge window around -rc5 already.
But, in this specific case those are both Fixes: patches with Cc: stable, so they should be pulled into drm-intel-next-fixes PR.
Quoted 6 lines
Quoted 2 lines
Rodrigo, can you cherry-pick those patches to -next-fixes that you send to Dave?
They still haven't made it to linux-next. I think for now I'll just rebase without them again and then you can handle the conflicts for 5.11.
Yeah after -rc6 drm is frozen for features, so anything that's stuck in subordinate trees rolls over to the next merge cycle. To avoid upsetting sfr from linux-next we keep those -next branches out of linux-next until after -rc1 again. iow, rebasing onto linux-next and smashing this into 5.10 sounds like the right approach (since everyone else freezes a bunch later afaik).
Cheers, Daniel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx