All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Bohan <mbohan@codeaurora.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Zhou Zhu <zzhu3@marvell.com>, Bin Wang <binw@marvell.com>,
	Chao Xie <cxie4@marvell.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Leo Yan <leoy@marvell.com>,
	linux-arm-msm@vger.kernel.org
Subject: Re: memcpy alignment for DEVICE_nGnRnE
Date: Mon, 7 Apr 2014 17:35:47 -0700	[thread overview]
Message-ID: <20140408003547.GA18321@codeaurora.org> (raw)
In-Reply-To: <20140221105307.GE25363@localhost>

Hi Catalin,

On Fri, Feb 21, 2014 at 10:53:08AM +0000, Catalin Marinas wrote:
> On Fri, Feb 21, 2014 at 09:58:27AM +0000, Zhou Zhu wrote:
> > We faced one issue using memcpy for memory type DEVICE_nGnRnE 
> > (pgprot_noncached). If the address is not aligned, exception would 
> > happen due to the alignment of this type could not be handled by hardware.
> 
> Indeed, that's expected. This memory type is the equivalent of Strongly
> Ordered.
> 
> > Is there any plan and ongoing patch to support this or we need to keep 
> > address aligned for memcpy using pgprot_noncached memory in drivers?
> 
> You either change the memory type to pgprot_writecombine() or use the
> right API (memcpy_toio/memcpy_fromio, these could be further optimised,
> similar to powerpc for example, but I didn't get there yet).

How should we handle Device Memory with copy_from_user / copy_to_user?
Should we follow the same scheme and create
copy_from_user_io / copy_to_user_io, or rather enforce that the stock
routines handle alignment?

Thanks,
Mike

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

WARNING: multiple messages have this Message-ID (diff)
From: mbohan@codeaurora.org (Michael Bohan)
To: linux-arm-kernel@lists.infradead.org
Subject: memcpy alignment for DEVICE_nGnRnE
Date: Mon, 7 Apr 2014 17:35:47 -0700	[thread overview]
Message-ID: <20140408003547.GA18321@codeaurora.org> (raw)
In-Reply-To: <20140221105307.GE25363@localhost>

Hi Catalin,

On Fri, Feb 21, 2014 at 10:53:08AM +0000, Catalin Marinas wrote:
> On Fri, Feb 21, 2014 at 09:58:27AM +0000, Zhou Zhu wrote:
> > We faced one issue using memcpy for memory type DEVICE_nGnRnE 
> > (pgprot_noncached). If the address is not aligned, exception would 
> > happen due to the alignment of this type could not be handled by hardware.
> 
> Indeed, that's expected. This memory type is the equivalent of Strongly
> Ordered.
> 
> > Is there any plan and ongoing patch to support this or we need to keep 
> > address aligned for memcpy using pgprot_noncached memory in drivers?
> 
> You either change the memory type to pgprot_writecombine() or use the
> right API (memcpy_toio/memcpy_fromio, these could be further optimised,
> similar to powerpc for example, but I didn't get there yet).

How should we handle Device Memory with copy_from_user / copy_to_user?
Should we follow the same scheme and create
copy_from_user_io / copy_to_user_io, or rather enforce that the stock
routines handle alignment?

Thanks,
Mike

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2014-04-08  0:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53072343.4080505@marvell.com>
2014-02-21 10:53 ` memcpy alignment for DEVICE_nGnRnE Catalin Marinas
2014-04-08  0:35   ` Michael Bohan [this message]
2014-04-08  0:35     ` Michael Bohan
2014-04-08 11:49     ` Catalin Marinas
2014-04-08 11:49       ` Catalin Marinas
2014-04-08 23:39       ` Michael Bohan
2014-04-08 23:39         ` Michael Bohan
2014-04-09  8:17         ` Catalin Marinas
2014-04-09  8:17           ` Catalin Marinas

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=20140408003547.GA18321@codeaurora.org \
    --to=mbohan@codeaurora.org \
    --cc=binw@marvell.com \
    --cc=catalin.marinas@arm.com \
    --cc=cxie4@marvell.com \
    --cc=leoy@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=zzhu3@marvell.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.