bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: bimmy.pujari@intel.com, bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, mchehab@kernel.org, ast@kernel.org,
	kafai@fb.com, maze@google.com, ashkan.nikravesh@intel.com,
	dsahern@gmail.com, andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v3 1/2] bpf: Add bpf_ktime_get_real_ns
Date: Thu, 24 Sep 2020 17:31:02 +0200	[thread overview]
Message-ID: <d232b77c-da79-da1c-e564-e2a5cb64acb6@iogearbox.net> (raw)
In-Reply-To: <20200924022557.16561-1-bimmy.pujari@intel.com>

On 9/24/20 4:25 AM, bimmy.pujari@intel.com wrote:
> From: Bimmy Pujari <bimmy.pujari@intel.com>
> 
> The existing bpf helper functions to get timestamp return the time
> elapsed since system boot. This timestamp is not particularly useful
> where epoch timestamp is required or more than one server is involved
> and time sync is required. Instead, you want to use CLOCK_REALTIME,
> which provides epoch timestamp.
> Hence add bfp_ktime_get_real_ns() based around CLOCK_REALTIME.

nit:        ^ typo

> 
> Signed-off-by: Ashkan Nikravesh <ashkan.nikravesh@intel.com>
> Signed-off-by: Bimmy Pujari <bimmy.pujari@intel.com>
> ---
>   drivers/media/rc/bpf-lirc.c    |  2 ++
>   include/linux/bpf.h            |  1 +
>   include/uapi/linux/bpf.h       |  8 ++++++++
>   kernel/bpf/core.c              |  1 +
>   kernel/bpf/helpers.c           | 13 +++++++++++++
>   kernel/trace/bpf_trace.c       |  2 ++
>   tools/include/uapi/linux/bpf.h |  8 ++++++++
>   7 files changed, 35 insertions(+)
[...]
> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
> index fc5c901c7542..18c4fdce65c8 100644
> --- a/include/linux/bpf.h
> +++ b/include/linux/bpf.h
> @@ -1757,6 +1757,7 @@ extern const struct bpf_func_proto bpf_get_numa_node_id_proto;
>   extern const struct bpf_func_proto bpf_tail_call_proto;
>   extern const struct bpf_func_proto bpf_ktime_get_ns_proto;
>   extern const struct bpf_func_proto bpf_ktime_get_boot_ns_proto;
> +extern const struct bpf_func_proto bpf_ktime_get_real_ns_proto;
>   extern const struct bpf_func_proto bpf_get_current_pid_tgid_proto;
>   extern const struct bpf_func_proto bpf_get_current_uid_gid_proto;
>   extern const struct bpf_func_proto bpf_get_current_comm_proto;
> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> index a22812561064..198e69a6508d 100644
> --- a/include/uapi/linux/bpf.h
> +++ b/include/uapi/linux/bpf.h
> @@ -3586,6 +3586,13 @@ union bpf_attr {
>    * 		the data in *dst*. This is a wrapper of **copy_from_user**\ ().
>    * 	Return
>    * 		0 on success, or a negative error in case of failure.
> + *
> + * u64 bpf_ktime_get_real_ns(void)
> + *	Description
> + *		Return the real time in nanoseconds.
> + *		See: **clock_gettime**\ (**CLOCK_REALTIME**)

So from prior discussion with Andrii and David my impression was that the plan
was to at least properly document the clock and its limitations at minimum in
order to provide some basic guidance for users? Seems this was not yet addressed
here.

> + *	Return
> + *		Current *ktime*.
>    */
>   #define __BPF_FUNC_MAPPER(FN)		\
>   	FN(unspec),			\
> @@ -3737,6 +3744,7 @@ union bpf_attr {
>   	FN(inode_storage_delete),	\
>   	FN(d_path),			\
>   	FN(copy_from_user),		\
> +	FN(ktime_get_real_ns),		\
>   	/* */
>   
>   /* integer value in 'imm' field of BPF_CALL instruction selects which helper
> diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
> index c4811b139caa..0dbbda9b743b 100644
> --- a/kernel/bpf/core.c
> +++ b/kernel/bpf/core.c
> @@ -2208,6 +2208,7 @@ const struct bpf_func_proto bpf_get_smp_processor_id_proto __weak;
>   const struct bpf_func_proto bpf_get_numa_node_id_proto __weak;
>   const struct bpf_func_proto bpf_ktime_get_ns_proto __weak;
>   const struct bpf_func_proto bpf_ktime_get_boot_ns_proto __weak;
> +const struct bpf_func_proto bpf_ktime_get_real_ns_proto __weak;
>   
>   const struct bpf_func_proto bpf_get_current_pid_tgid_proto __weak;
>   const struct bpf_func_proto bpf_get_current_uid_gid_proto __weak;
> diff --git a/kernel/bpf/helpers.c b/kernel/bpf/helpers.c
> index 5cc7425ee476..300db9269996 100644
> --- a/kernel/bpf/helpers.c
> +++ b/kernel/bpf/helpers.c
> @@ -166,6 +166,17 @@ const struct bpf_func_proto bpf_ktime_get_boot_ns_proto = {
>   	.gpl_only	= false,
>   	.ret_type	= RET_INTEGER,
>   };
> +BPF_CALL_0(bpf_ktime_get_real_ns)
> +{

nit: newline before BPF_CALL_0(...)

> +	/* NMI safe access to clock realtime */
> +	return ktime_get_real_fast_ns();
> +}
> +
> +const struct bpf_func_proto bpf_ktime_get_real_ns_proto = {
> +	.func		= bpf_ktime_get_real_ns,
> +	.gpl_only	= false,
> +	.ret_type	= RET_INTEGER,
> +};
>   
>   BPF_CALL_0(bpf_get_current_pid_tgid)
>   {
[...]

      parent reply	other threads:[~2020-09-24 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  2:25 [PATCH bpf-next v3 1/2] bpf: Add bpf_ktime_get_real_ns bimmy.pujari
2020-09-24  2:25 ` [PATCH bpf-next v3 2/2] selftests/bpf: Verifying real time helper function bimmy.pujari
2020-09-24 15:34   ` Daniel Borkmann
2020-09-24 20:22   ` Andrii Nakryiko
2020-09-25  0:22     ` Pujari, Bimmy
2020-09-24  2:41 ` [PATCH bpf-next v3 1/2] bpf: Add bpf_ktime_get_real_ns Maciej Żenczykowski
2020-09-24 15:31 ` Daniel Borkmann [this message]

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=d232b77c-da79-da1c-e564-e2a5cb64acb6@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=andrii.nakryiko@gmail.com \
    --cc=ashkan.nikravesh@intel.com \
    --cc=ast@kernel.org \
    --cc=bimmy.pujari@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=dsahern@gmail.com \
    --cc=kafai@fb.com \
    --cc=maze@google.com \
    --cc=mchehab@kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).