iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>,
	Jonathan Hunter
	<jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: [PATCH v2 0/2] TEGRA GART cleanup and new debug option
Date: Wed,  4 Oct 2017 04:02:29 +0300	[thread overview]
Message-ID: <cover.1507078770.git.digetx@gmail.com> (raw)

This is a continuation of the "iommu/tegra: gart: Couple corrections"
patchset that was send out quite some time ago and reviewed by Thierry Reding
recently.

Change log:

v2:
	- Dropped "Don't unnecessarily allocate registers context" patch
	  as it is not entirely correct.

	- Replaced "Correct number of unmapped bytes" and "Check whether page
	  is already mapped" patches with a new GART debug Kconfig option
	  patch.

Dmitry Osipenko (2):
  iommu/tegra: gart: Optionally check for overwriting of page mappings
  iommu/tegra: gart: Move PFN validation out of spinlock

 drivers/iommu/Kconfig      |  9 +++++++++
 drivers/iommu/tegra-gart.c | 20 +++++++++++++++++---
 2 files changed, 26 insertions(+), 3 deletions(-)

-- 
2.14.1

             reply	other threads:[~2017-10-04  1:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  1:02 Dmitry Osipenko [this message]
     [not found] ` <cover.1507078586.git.digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
     [not found]   ` <cover.1507078770.git.digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-04  1:02     ` [PATCH v2 1/2] iommu/tegra: gart: Add optional debug checking for overwriting of page mappings Dmitry Osipenko
     [not found]       ` <2eadfde76987532354e419ffc98aae44e4af489a.1507078586.git.digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-04  1:12         ` Dmitry Osipenko
2017-10-04  1:02     ` [PATCH v2 1/2] iommu/tegra: gart: Optionally check " Dmitry Osipenko
     [not found]       ` <7eea4a30b0f4fdbe14351cf2c6cf537365080d2d.1507078770.git.digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-10  9:53         ` Joerg Roedel
     [not found]           ` <20171010095342.jyvzl2zex2pynqvv-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-10-12 14:27             ` Dmitry Osipenko
     [not found]               ` <7dc66d59-3904-d1f8-3941-f9a534ff899a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-13  8:38                 ` Joerg Roedel
     [not found]                   ` <20171013083848.GA29513-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-10-13 12:52                     ` Dmitry Osipenko
2017-10-04  1:02     ` [PATCH v2 2/2] iommu/tegra: gart: Move PFN validation out of spinlock Dmitry Osipenko

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=cover.1507078770.git.digetx@gmail.com \
    --to=digetx-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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).