From: George Anzinger <george@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH] to fix xtime lock for in the RT kernel patch
Date: Fri, 21 Jan 2005 01:08:22 -0800 [thread overview]
Message-ID: <41F0C686.5070903@mvista.com> (raw)
In-Reply-To: <20050121090014.GA30379@elte.hu>
Ingo Molnar wrote:
> * George Anzinger <george@mvista.com> wrote:
>
>
>>What I am suggesting is spliting the mark code so that it would only
>>grap the offset (current TSC in most systems) during interrupt
>>processing. Applying this would be done later in the thread. Since
>>it is not applying the offset, the xtime_lock would not need to be
>>taken.
>
>
> ok, you are right, and this would be fine with me. Wanna take a shot at
> it? I've uploaded the -03 patch which is my most current tree. (with the
> do_timer() moving done already.) I've reviewed the TSC offset codepath
> again and i'm not sure where i got the 10 usecs from ... it's a pretty
> cheap codepath that can be done in the direct interrupt just fine.
>
Tomorrow, uh, later today. Need some sleep now...
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-01-21 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:57 [PATCH] to fix xtime lock for in the RT kernel patch George Anzinger
2005-01-21 6:35 ` Ingo Molnar
2005-01-21 8:16 ` George Anzinger
2005-01-21 8:21 ` Ingo Molnar
2005-01-21 8:39 ` George Anzinger
2005-01-21 8:45 ` Ingo Molnar
2005-01-21 8:54 ` George Anzinger
2005-01-21 9:00 ` Ingo Molnar
2005-01-21 9:08 ` George Anzinger [this message]
2005-01-27 20:53 ` George Anzinger
2005-01-28 4:35 ` Ingo Molnar
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=41F0C686.5070903@mvista.com \
--to=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.