From: Domen Puncer <domen.puncer@telargo.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Tickless Hz/hrtimers/etc. on PowerPC
Date: Fri, 13 Jul 2007 10:49:37 +0200 [thread overview]
Message-ID: <20070713084936.GC11476@nd47.coderock.org> (raw)
In-Reply-To: <4696369A.2010200@ru.mvista.com>
On 12/07/07 18:11 +0400, Sergei Shtylyov wrote:
> Hello.
>
> Domen Puncer wrote:
>
> >>Does anyone have the definitive patchset to enable the tickless hz,
> >>some kind of hrtimer and the other related improvements in the
> >>PowerPC tree?
>
> >I use attached patches for tickless.
> >Order in which they're applied:
>
> >PowerPC_GENERIC_CLOCKEVENTS.patch
>
> That's my patch which used to have both description and signoff that I'm
> not seeing in the attached version...
Err, yes, sorry, I don't remember anymore where I picked them,
but I'm pretty sure I didn't go delete description and signoff
by hand.
>
> >PowerPC_GENERIC_TIME.linux-2.6.18-rc6_timeofday-arch-ppc_C6.patch
>
> This one should come first of all, I'd say...
> Note that it breaks TOD vsyscalls, so you need my patch that removes
> support for those for the time being (i.e. until Tony hopefully fixes this
> :-). Also, there was a patch implementing read_persistent_clock() and
> getting rid of the code setting xtime in time_init(). Attaching them
> both...
>
> >PowerPC_enable_HRT_and_dynticks_support.patch
>
> Again looks like my patch with description/signoff missing for whatever
> reason...
>
> >PowerPC_no_hz_fix.patch
>
> This has nothing to do with CONFIG_NO_HZ per se -- it fixes the
> compilation error introduced by John's patch.
>
> >tickless-enable.patch
>
> That one doesn't look quite right...
That's because I made it ;-)
It did the trick of enabling tickless though.
Domen
prev parent reply other threads:[~2007-07-13 8:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 18:06 Tickless Hz/hrtimers/etc. on PowerPC Matt Sealey
2007-07-11 18:17 ` Sergei Shtylyov
2007-07-11 18:33 ` Michael Neuling
2007-07-11 22:15 ` Matt Sealey
2007-07-12 6:41 ` Tony Breeds
2007-07-12 12:07 ` Matt Sealey
2007-07-16 0:45 ` Tony Breeds
2007-07-12 15:49 ` Michael Neuling
2007-07-12 20:04 ` Matt Sealey
2007-07-12 20:12 ` Geert Uytterhoeven
2007-07-13 8:34 ` Benjamin Herrenschmidt
2007-07-12 16:32 ` Sergei Shtylyov
2007-07-12 20:08 ` Matt Sealey
2007-07-12 6:51 ` Domen Puncer
2007-07-12 12:07 ` Matt Sealey
2007-07-13 8:41 ` Domen Puncer
2007-07-12 14:11 ` Sergei Shtylyov
2007-07-12 16:41 ` Sergei Shtylyov
2007-07-13 8:49 ` Domen Puncer [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=20070713084936.GC11476@nd47.coderock.org \
--to=domen.puncer@telargo.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sshtylyov@ru.mvista.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.