Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap callback

Path	csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From	Greg KH <gregkh@linuxfoundation.org>
Newsgroups	linux.kernel
Subject	Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap callback
Date	Sat, 16 Sep 2017 03:30:02 +0200
Message-ID	<uqa5I-2Li-13@gated-at.bofh.it> (permalink)
References	<upLK1-30B-5@gated-at.bofh.it>
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Content-Disposition	inline
User-Agent	Mutt/1.9.0 (2017-09-02)
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	37
Organization	linux.* mail to news gateway
X-Original-Cc	stable@vger.kernel.org, linux-kernel@vger.kernel.org, julien.grall@arm.com, jgross@suse.com, boris.ostrovsky@oracle.com
X-Original-Date	Fri, 15 Sep 2017 18:23:52 -0700
X-Original-Message-ID	<20170916012352.GA21774@kroah.com>
X-Original-References	<alpine.DEB.2.10.1709141535260.9439@sstabellini-ThinkPad-X260>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1733187

Show key headers only | View raw

On Thu, Sep 14, 2017 at 04:23:05PM -0700, Stefano Stabellini wrote:
> Hi all,
> 
> We are getting reports from Xen on ARM users about DMA issues. The
> problem is that the commit below
> (7e91c7df29b5e196de3dc6f086c8937973bd0b88) is necessary to support mmap
> on Xen on ARM. It is self-contained and doesn't affect anything outside
> of Xen on ARM, so I think is a good candidate for backporting. It went
> upstream in 4.11.

But it's a new feature, right?  How does that fit the stable kernel
rules?

> 
> 
> Could you please backport the following commit:
> 
>   commit 7e91c7df29b5e196de3dc6f086c8937973bd0b88
>   Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>   Date:   Tue Feb 7 19:58:02 2017 +0200
>   
>       swiotlb-xen: implement xen_swiotlb_dma_mmap callback
>       
>       This function creates userspace mapping for the DMA-coherent memory.
>     
> to the stable trees up until 3.14?
> 
> 
> Because of 00085f1efa387a8ce100e3734920f7639c80caa3 "dma-mapping: use
> unsigned long for dma_attrs", the appended patch (to be applied on top)
> is required for trees older than 4.8. 

What does the kvm maintainers think about this?

thanks,

greg k-h

Thread

[BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap callback Stefano Stabellini <sstabellini@kernel.org> - 2017-09-15 01:30 +0200
  Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap callback Greg KH <gregkh@linuxfoundation.org> - 2017-09-16 03:30 +0200
    Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap  callback Stefano Stabellini <sstabellini@kernel.org> - 2017-09-18 20:10 +0200
      Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap callback Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2017-09-18 21:00 +0200
        Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap  callback Stefano Stabellini <sstabellini@kernel.org> - 2017-09-20 00:00 +0200
      Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap  callback Stefano Stabellini <sstabellini@kernel.org> - 2017-09-21 02:40 +0200
      Re: [BACKPORT] swiotlb-xen: implement xen_swiotlb_dma_mmap callback Juergen Gross <jgross@suse.com> - 2017-09-22 14:20 +0200

csiph-web