All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Salyzyn <salyzyn@android.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Android Kernel Team <kernel-team@android.com>,
	Chiawei Wang <chiaweiwang@google.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Enrico Weigelt <info@metux.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alexios Zavras <alexios.zavras@intel.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Allison Randal <allison@lohutok.net>
Subject: Re: [PATCH v2]: arch: arm64: vdso: export the symbols for time()
Date: Tue, 23 Jun 2020 17:57:24 +0100	[thread overview]
Message-ID: <20200623165723.GB4819@willie-the-truck> (raw)
In-Reply-To: <CAJ-C09j3ZZOZDPLiS+8-9Ypd1hYtfJY5LUym8z79xAUKS11VUA@mail.gmail.com>

On Tue, Jun 23, 2020 at 09:47:57AM -0700, Mark Salyzyn wrote:
>    time() in bionic libc will go an use vDSO interface to pick up this
>    low-resolution timer.

But my point is it should _already_ be using the vDSO implementation of
clock_gettime(), which should be plenty fast enough.

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Mark Salyzyn <salyzyn@android.com>
Cc: Enrico Weigelt <info@metux.net>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Allison Randal <allison@lohutok.net>,
	LKML <linux-kernel@vger.kernel.org>,
	Alexios Zavras <alexios.zavras@intel.com>,
	Chiawei Wang <chiaweiwang@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Android Kernel Team <kernel-team@android.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2]: arch: arm64: vdso: export the symbols for time()
Date: Tue, 23 Jun 2020 17:57:24 +0100	[thread overview]
Message-ID: <20200623165723.GB4819@willie-the-truck> (raw)
In-Reply-To: <CAJ-C09j3ZZOZDPLiS+8-9Ypd1hYtfJY5LUym8z79xAUKS11VUA@mail.gmail.com>

On Tue, Jun 23, 2020 at 09:47:57AM -0700, Mark Salyzyn wrote:
>    time() in bionic libc will go an use vDSO interface to pick up this
>    low-resolution timer.

But my point is it should _already_ be using the vDSO implementation of
clock_gettime(), which should be plenty fast enough.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-06-23 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 14:38 [PATCH v2]: arch: arm64: vdso: export the symbols for time() Mark Salyzyn
2020-06-15 14:38 ` Mark Salyzyn
2020-06-23 14:44 ` Will Deacon
2020-06-23 14:44   ` Will Deacon
     [not found]   ` <CAJ-C09j3ZZOZDPLiS+8-9Ypd1hYtfJY5LUym8z79xAUKS11VUA@mail.gmail.com>
2020-06-23 16:57     ` Will Deacon [this message]
2020-06-23 16:57       ` 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=20200623165723.GB4819@willie-the-truck \
    --to=will@kernel.org \
    --cc=alexios.zavras@intel.com \
    --cc=allison@lohutok.net \
    --cc=catalin.marinas@arm.com \
    --cc=chiaweiwang@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=info@metux.net \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=salyzyn@android.com \
    --cc=tglx@linutronix.de \
    --cc=vincenzo.frascino@arm.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.