Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1544572
| From | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option |
| Date | 2016-12-19 15:40 +0100 |
| Message-ID | <sQ7gC-Ek-29@gated-at.bofh.it> (permalink) |
| References | <sP0Kd-4gJ-3@gated-at.bofh.it> <sP0Ke-4gJ-21@gated-at.bofh.it> <sQ6kx-8mS-25@gated-at.bofh.it> <sQ6DU-8us-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Dec 19, 2016 at 02:57:00PM +0100, Geert Uytterhoeven wrote: > Hi Konrad, > > On Mon, Dec 19, 2016 at 2:38 PM, Konrad Rzeszutek Wilk > <konrad@darnok.org> 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 <geert+renesas@glider.be> > > > > 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? Ah that does indeed work. Which means I can't push it to Linus until rc2 at least. Linus is sad when he sees git pulls that hadn't "soaked" for two weeks in linux-next - and especially patches on top of merges during the merge window. > > Please let me know what to do. Thanks! Building and testing them now. Wish there was some travis script to do this.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v2 0/3] swiotlb: Add swiotlb=noforce debug option Geert Uytterhoeven <geert+renesas@glider.be> - 2016-12-16 14:30 +0100
[PATCH v2 2/3] swiotlb: Convert swiotlb_force from int to enum Geert Uytterhoeven <geert+renesas@glider.be> - 2016-12-16 14:30 +0100
[PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option Geert Uytterhoeven <geert+renesas@glider.be> - 2016-12-16 14:30 +0100
Re: [PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option Konrad Rzeszutek Wilk <konrad@darnok.org> - 2016-12-19 14:40 +0100
Re: [PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option Geert Uytterhoeven <geert@linux-m68k.org> - 2016-12-19 15:00 +0100
Re: [PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> - 2016-12-19 15:40 +0100
[PATCH v2 1/3] x86, swiotlb: Simplify pci_swiotlb_detect_override() Geert Uytterhoeven <geert+renesas@glider.be> - 2016-12-16 14:30 +0100
Re: [PATCH v2 0/3] swiotlb: Add swiotlb=noforce debug option Konrad Rzeszutek Wilk <konrad@darnok.org> - 2016-12-19 14:40 +0100
csiph-web