public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: mm: get_user_pages_fast()
Date: Wed, 6 Nov 2013 10:19:02 +0000	[thread overview]
Message-ID: <20131106101901.GA21074@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <52797483.2000105@cs.bris.ac.uk>

On Tue, Nov 05, 2013 at 10:43:15PM +0000, Michael McTernan wrote:
> Hi all,

Hi Mike,

> I think there's a problem on ARM with futex calls to FUTEX_WAIT and 
> similar for addresses that have been mapped to userspace from /dev/mem 
> or a device which sets VM_IO or VM_PFNMAP.  This can break 
> pthread_mutex_lock() if placed on such mapped memory and attributed as 
> process-shared.
> 
> The cause looks to be that ARM doesn't yet implement 
> get_user_pages_fast(), which is called in get_futex_key() for a 
> non-process private futex.

[...]

> I've seen a couple of patches go by that provide get_user_pages_fast() 
> on ARM, but none yet accepted.  I therefore would like to highlight this 
> particular case for context, and also to perhaps generate some movement 
> on this issue, which I also reported here:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=64321

The latest patches from Steve are here:

  http://lists.infradead.org/pipermail/linux-arm-kernel/2013-October/205951.html

but we need some feedback from the MM guys regarding the atomics in patch 2
(since we don't require IPIs for TLB invalidation). I'd also like to see
some numbers comparing the two schemes (since we could add a dummy IPI to
our huge TLB flushing code if it's cheaper).

Will

  reply	other threads:[~2013-11-06 10:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 22:43 mm: get_user_pages_fast() Michael McTernan
2013-11-06 10:19 ` Will Deacon [this message]
2013-11-06 10:54 ` Russell King - ARM Linux
2013-11-06 11:07   ` Will Deacon
2013-11-06 19:38   ` Michael McTernan
2013-11-06 19:57     ` Russell King - ARM Linux
2013-11-06 22:31       ` Michael McTernan

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=20131106101901.GA21074@mudshark.cambridge.arm.com \
    --to=will.deacon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox