diff options
| author | maxv <maxv@NetBSD.org> | 2018-03-01 16:49:06 +0000 |
|---|---|---|
| committer | maxv <maxv@NetBSD.org> | 2018-03-01 16:49:06 +0000 |
| commit | ee9e9ddc413d9498a36bc999281e45dbfc4c5373 (patch) | |
| tree | 2dfbfd9e3e994980fb469c92393ffc8c2fad85da /sys/dev/microcode | |
| parent | 37718c7bd69dccd4216facdc9fb1bb779d6b0924 (diff) | |
Remove these two KASSERTs. Thinking about it, they may fire when the user
enters "sysctl -w machdep.svs.enabled=0", if the xcall is received between
the 'svs_enabled' check in the caller and the same check in these KASSERTs.
In such a case we perform an SVS operation with svs_enabled set to false,
but that's intentional: after it is done svs_pmap_sync and svs_lwp_switch
won't be called anymore, the pdir synchronization is dropped.
Having said that, I didn't see these KASSERTs getting triggered.
Diffstat (limited to 'sys/dev/microcode')
0 files changed, 0 insertions, 0 deletions
