From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v2.6.19-rt6, yum/rpm
Date: Thu, 01 Feb 2007 18:52:38 +0300 [thread overview]
Message-ID: <45C20CC6.2070201@ru.mvista.com> (raw)
In-Reply-To: <20061215161952.GA29191@elte.hu>
Hello.
Ingo Molnar wrote:
>>>as usual, bugreports, fixes and suggestions are welcome,
>> Be aware that even with the newest -rt patch, the PowerPC TOD
>>vsyscalls are still broken, i.e. glibc may return imprecise/incorrect
>>results for the related calls -- despite arch/powerpc/kernel/time.c
>>has been at last fixed to at least compile, the PowerPC clocksource
>>patch removed the important part of TOD vsyscall support, and this
>>hasn't been dealt with. I've sent to Thomas Gleixner a patch removing
>>the affected vsyscalls altogether for the time being in the early
>>November (unfortunately, I came to know of the breakage too late, and
>>hadn't time to deal with it propery due to othr woes), however, I'm
>>not seeing any of my patches (I've also done PowerPC clockevents
>>support) merged to -rt (or otherwise published). Most of the patches
>>can be found in the linuxppc-dev list archives, for the interested...
> could you resend them to me please?
Seeing that GENERIC_TIME has been thrown out from the -rt patch, it makes
no sense now (even if I had time -- I also decided to leave this to Thomas as
the HRT maintainer). Concerning this change: tghe patch that comments out
recalc_time_offset() call in arch/powerpc/kernel/time.c must have be thrown
out as well since it's breaking TOD vsyscall support now.
> Ingo
WBR, Sergei
next prev parent reply other threads:[~2007-02-01 15:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 17:11 v2.6.19-rt6, yum/rpm Ingo Molnar
2006-12-07 11:33 ` K.R. Foley
2006-12-07 12:13 ` Ingo Molnar
2006-12-07 15:54 ` K.R. Foley
2006-12-07 16:57 ` Ingo Molnar
2006-12-07 19:40 ` K.R. Foley
2006-12-07 20:04 ` Ingo Molnar
2006-12-07 20:45 ` Fernando Lopez-Lezcano
2006-12-07 20:58 ` Ingo Molnar
2006-12-07 21:07 ` Fernando Lopez-Lezcano
2006-12-07 21:42 ` Fernando Lopez-Lezcano
2006-12-07 21:20 ` Arjan van de Ven
2006-12-07 21:44 ` Ingo Molnar
2006-12-15 16:18 ` Sergei Shtylyov
2006-12-15 16:19 ` Ingo Molnar
2007-02-01 15:52 ` Sergei Shtylyov [this message]
2007-02-01 17:38 ` Ingo Molnar
2007-02-01 17:49 ` Ingo Molnar
2007-02-01 18:01 ` Sergei Shtylyov
2007-03-07 14:55 ` Sergei Shtylyov
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=45C20CC6.2070201@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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