on 11/02/2012 00:42 Sushanth Rai said the following:
> Basically I would like to force system panic (and take kernel dump) when
> watchdog time expires. Assuming that timer expired due to some OS bug, kernel
> memory dump would be very useful. I'm running freebsd 7.2 on Intel IbexPeak
> chipset. Ac
on 06/02/2012 09:04 Alexander Motin said the following:
> Hi.
>
> I've analyzed scheduler behavior and think found the problem with HTT.
> SCHED_ULE
> knows about HTT and when doing load balancing once a second, it does right
> things. Unluckily, if some other thread gets in the way, process can
On 02/11/12 15:35, Andriy Gapon wrote:
on 06/02/2012 09:04 Alexander Motin said the following:
I've analyzed scheduler behavior and think found the problem with HTT. SCHED_ULE
knows about HTT and when doing load balancing once a second, it does right
things. Unluckily, if some other thread gets
On Sat, Feb 11, 2012 at 04:21:25PM +0200, Alexander Motin wrote:
> At this moment I am using different penalty coefficients for SMT and
> shared caches (for unrelated processes sharing is is not good). No
> problem to add more types there. Separate flag for shared FPU could be
> used to have dif
on 11/02/2012 15:35 Andriy Gapon said the following:
> It seems that on modern CPUs the caches are either inclusive or some smart "as
> if inclusive" caches. As a result, if two cores have a shared cache at any
> level, then it should be relatively cheap to move a thread from one core to
> the
>
I had looked at this. It seems to be doing the opposite of what I want. That
is, it routes a NMI as an SMI and I need SMI to trigger an NMI. Watchdog timer
on 3100 chipset had the ability to send either an NMI or SMI when the timer
fired for the first time. I used NMI to generate kernel panic.
6 matches
Mail list logo
