Jan Kiszka wrote:
Gilles Chanteperdrix wrote:
But it does not seem to be due to the bug I was suspecting in context
switch code.
What about the PPC world? I saw some SVN commits claiming to fix this
(also for blackfin) - but there was no Hey, it's fixed now! on the
mailing
Jan Kiszka wrote:
Gilles Chanteperdrix wrote:
But it does not seem to be due to the bug I was suspecting in context
switch code.
What about the PPC world? I saw some SVN commits claiming to fix this
(also for blackfin) - but there was no Hey, it's fixed now! on the
mailing
Philippe Gerum wrote:
Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
Likely not this time (keep it cold anyway, who knows); I strongly
suspect a bug in
xnarch_switch_to() for all archs but x86
Now that you are talking about it, I may be the one who owes a beer to
Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
Likely not this time (keep it cold anyway, who knows); I strongly suspect a bug in
xnarch_switch_to() for all archs but x86
Now that you are talking about it, I may be the one who owes a beer to
everyone by first having put a bug in ia64
Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
Likely not this time (keep it cold anyway, who knows); I strongly suspect a bug in
xnarch_switch_to() for all archs but x86
Now that you are talking about it, I may be the one who owes a beer to
everyone by first having put a bug in ia64
Philippe Gerum wrote:
Likely not this time (keep it cold anyway, who knows); I strongly suspect a
bug in
xnarch_switch_to() for all archs but x86
Now that you are talking about it, I may be the one who owes a beer to
everyone by first having put a bug in ia64 context-switch code... If I
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Hi,
Some recent changes (*cough* RTDM benchmark driver *cough*) broke kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes somewhere in xnpod_schedule.
Heikki Lindholm wrote:
o When and how does it crash? At start-up immediately? Or after a
while?
I inserted some serial debug prints and it gets two passes to
eval_outer_loop done (enter/exit function). After that it freezes.
Without the debug printing it dies with kernel
Le dimanche 08 janvier 2006 à 18:56 +0200, Heikki Lindholm a écrit :
Some recent changes (*cough* RTDM benchmark driver *cough*) broke kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes somewhere in xnpod_schedule. Jan, any pending
patches a
Heikki Lindholm wrote:
Hi,
Some recent changes (*cough* RTDM benchmark driver *cough*) broke kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes somewhere in xnpod_schedule. Jan, any pending
patches a comin'?
Nope, it should work as it is. But
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Hi,
Some recent changes (*cough* RTDM benchmark driver *cough*) broke kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes somewhere in xnpod_schedule. Jan, any pending
patches a comin'?
Nope, it
Heikki Lindholm wrote:
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Hi,
Some recent changes (*cough* RTDM benchmark driver *cough*) broke kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes somewhere in xnpod_schedule. Jan, any pending
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Hi,
Some recent changes (*cough* RTDM benchmark driver *cough*) broke kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes somewhere in xnpod_schedule.
Heikki Lindholm wrote:
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Jan Kiszka kirjoitti:
Heikki Lindholm wrote:
Hi,
Some recent changes (*cough* RTDM benchmark driver *cough*) broke
kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes
Heikki Lindholm wrote:
o When and how does it crash? At start-up immediately? Or after a
while?
I inserted some serial debug prints and it gets two passes to
eval_outer_loop done (enter/exit function). After that it freezes.
Without the debug printing it dies with kernel
Le dimanche 08 janvier 2006 à 18:56 +0200, Heikki Lindholm a écrit :
Some recent changes (*cough* RTDM benchmark driver *cough*) broke kernel
mode benchmarking for ppc64. Previously klatency worked fine, but now
latency -t 1 crashes somewhere in xnpod_schedule. Jan, any pending
patches a
16 matches
Mail list logo
