All of lore.kernel.org
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
To: linux-arm-kernel@lists.infradead.org
Subject: arm32: Missing __get_user for u64 user type
Date: Fri, 6 Jul 2018 13:30:04 -0400 (EDT)	[thread overview]
Message-ID: <208280844.1302.1530898204811.JavaMail.zimbra@efficios.com> (raw)

Hi,

The restartable sequence code needs a __get_user for u64 types.
arm32. Although a get_user() is implemented, the architecture
lacks support for 8 bytes __get_user().

Do you guys recommend extending __get_user_err() to do two
__get_user_asm_word() to read it through a temporary union,
or do you have other approaches in mind ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Will Deacon <will.deacon@arm.com>,
	Russell King <linux@arm.linux.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: arm32: Missing __get_user for u64 user type
Date: Fri, 6 Jul 2018 13:30:04 -0400 (EDT)	[thread overview]
Message-ID: <208280844.1302.1530898204811.JavaMail.zimbra@efficios.com> (raw)

Hi,

The restartable sequence code needs a __get_user for u64 types.
arm32. Although a get_user() is implemented, the architecture
lacks support for 8 bytes __get_user().

Do you guys recommend extending __get_user_err() to do two
__get_user_asm_word() to read it through a temporary union,
or do you have other approaches in mind ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

             reply	other threads:[~2018-07-06 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 17:30 Mathieu Desnoyers [this message]
2018-07-06 17:30 ` arm32: Missing __get_user for u64 user type Mathieu Desnoyers

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=208280844.1302.1530898204811.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.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.