All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elad Lahav <e2lahav@gmail.com>
To: perfbook@vger.kernel.org
Subject: Re: [PATCH v2] CodeSamples: Support for building on different operating systems
Date: Mon, 15 Aug 2022 06:42:22 -0400	[thread overview]
Message-ID: <07ed4c84-976a-cb4a-072f-47a7599cc434@gmail.com> (raw)
In-Reply-To: <20220815103717.7454-1-e2lahav@gmail.com>

On 2022-08-15 06:37, Elad Lahav wrote:
> +	cat api-pthreads/api-$(os_compat).h >> api.h

I didn't want to go overboard here, so it's just the minimum required 
for having a single per-OS header with specific definitions.


> +#ifndef CLOCK_MONOTONIC_RAW
> +#define CLOCK_MONOTONIC_RAW CLOCK_MONOTONIC
> +#endif

This one wasn't moved to the per-OS header because of the order in which 
headers are included, which I didn't want to fiddle with.
That said, would you be open to changing the ARM64 get_timestamp() to a 
simple read of the hardware clock? It is architecturally-defined.

--Elad

  reply	other threads:[~2022-08-15 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 10:37 [PATCH v2] CodeSamples: Support for building on different operating systems Elad Lahav
2022-08-15 10:42 ` Elad Lahav [this message]
2022-08-15 16:54   ` Paul E. McKenney

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=07ed4c84-976a-cb4a-072f-47a7599cc434@gmail.com \
    --to=e2lahav@gmail.com \
    --cc=perfbook@vger.kernel.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.