From: Con Kolivas <kernel@kolivas.org>
To: Tony Lindgren <tony@atomide.com>
Cc: tony@muru.com, linux-kernel@vger.kernel.org
Subject: Re: dynamic ticks for 2.6.13-rc4 & bad gzip
Date: Tue, 2 Aug 2005 17:21:21 +1000 [thread overview]
Message-ID: <200508021721.21232.kernel@kolivas.org> (raw)
In-Reply-To: <20050802071035.GF15903@atomide.com>
On Tue, 2 Aug 2005 05:10 pm, Tony Lindgren wrote:
> * Con Kolivas <kernel@kolivas.org> [050801 18:24]:
> > Hi Tony, LKML
> >
> > Since there appears to be renewed interest of late in dynamic ticks...
> >
> > You didn't respond with my last patch for dynamic ticks so I assume
> > that's because you threw up when you saw what a mess it is. Anyway I'm
> > sorry for sending you that naive mess the first time around.
>
> Hehe, my strategy of lame response and sloppy patches seems to be working
> then! :)
Yes you must have learnt from akpm :P He's a master of that game. Thanks for
replying :)
> > Here is a full patch for 2.6.13-rc4 pushing code out of common paths and
> > into dyn-tick.h where possible that builds on any config I can throw on
> > it so far. I'm having trouble with "bad gzip magic" on boot with this one
> > so I'm not really sure what's going on. Perhaps someone on the mailing
> > list can shed some light on it.
>
> Thanks a lot, I really appreciate help on getting this thing cleaned up for
> x86 + PPC. The ARM version is already merged to mainline, but that's did
> not have all the legacy issues, and ARM has nice sys_timer...
You're welcome, but I'm no coding expert and just applying a few styling
issues as I see them.
> I'll try out your patch today at some point, and will post a merged patches
> that also integrate the PPC support.
> I don't understand the "bad gzip magic", that happens while uncompressing
> before kernel boots, right?
Yeah, bzImage has some convoluted way of storing the gunzip code in the header
and then it decompresses the image. This error implies something went
horribly wrong but I have seen it before occasionally with gcc 4.0.1 - it
usually goes away with reconfigure/rebuilding but this one didn't. Probably
not important for this code per se.
Cheers,
Con
next prev parent reply other threads:[~2005-08-02 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 1:24 dynamic ticks for 2.6.13-rc4 & bad gzip Con Kolivas
2005-08-02 7:10 ` Tony Lindgren
2005-08-02 7:21 ` Con Kolivas [this message]
2005-08-02 8:26 ` PF_KEY & 26Sec Documentation Eshwar
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=200508021721.21232.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=tony@muru.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox