All of lore.kernel.org
 help / color / mirror / Atom feed
From: brian.starkey@arm.com (Brian Starkey)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Fix kernel panic in dma-coherent allocations
Date: Mon, 29 Feb 2016 16:09:20 +0000	[thread overview]
Message-ID: <cover.1456225103.git.brian.starkey@arm.com> (raw)

Hi,

These patches implement a MEMREMAP_WC flag for memremap(), which can
be used to obtain writecombine mappings. This is then used for setting
up dma_coherent_mem regions which use the DMA_MEMORY_MAP flag.

The motivation is to fix an alignment fault on arm64, and the
suggestion to implement MEMREMAP_WC for this case was made at [1].
That particular issue is handled in patch 4, which makes sure that the
appropriate memset function is used when zeroing allocations mapped as
IO memory.

Best Regards,
Brian

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-December/390857.html

Changes since v1:
* Added preparatory patch removing flag modifications in memremap()
  (Suggested by Andrew Morton)
* Rebase onto linux-next

Brian Starkey (4):
  memremap: don't modify flags
  memremap: add MEMREMAP_WC flag.
  drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MAP
  drivers: dma-coherent: use memset_io for DMA_MEMORY_IO mappings

 drivers/base/dma-coherent.c |   25 ++++++++++++++++++++-----
 include/linux/io.h          |    1 +
 kernel/memremap.c           |   24 +++++++++++++++---------
 3 files changed, 36 insertions(+), 14 deletions(-)

-- 
1.7.9.5

WARNING: multiple messages have this Message-ID (diff)
From: Brian Starkey <brian.starkey@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Fix kernel panic in dma-coherent allocations
Date: Mon, 29 Feb 2016 16:09:20 +0000	[thread overview]
Message-ID: <cover.1456225103.git.brian.starkey@arm.com> (raw)

Hi,

These patches implement a MEMREMAP_WC flag for memremap(), which can
be used to obtain writecombine mappings. This is then used for setting
up dma_coherent_mem regions which use the DMA_MEMORY_MAP flag.

The motivation is to fix an alignment fault on arm64, and the
suggestion to implement MEMREMAP_WC for this case was made at [1].
That particular issue is handled in patch 4, which makes sure that the
appropriate memset function is used when zeroing allocations mapped as
IO memory.

Best Regards,
Brian

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-December/390857.html

Changes since v1:
* Added preparatory patch removing flag modifications in memremap()
  (Suggested by Andrew Morton)
* Rebase onto linux-next

Brian Starkey (4):
  memremap: don't modify flags
  memremap: add MEMREMAP_WC flag.
  drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MAP
  drivers: dma-coherent: use memset_io for DMA_MEMORY_IO mappings

 drivers/base/dma-coherent.c |   25 ++++++++++++++++++++-----
 include/linux/io.h          |    1 +
 kernel/memremap.c           |   24 +++++++++++++++---------
 3 files changed, 36 insertions(+), 14 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2016-02-29 16:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 16:09 Brian Starkey [this message]
2016-02-29 16:09 ` [PATCH v2 0/4] Fix kernel panic in dma-coherent allocations Brian Starkey
2016-02-29 16:09 ` [PATCH v2 1/4] memremap: don't modify flags Brian Starkey
2016-02-29 16:09   ` Brian Starkey
2016-02-29 16:09 ` [PATCH v2 2/4] memremap: add MEMREMAP_WC flag Brian Starkey
2016-02-29 16:09   ` Brian Starkey
2016-02-29 16:09 ` [PATCH v2 3/4] drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MAP Brian Starkey
2016-02-29 16:09   ` Brian Starkey
2016-02-29 16:09 ` [PATCH v2 4/4] drivers: dma-coherent: use memset_io for DMA_MEMORY_IO mappings Brian Starkey
2016-02-29 16:09   ` Brian Starkey
2016-02-29 23:17   ` Andrew Morton
2016-02-29 23:17     ` Andrew Morton
2016-03-01  9:03     ` Brian Starkey
2016-03-01  9:03       ` Brian Starkey

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.1456225103.git.brian.starkey@arm.com \
    --to=brian.starkey@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.