From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
frankja@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 2/4] lib: s390x: add CPU timer functions to time.h
Date: Tue, 5 Jul 2022 10:20:11 +0200 [thread overview]
Message-ID: <20220705102011.1cf2237e@p-imbrenda> (raw)
In-Reply-To: <20220704121328.721841-3-nrb@linux.ibm.com>
On Mon, 4 Jul 2022 14:13:26 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:
> Upcoming changes will make use of the CPU timer, so add a convenience
> function to set the CPU timer.
>
> Since shifts for both CPU timer and TOD clock are the same, introduce a
> new define TIMING_S390_SHIFT_US. The respective shifts for CPU timer and
> TOD clock reference it, so the semantic difference between the two
> defines is kept.
>
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> ---
> lib/s390x/asm/time.h | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/lib/s390x/asm/time.h b/lib/s390x/asm/time.h
> index 7652a151e87a..9ae364afb8a3 100644
> --- a/lib/s390x/asm/time.h
> +++ b/lib/s390x/asm/time.h
> @@ -11,9 +11,13 @@
> #ifndef _ASMS390X_TIME_H_
> #define _ASMS390X_TIME_H_
>
> -#define STCK_SHIFT_US (63 - 51)
> +#define TIMING_S390_SHIFT_US (63 - 51)
I would call it S390_CLOCK_SHIFT_US
> +
> +#define STCK_SHIFT_US TIMING_S390_SHIFT_US
> #define STCK_MAX ((1UL << 52) - 1)
>
> +#define CPU_TIMER_SHIFT_US TIMING_S390_SHIFT_US
> +
> static inline uint64_t get_clock_us(void)
> {
> uint64_t clk;
> @@ -45,4 +49,14 @@ static inline void mdelay(unsigned long ms)
> udelay(ms * 1000);
> }
>
> +static inline void cpu_timer_set(int64_t timeout_ms)
I would call the function cpu_timer_set_ms
so that it's clear what unit goes in, and it makes things easier if in
the future someone needs a _us version
> +{
> + int64_t timer_value = (timeout_ms * 1000) << CPU_TIMER_SHIFT_US;
> + asm volatile (
> + "spt %[timer_value]\n"
> + :
> + : [timer_value] "Q" (timer_value)
> + );
> +}
> +
> #endif
next prev parent reply other threads:[~2022-07-05 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 12:13 [kvm-unit-tests PATCH v2 0/4] Add panic test support Nico Boehr
2022-07-04 12:13 ` [kvm-unit-tests PATCH v2 1/4] runtime: add support for panic tests Nico Boehr
2022-07-04 12:13 ` [kvm-unit-tests PATCH v2 2/4] lib: s390x: add CPU timer functions to time.h Nico Boehr
2022-07-05 8:20 ` Claudio Imbrenda [this message]
2022-07-19 6:35 ` Nico Boehr
2022-07-04 12:13 ` [kvm-unit-tests PATCH v2 3/4] s390x: add extint loop test Nico Boehr
2022-07-04 12:13 ` [kvm-unit-tests PATCH v2 4/4] s390x: add pgm spec interrupt " Nico Boehr
2022-07-11 12:54 ` Thomas Huth
2022-07-18 14:07 ` Nico Boehr
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=20220705102011.1cf2237e@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=thuth@redhat.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.