From: Oleg Drokin <green@linuxhacker.ru>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: 2.6.0 uptime bug
Date: Fri, 12 Sep 2003 23:32:39 +0400 [thread overview]
Message-ID: <200309121932.h8CJWdUs003131@car.linuxhacker.ru> (raw)
In-Reply-To: 20030911180344.A96963BCE4@home.petschge.de
Hello!
Patrick Kilian <petschge@gmx.de> wrote:
>>> I have a patch which gives the correct uptime. I don't know what the
>>> patch breaks so please post any problems you have.
>> Have you been able to figure out whether this is also a problem for
>> other ports? Your patch suggests that it is, and if it is, then you
>> should send it to LKML so it can be fixed in mainline.
PK> Ok 2.6.0-test5 gives the correct uptime on i386 and the wrong huge uptime as uml. My patch doesn't break anything on i386 but I'm going to fix this bug in the uml part of the kernel.
Well, but we have HZ=1000 on i386 and HZ=100 in UML
that's different code paths in kernel.
Bye,
Oleg
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-09-12 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 17:44 [uml-devel] Re: 2.6.0 uptime bug Patrick Kilian
2003-09-12 18:09 ` Jeff Dike
2003-09-12 19:32 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 13:30 Patrick Kilian
2003-09-14 16:06 ` Jeff Dike
2003-09-04 15:06 [uml-devel] " Patrick Kilian
[not found] ` <20030905151952.6EBFC3BCE4@home.petschge.de>
[not found] ` <20030906190708.56B8C3BCE4@home.petschge.de>
2003-09-09 16:16 ` [uml-devel] " Jeff Dike
2003-09-09 16:28 ` Patrick "Petschge" Kilian
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=200309121932.h8CJWdUs003131@car.linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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