All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH_TAKE_2] now < last_tick problem
Date: Tue, 14 Oct 2003 16:58:14 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106615107610622@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106575925709435@msgid-missing>

>>>>> On Tue, 14 Oct 2003 15:53:15 +1000, Ian Wienand <ianw@gelato.unsw.edu.au> said:

  Ian> On Mon, Oct 13, 2003 at 10:23:39PM -0700, David Mosberger
  Ian> wrote:
  >> consistency-check.  May want to add a comment about that, though.

  Ian> A few messages up I added something like

  Ian> + * Return the number of nano-seconds that elapsed since the
  Ian> last + * update to jiffy.  It is quite possible that the timer
  Ian> interrupt + * will interrupt this and result in a race for any
  Ian> of jiffies, + * wall_jiffies or itm_next.  Thus, the xtime_lock
  Ian> must be at least + * read-locked when calling this routine.

  Ian> although read-locked should probably be 'read synchronised' or
  Ian> something to avoid confusion.

Sounds fine to me.  Do you want to send me a complete patch so you'll
get the proper credit?

Thanks,

	--david

  parent reply	other threads:[~2003-10-14 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10  4:13 [PATCH_TAKE_2] now < last_tick problem Ian Wienand
2003-10-10 16:42 ` David Mosberger
2003-10-13  2:11 ` Ian Wienand
2003-10-13 18:17 ` David Mosberger
2003-10-13 23:06 ` Ian Wienand
2003-10-14  5:23 ` David Mosberger
2003-10-14  5:53 ` Ian Wienand
2003-10-14 16:58 ` David Mosberger [this message]
2003-10-14 23:05 ` Ian Wienand

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=marc-linux-ia64-106615107610622@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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.