From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 10/10] arm+arm64: vdso: Add support for CLOCK_BOOTTIME
Date: Mon, 30 Oct 2017 15:25:18 +0000 [thread overview]
Message-ID: <20171030152517.GB1705@arm.com> (raw)
In-Reply-To: <20171012230154.87782-1-salyzyn@android.com>
Hi Mark,
On Thu, Oct 12, 2017 at 04:01:45PM -0700, Mark Salyzyn wrote:
> Add a case for CLOCK_BOOTTIME as it is popular for measuring
> relative time on systems expected to suspend() or hibernate().
>
> Signed-off-by: Mark Salyzyn <salyzyn@android.com>
>
> v2: rebased and changed from 3/3 to 10/10, fortified commit message.
> ---
> arch/arm/include/asm/vdso_datapage.h | 1 +
> arch/arm/kernel/vdso.c | 1 +
> arch/arm/vdso/vgettimeofday.c | 56 ++++++++++++++++++++++++++++++++++
> arch/arm64/include/asm/vdso_datapage.h | 1 +
> arch/arm64/kernel/vdso.c | 1 +
> 5 files changed, 60 insertions(+)
Can you elaborate a bit on the use-case for CLOCK_BOOTTIME, please, so
that we can justify accelerating it in the vDSO?
Thanks,
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Mark Salyzyn <salyzyn@android.com>
Cc: linux-kernel@vger.kernel.org, james.morse@arm.com,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Salyzyn <salyzyn@google.com>,
Andy Lutomirski <luto@amacapital.net>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
John Stultz <john.stultz@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Laura Abbott <labbott@redhat.com>,
Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 10/10] arm+arm64: vdso: Add support for CLOCK_BOOTTIME
Date: Mon, 30 Oct 2017 15:25:18 +0000 [thread overview]
Message-ID: <20171030152517.GB1705@arm.com> (raw)
In-Reply-To: <20171012230154.87782-1-salyzyn@android.com>
Hi Mark,
On Thu, Oct 12, 2017 at 04:01:45PM -0700, Mark Salyzyn wrote:
> Add a case for CLOCK_BOOTTIME as it is popular for measuring
> relative time on systems expected to suspend() or hibernate().
>
> Signed-off-by: Mark Salyzyn <salyzyn@android.com>
>
> v2: rebased and changed from 3/3 to 10/10, fortified commit message.
> ---
> arch/arm/include/asm/vdso_datapage.h | 1 +
> arch/arm/kernel/vdso.c | 1 +
> arch/arm/vdso/vgettimeofday.c | 56 ++++++++++++++++++++++++++++++++++
> arch/arm64/include/asm/vdso_datapage.h | 1 +
> arch/arm64/kernel/vdso.c | 1 +
> 5 files changed, 60 insertions(+)
Can you elaborate a bit on the use-case for CLOCK_BOOTTIME, please, so
that we can justify accelerating it in the vDSO?
Thanks,
Will
next prev parent reply other threads:[~2017-10-30 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 23:01 [PATCH v2 10/10] arm+arm64: vdso: Add support for CLOCK_BOOTTIME Mark Salyzyn
2017-10-12 23:01 ` Mark Salyzyn
2017-10-30 15:25 ` Will Deacon [this message]
2017-10-30 15:25 ` Will Deacon
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=20171030152517.GB1705@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 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.