All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jonas Bonn <jonas@southpole.se>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Stafford Horne <shorne@gmail.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	openrisc@lists.librecores.org, iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: provide in-place uncached remapping for dma-direct (resend)
Date: Thu, 20 Feb 2020 09:01:37 -0800	[thread overview]
Message-ID: <20200220170139.387354-1-hch@lst.de> (raw)

Hi all,

this series provides support for remapping places uncached in-place in
the generic dma-direct code, and moves openrisc over from its own
in-place remapping scheme.  The arm64 folks also had interest in such
a scheme to avoid problems with speculating into cache aliases.

Also all architectures that always use small page mappings for the
kernel and have non-coherent DMA should look into enabling this
scheme, as it is much more efficient than the vmap remapping.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jonas Bonn <jonas@southpole.se>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Stafford Horne <shorne@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	linux-arch@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	openrisc@lists.librecores.org, Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: provide in-place uncached remapping for dma-direct (resend)
Date: Thu, 20 Feb 2020 09:01:37 -0800	[thread overview]
Message-ID: <20200220170139.387354-1-hch@lst.de> (raw)

Hi all,

this series provides support for remapping places uncached in-place in
the generic dma-direct code, and moves openrisc over from its own
in-place remapping scheme.  The arm64 folks also had interest in such
a scheme to avoid problems with speculating into cache aliases.

Also all architectures that always use small page mappings for the
kernel and have non-coherent DMA should look into enabling this
scheme, as it is much more efficient than the vmap remapping.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jonas Bonn <jonas@southpole.se>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Stafford Horne <shorne@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	linux-arch@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	openrisc@lists.librecores.org, Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: provide in-place uncached remapping for dma-direct (resend)
Date: Thu, 20 Feb 2020 09:01:37 -0800	[thread overview]
Message-ID: <20200220170139.387354-1-hch@lst.de> (raw)

Hi all,

this series provides support for remapping places uncached in-place in
the generic dma-direct code, and moves openrisc over from its own
in-place remapping scheme.  The arm64 folks also had interest in such
a scheme to avoid problems with speculating into cache aliases.

Also all architectures that always use small page mappings for the
kernel and have non-coherent DMA should look into enabling this
scheme, as it is much more efficient than the vmap remapping.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] provide in-place uncached remapping for dma-direct (resend)
Date: Thu, 20 Feb 2020 09:01:37 -0800	[thread overview]
Message-ID: <20200220170139.387354-1-hch@lst.de> (raw)

Hi all,

this series provides support for remapping places uncached in-place in
the generic dma-direct code, and moves openrisc over from its own
in-place remapping scheme.  The arm64 folks also had interest in such
a scheme to avoid problems with speculating into cache aliases.

Also all architectures that always use small page mappings for the
kernel and have non-coherent DMA should look into enabling this
scheme, as it is much more efficient than the vmap remapping.

             reply	other threads:[~2020-02-20 17:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 17:01 Christoph Hellwig [this message]
2020-02-20 17:01 ` [OpenRISC] provide in-place uncached remapping for dma-direct (resend) Christoph Hellwig
2020-02-20 17:01 ` Christoph Hellwig
2020-02-20 17:01 ` Christoph Hellwig
2020-02-20 17:01 ` [PATCH 1/2] dma-mapping: support setting memory uncached in place Christoph Hellwig
2020-02-20 17:01   ` [OpenRISC] " Christoph Hellwig
2020-02-20 17:01   ` Christoph Hellwig
2020-02-20 17:01   ` Christoph Hellwig
2020-02-20 17:01   ` Christoph Hellwig
2020-02-20 17:21   ` Robin Murphy
2020-02-20 17:21     ` [OpenRISC] " Robin Murphy
2020-02-20 17:21     ` Robin Murphy
2020-02-20 17:21     ` Robin Murphy
2020-02-21 14:16     ` Christoph Hellwig
2020-02-21 14:16       ` [OpenRISC] " Christoph Hellwig
2020-02-21 14:16       ` Christoph Hellwig
2020-02-21 14:16       ` Christoph Hellwig
2020-02-20 17:01 ` [PATCH 2/2] openrisc: use the generic in-place uncached DMA allocator Christoph Hellwig
2020-02-20 17:01   ` [OpenRISC] " Christoph Hellwig
2020-02-20 17:01   ` Christoph Hellwig
2020-02-20 17:01   ` Christoph Hellwig
2020-02-20 17:01   ` Christoph Hellwig
2020-02-21 22:14   ` Stafford Horne
2020-02-21 22:14     ` [OpenRISC] " Stafford Horne
2020-02-21 22:14     ` Stafford Horne
2020-02-21 22:14     ` Stafford Horne
2020-02-24 19:45     ` Christoph Hellwig
2020-02-24 19:45       ` [OpenRISC] " Christoph Hellwig
2020-02-24 19:45       ` Christoph Hellwig
2020-02-24 19:45       ` Christoph Hellwig
2020-02-25 10:10       ` Stafford Horne
2020-02-25 10:10         ` [OpenRISC] " Stafford Horne
2020-02-25 10:10         ` Stafford Horne
2020-02-25 10:10         ` Stafford Horne

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=20200220170139.387354-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jonas@southpole.se \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=openrisc@lists.librecores.org \
    --cc=robin.murphy@arm.com \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    --cc=will@kernel.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 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.