From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: MIME-Version: 1.0 In-Reply-To: <20161219133817.GA4358@localhost.localdomain> References: <1481894922-28828-1-git-send-email-geert+renesas@glider.be> <1481894922-28828-4-git-send-email-geert+renesas@glider.be> <20161219133817.GA4358@localhost.localdomain> From: Geert Uytterhoeven Date: Mon, 19 Dec 2016 14:57:00 +0100 Message-ID: Subject: Re: [PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option To: Konrad Rzeszutek Wilk Cc: Geert Uytterhoeven , Konrad Rzeszutek Wilk , Jonathan Corbet , Catalin Marinas , Will Deacon , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Boris Ostrovsky , David Vrabel , Juergen Gross , Steven Rostedt , "linux-kernel@vger.kernel.org" , Linux-Renesas Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: Hi Konrad, On Mon, Dec 19, 2016 at 2:38 PM, Konrad Rzeszutek Wilk wrote: > On Fri, Dec 16, 2016 at 02:28:42PM +0100, Geert Uytterhoeven wrote: >> On architectures like arm64, swiotlb is tied intimately to the core >> architecture DMA support. In addition, ZONE_DMA cannot be disabled. >> >> To aid debugging and catch devices not supporting DMA to memory outside >> the 32-bit address space, add a kernel command line option >> "swiotlb=noforce", which disables the use of bounce buffers. >> If specified, trying to map memory that cannot be used with DMA will >> fail, and a rate-limited warning will be printed. >> >> Note that io_tlb_nslabs is set to 1, which is the minimal supported >> value. >> >> Signed-off-by: Geert Uytterhoeven > > What is this based on? I can't apply it on my latest that I had > sent to Linus? I rebased it on last Friday's linux-next, due to the recent move of kernel-parameters.txt. All the rest should be identical to your linux-next branch. > Could you rebase this one please on: > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb.git stable/for-linus-4.9 That one indeed doesn't have the move of kernel-parameters.txt. > Or if alternatively that does not - then please rebase it on > b5cab0da75c292ffa0fbd68dd2c820066b2842de However, my series already applies cleanly with git am on top of that commit? Please let me know what to do. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds