Michal Piotrowski wrote:
> Hi all,
>
> Here is a list of some known regressions in 2.6.23-rc6.
...
Missing from the list:
USB "autosuspend" feature (new in 2.6.23) breaks *lots* of devices.
Many have since been blacklisted in one-at-a-time discovery patches,
but that's really just the tip of the
Dear Jeff,
Jeff Dike wrote:
> On Wed, Sep 12, 2007 at 11:52:32PM +0200, Fermín Galán Márquez wrote:
>> This is the trace (as you can see I're repeated the experiment twice,
>> the result is basically the same), hoping it could be useful to diagnose
>> the problem and fix eventual bugs in the UML
There are various uses of powers of 1000, plus the odd BILLION
constant in the time code. However, there are perfectly good definitions of
*SEC_PER_*SEC in linux/time.h which can be used instaed.
These are replaced directly in kernel code. Userspace code imports
those constants as UM_*SEC_PER_*S
Move timer signal initialization from init_irq_signals to a new
function, timer_init.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/include/os.h |1 +
arch/um/kernel/time.c |2 ++
arch/um/os-Linux/irq.c|4
arch/um/os-Linux/signal.c | 10 ++
4 file
Enable tickless support.
CONFIG_TICK_ONESHOT and CONFIG_NO_HZ are enabled.
itimer_clockevent gets CLOCK_EVT_FEAT_ONESHOT and an implementation of
.set_next_event.
CONFIG_UML_REAL_TIME_CLOCK goes away because it only makes sense when
there is a clock ticking away all the time. timer_handler now
Now that ITIMER_REAL is no longer used, there is no need for any use
of SIGALRM whatsoever. This patch removes all mention of it.
In addition, real_alarm_handler took a signal argument which is now
always SIGVTALRM. So, that is gone.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/os-L
Now, the idle loop now longer needs SIGALRM firing - it can just sleep
for the requisite amount of time and fake a timer interrupt when it
finishes.
Any use of ITIMER_REAL now goes away. disable_timer only turns off
ITIMER_VIRTUAL. switch_timers is no longer needed, so it, and all
calls, goes aw
Enable CONFIG_GENERIC_CLOCKEVENTS.
timer_irq gets its name changed to timer_handler, and becomes the
recipient of timer signals.
The clock_event_device is set up to imitate the current ticking clock,
i.e. CLOCK_EVT_FEAT_ONESHOT is not enabled yet.
disable_timer now doesn't ignore SIGALRM and SIG
Add clocksource support.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/kernel/time.c | 21 +
1 file changed, 21 insertions(+)
Index: linux-2.6.22/arch/um/kernel/time.c
===
--- linux-2.6.22.orig/arch/u
Eliminate hz() since its only purpose was to provide a kernel-space
constant to userspace code. This can be done instead by providing the
constant directly through kernel_constants.h.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/include/common-offsets.h |2 ++
arch/um/include/kern
Enable CONFIG_GENERIC_TIME.
As a side-effect of this, the UML implementations of do_gettimeofday
and do_settimeofday go away, as these are provided by generic code.
set_time also goes away since it was only used by do_settimeofday.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/Kconfig
set_interval took a timer type as an argument, but it always specified
a virtual timer. So, it is not needed, and it is gone, and
set_interval is simplified appropriately.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/include/os.h|2 +-
arch/um/kernel/time.c |
Fix up the switching between virtual and real timers. The idle loop
sleeps, the timer at that point must be real time. At all other
times, the timer must be virtual. Even when userspace is running, and
the kernel is asleep, the virtual timer is correct because the process
timer will be running.
This patchset modernizes UML's timekeeping system. There are a number
of cleanups, but the major items are clockevent and clocksource
support, followed by tickless support.
This is obviously 2.6.24 material.
Jeff
--
Work email - jdike at linux dot intel dot com
On Wed, Sep 12, 2007 at 11:52:32PM +0200, Fermín Galán Márquez wrote:
> This is the trace (as you can see I're repeated the experiment twice,
> the result is basically the same), hoping it could be useful to diagnose
> the problem and fix eventual bugs in the UML kernel. See below regarding
> th
Thomas Gleixner pisze:
> On Wed, 2007-09-12 at 18:58 +0200, Michal Piotrowski wrote:
>> Subject : x86_64 vdso patch is broken somehow?
>> References : http://lkml.org/lkml/2007/8/29/136
>> Last known good : ?
>> Submitter : Chuck Ebbert <[EMAIL PROTECTED]>
>> Caused-By : A
On Wed, 2007-09-12 at 18:58 +0200, Michal Piotrowski wrote:
> Subject : x86_64 vdso patch is broken somehow?
> References : http://lkml.org/lkml/2007/8/29/136
> Last known good : ?
> Submitter : Chuck Ebbert <[EMAIL PROTECTED]>
> Caused-By : Andi Kleen <[EMAIL PROTECTED]>
On Wed, 12 Sep 2007, Michal Piotrowski wrote:
>
> Subject : x86_64 vdso patch is broken somehow?
> References : http://lkml.org/lkml/2007/8/29/136
> Last known good : ?
> Submitter : Chuck Ebbert <[EMAIL PROTECTED]>
> Caused-By : Andi Kleen <[EMAIL PROTECTED]>
>
Hi all,
Here is a list of some known regressions in 2.6.23-rc6.
Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions
List of Aces
NameRegressions fixed since 21-Jun-2007
Adrian Bunk10
Linus Torvalds
On Wed, Sep 12, 2007 at 06:58:46PM +0200, Michal Piotrowski wrote:
> Hi all,
>...
> Subject : uml on x86_64 compile error
> References : http://lkml.org/lkml/2007/9/3/86
> Last known good : ?
> Submitter : Adrian Bunk <[EMAIL PROTECTED]>
> Caused-By : Jeff Dike <[EMAIL PROT
On lunedì 27 agosto 2007, Fermín Galán Márquez wrote:
> Dear Paolo,
> First of all, thank you very much for your information regarding the
> status of bb/bs patches and mconsole exec functionality. That
> information will be very useful for us in the generation of new UML
> kernels for the VNUML P
21 matches
Mail list logo