All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Tom Murphy <tmurphy@arista.com>
Cc: iommu@lists.linux-foundation.org, murphyt7@tcd.ie,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove old no iommu direct mapping code
Date: Fri, 26 Apr 2019 17:02:42 +0200	[thread overview]
Message-ID: <20190426150242.GL24576@8bytes.org> (raw)
In-Reply-To: <20190423200335.3888-1-tmurphy@arista.com>

On Tue, Apr 23, 2019 at 09:03:34PM +0100, Tom Murphy wrote:
> These checks were intended to handle devices not mapped by the IOMMU.
> Since the AMD IOMMU driver uses per-device dma_ops these functions can
> no longer be called by direct mapped devices. So these checks aren't
> needed anymore.
> 
> Signed-off-by: Tom Murphy <tmurphy@arista.com>
> ---
>  drivers/iommu/amd_iommu.c | 10 ++--------
>  1 file changed, 2 insertions(+), 8 deletions(-)

This has already been done by Christoph, see

	https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/commit/?id=7a5dbf3ab2f04905cf8468c66fcdbfb643068bcb

Regards,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Tom Murphy <tmurphy@arista.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	murphyt7@tcd.ie
Subject: Re: [PATCH] Remove old no iommu direct mapping code
Date: Fri, 26 Apr 2019 17:02:42 +0200	[thread overview]
Message-ID: <20190426150242.GL24576@8bytes.org> (raw)
Message-ID: <20190426150242.LCfdyR0WTKqxs4Y3X7e3RC0OqTlXpzV43egsc74VXTc@z> (raw)
In-Reply-To: <20190423200335.3888-1-tmurphy@arista.com>

On Tue, Apr 23, 2019 at 09:03:34PM +0100, Tom Murphy wrote:
> These checks were intended to handle devices not mapped by the IOMMU.
> Since the AMD IOMMU driver uses per-device dma_ops these functions can
> no longer be called by direct mapped devices. So these checks aren't
> needed anymore.
> 
> Signed-off-by: Tom Murphy <tmurphy@arista.com>
> ---
>  drivers/iommu/amd_iommu.c | 10 ++--------
>  1 file changed, 2 insertions(+), 8 deletions(-)

This has already been done by Christoph, see

	https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/commit/?id=7a5dbf3ab2f04905cf8468c66fcdbfb643068bcb

Regards,

	Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  parent reply	other threads:[~2019-04-26 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 20:03 [PATCH] Remove old no iommu direct mapping code Tom Murphy via iommu
2019-04-23 20:03 ` Tom Murphy
2019-04-23 20:03 ` Tom Murphy via iommu
2019-04-24  5:32 ` Christoph Hellwig
2019-04-24  5:32   ` Christoph Hellwig
2019-04-26 15:02 ` Joerg Roedel [this message]
2019-04-26 15:02   ` Joerg Roedel

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=20190426150242.GL24576@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=murphyt7@tcd.ie \
    --cc=tmurphy@arista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.