diff options
| author | Pavel Pisa <pisa@cmp.felk.cvut.cz> | 2005-05-01 08:58:52 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-05-01 08:58:52 -0700 |
| commit | ad6714230f2269d5d7db2cd1900fe7bfc7aa76dc (patch) | |
| tree | f73fa14b2934ddf7e542a678eb8fe1f876ae6d98 /crypto/internal.h | |
| parent | f9ba70535dc12d9eb57d466a2ecd749e16eca866 (diff) | |
| download | op-kernel-dev-ad6714230f2269d5d7db2cd1900fe7bfc7aa76dc.zip op-kernel-dev-ad6714230f2269d5d7db2cd1900fe7bfc7aa76dc.tar.gz | |
[PATCH] Linux 2.6.x VM86 interrupt emulation fixes
Patch solves VM86 interrupt emulation deadlock on SMP systems. The VM86
interrupt emulation has been heavily tested and works well on UP systems
after last update, but it seems to deadlock when we have used it on SMP/HT
boxes now.
It seems, that disable_irq() cannot be called from interrupts, because it
waits until disabled interrupt handler finishes
(/kernel/irq/manage.c:synchronize_irq():while(IRQ_INPROGRESS);). This
blocks one CPU after another. Solved by use disable_irq_nosync.
There is the second problem. If IRQ source is fast, it is possible, that
interrupt is sometimes processed and re-enabled by the second CPU, before
it is disabled by the first one, but negative IRQ disable depths are not
allowed. The spinlocking and disabling IRQs over call to
disable_irq_nosync/enable_irq is the only solution found reliable till now.
Signed-off-by: Michal Sojka <sojkam1@control.felk.cvut.cz>
Signed-off-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'crypto/internal.h')
0 files changed, 0 insertions, 0 deletions
