diff options
| author | marius <marius@FreeBSD.org> | 2013-01-23 22:52:20 +0000 |
|---|---|---|
| committer | marius <marius@FreeBSD.org> | 2013-01-23 22:52:20 +0000 |
| commit | 6892c8a3befeed6ac18475f3b47fe5e621c613f2 (patch) | |
| tree | b3509aa07c2392071b525e3609bd5d09c8029f06 /kerberos5 | |
| parent | af17a55dfd7a008dea74152e32f5d6c803b46bdd (diff) | |
| download | FreeBSD-src-6892c8a3befeed6ac18475f3b47fe5e621c613f2.zip FreeBSD-src-6892c8a3befeed6ac18475f3b47fe5e621c613f2.tar.gz | |
Revert the part of r239864 which removed obtaining the SMP mutex around
reading registers from other CPUs. As it turns out, the hardware doesn't
really like concurrent IPI'ing causing adverse effects. Also the thought
deadlock when using this spin lock here and the targeted CPU(s) are also
holding or in case of nested locks can't actually happen. This is due to
the fact that on sparc64, spinlock_enter() only raises the PIL but doesn't
disable interrupts completely. Thus direct cross calls as used for the
register reading (and all other MD IPI needs) still will be executed by
the targeted CPU(s) in that case.
MFC after: 3 days
Diffstat (limited to 'kerberos5')
0 files changed, 0 insertions, 0 deletions
