From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM64:VDSO: Improve gettimeofday, don't use udiv
Date: Thu, 10 Mar 2016 17:00:33 +0000 [thread overview]
Message-ID: <20160310170032.GA11413@svinekod> (raw)
In-Reply-To: <CAKv+Gu90LOYRKWR8svKhqn6T9qQ-A=VB7iP7wM6oz=MyCs7CJA@mail.gmail.com>
On Mon, Mar 14, 2016 at 07:55:38AM +0100, Ard Biesheuvel wrote:
> On 13 March 2016 at 20:50, Andrew Pinski <apinski@cavium.com> wrote:
> > + movk x13, 0xe353, lsl 16
> > + lsr x11, x11, 3
> > + movk x13, 0x9ba5, lsl 32
> > + movk x13, 0x20c4, lsl 48
> > + /* x13 = 0x20c49ba5e353f7cf */
>
> Could we clean this up a bit? Something along the lines of
>
> .set m, 0x20c49ba5e353f7cf
> movz x13,#:abs_g3:m
> movk x13, #:abs:g2_nc:m
> movk x13, #:abs_g1_nc:m
> movk x13, #:abs_g0_nc:m
>
> Actually, the movz/movk sequence should probably be implemented as a
> macro in asm/assembler.h, with parameters for the register and the
> symbol name.
Agreed.
> I think Mark proposed such a patch at some point
That would be [1], which needs the relocations fixed up [2,3] to match the
above.
I didn't respin that as it turned out to be unnecessary at the time, but I'm
more than happy for someone to pick it up.
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397563.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397572.html
[3] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397573.html
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Andrew Pinski <apinski@cavium.com>,
pinskia@gmail.com,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM64:VDSO: Improve gettimeofday, don't use udiv
Date: Thu, 10 Mar 2016 17:00:33 +0000 [thread overview]
Message-ID: <20160310170032.GA11413@svinekod> (raw)
In-Reply-To: <CAKv+Gu90LOYRKWR8svKhqn6T9qQ-A=VB7iP7wM6oz=MyCs7CJA@mail.gmail.com>
On Mon, Mar 14, 2016 at 07:55:38AM +0100, Ard Biesheuvel wrote:
> On 13 March 2016 at 20:50, Andrew Pinski <apinski@cavium.com> wrote:
> > + movk x13, 0xe353, lsl 16
> > + lsr x11, x11, 3
> > + movk x13, 0x9ba5, lsl 32
> > + movk x13, 0x20c4, lsl 48
> > + /* x13 = 0x20c49ba5e353f7cf */
>
> Could we clean this up a bit? Something along the lines of
>
> .set m, 0x20c49ba5e353f7cf
> movz x13,#:abs_g3:m
> movk x13, #:abs:g2_nc:m
> movk x13, #:abs_g1_nc:m
> movk x13, #:abs_g0_nc:m
>
> Actually, the movz/movk sequence should probably be implemented as a
> macro in asm/assembler.h, with parameters for the register and the
> symbol name.
Agreed.
> I think Mark proposed such a patch at some point
That would be [1], which needs the relocations fixed up [2,3] to match the
above.
I didn't respin that as it turned out to be unnecessary at the time, but I'm
more than happy for someone to pick it up.
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397563.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397572.html
[3] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397573.html
next prev parent reply other threads:[~2016-03-10 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 19:50 [PATCH 0/2] *** SUBJECT HERE *** Andrew Pinski
2016-03-13 19:50 ` Andrew Pinski
2016-03-13 19:50 ` [PATCH 1/2] ARM64:VDSO: Improve gettimeofday, don't use udiv Andrew Pinski
2016-03-13 19:50 ` Andrew Pinski
2016-03-14 6:55 ` Ard Biesheuvel
2016-03-14 6:55 ` Ard Biesheuvel
2016-03-10 17:00 ` Mark Rutland [this message]
2016-03-10 17:00 ` Mark Rutland
2016-03-24 14:36 ` Christopher Covington
2016-03-24 14:36 ` Christopher Covington
2016-03-13 19:50 ` [PATCH 2/2] ARM64:VDSO: Improve __do_get_tspec, " Andrew Pinski
2016-03-13 19:50 ` Andrew Pinski
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=20160310170032.GA11413@svinekod \
--to=mark.rutland@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.