All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@uga.edu>
To: sparclinux@vger.kernel.org
Subject: why "mov %0, %0" after "rd %%tick, %0"?
Date: Fri, 23 Jan 2004 20:59:13 +0000	[thread overview]
Message-ID: <871xpqtm8u.fsf@uga.edu> (raw)
In-Reply-To: <20040123125806.215b41da.davem@redhat.com>

Hi.  In arch/sparc64/kernel/time.c, there are some routines that use
the %tick register.  It seems analogous to the Pentium's TSC.  I'm
planning to use that register in userland via inline asm.  (Thanks for
making sure that non-privileged access is allowed, BTW!)

One thing I don't get is why there's a mov %0, %0 instruction after
reading the tick register.  Is this because of the delay slot?

static unsigned long tick_get_tick(void)
{
	unsigned long ret;

	__asm__ __volatile__("rd	%%tick, %0\n\t"
			     "mov	%0, %0"
			     : "=r" (ret));

	return ret & ~TICK_PRIV_BIT;
}


-- 
--Ed L Cashin            |   PGP public key:
  ecashin@uga.edu        |   http://noserose.net/e/pgp/


  reply	other threads:[~2004-01-23 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 20:58 why "mov %0, %0" after "rd %%tick, %0"? David S. Miller
2004-01-23 20:59 ` Ed L Cashin [this message]
2004-01-23 21:31 ` Ed L Cashin

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=871xpqtm8u.fsf@uga.edu \
    --to=ecashin@uga.edu \
    --cc=sparclinux@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.