From: Jens Axboe <axboe@kernel.dk>
To: "Dan Horák" <dan@danny.cz>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] implement get_cpu_clock() for s390/s390x
Date: Tue, 01 Jan 2013 10:57:08 +0100 [thread overview]
Message-ID: <50E2B2F4.2010508@kernel.dk> (raw)
In-Reply-To: <1356905016-48651-1-git-send-email-dan@danny.cz>
On 2012-12-30 23:03, Dan Hor�k wrote:
> ---
> arch/arch-s390.h | 18 ++++++++++++++++++
> 1 files changed, 18 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arch-s390.h b/arch/arch-s390.h
> index fe51791..bcd9163 100644
> --- a/arch/arch-s390.h
> +++ b/arch/arch-s390.h
> @@ -22,4 +22,22 @@
> #define read_barrier() asm volatile("bcr 15,0" : : : "memory")
> #define write_barrier() asm volatile("bcr 15,0" : : : "memory")
>
> +static inline unsigned long long get_cpu_clock(void)
> +{
> + unsigned long long clk;
> +
> + __asm__ __volatile__("stck %0" : "=Q" (clk) : : "cc");
> + return clk;
> +}
> +
> +#define ARCH_HAVE_INIT
> +extern int tsc_reliable;
> +static inline int arch_init(char *envp[])
> +{
> + tsc_reliable = 1;
> + return 0;
> +}
> +
> +#define ARCH_HAVE_CPU_CLOCK
> +
> #endif
Thanks, Dan! Applied.
--
Jens Axboe
prev parent reply other threads:[~2013-01-01 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 22:03 [PATCH] implement get_cpu_clock() for s390/s390x Dan Horák
2013-01-01 9:57 ` Jens Axboe [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=50E2B2F4.2010508@kernel.dk \
--to=axboe@kernel.dk \
--cc=dan@danny.cz \
--cc=fio@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