From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
iommu@lists.linux-foundation.org,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] swiotlb: Rate-limit printing and 64-bit memory debugging
Date: Mon, 31 Oct 2016 16:45:02 +0100 [thread overview]
Message-ID: <1477928704-10611-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Konrad, Jon,
This patch series contains two improvements for the SWIOTLB subsystem.
The first patch adds rate-limiting to an error message, to avoid
flooding the kernel log.
The second patch adds a kernel command line option to aid debugging when
developing support for DMA to memory outside the 32-bit address space.
Thanks for your comments!
Geert Uytterhoeven (2):
swiotlb: Rate-limit printing when running out of SW-IOMMU space
swiotlb: Add swiotlb=nobounce debug option
Documentation/kernel-parameters.txt | 3 ++-
lib/swiotlb.c | 23 +++++++++++++++++++----
2 files changed, 21 insertions(+), 5 deletions(-)
--
1.9.1
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
next reply other threads:[~2016-10-31 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 15:45 Geert Uytterhoeven [this message]
2016-10-31 15:45 ` [PATCH 1/2] swiotlb: Rate-limit printing when running out of SW-IOMMU space Geert Uytterhoeven
2016-10-31 16:02 ` Sergei Shtylyov
2016-11-05 19:40 ` Konrad Rzeszutek Wilk
2016-10-31 15:45 ` [PATCH 2/2] swiotlb: Add swiotlb=nobounce debug option Geert Uytterhoeven
2016-10-31 17:41 ` Robin Murphy
2016-10-31 18:20 ` Geert Uytterhoeven
2016-11-01 11:46 ` Robin Murphy
2016-11-07 15:41 ` Geert Uytterhoeven
2016-11-07 17:18 ` Robin Murphy
2016-10-31 17:52 ` Konrad Rzeszutek Wilk
2016-11-07 18:57 ` Geert Uytterhoeven
2016-11-07 19:20 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1477928704-10611-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=corbet@lwn.net \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).