For reporting bugs send an email to the list. Alternatively, you can create an issue on our Github project: * https://github.com/netsniff-ng/netsniff-ng/issues If you use Fedora or have a RHEL subscription, you can also report bugs to: * https://bugzilla.redhat.com/ If you use Debian Linux, we might also process / track bugs there: * http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=netsniff-ng In any way, you'll get a reply from us. Please do not contact individual developers directly in case of netsniff-ng issues or patches, but rather always our mailing list. By this, you're not wasting time of a single developer and increase your chances of getting a reply from us. In general, we are also highly interested in how you use the toolkit, what problems you are trying to solve and what kind of things you would like to have improved. So feel free to drop us some feature requests as well. net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorValentin Rothberg <valentinrothberg@gmail.com>2016-10-05 07:57:26 +0200
committerMichael Ellerman <mpe@ellerman.id.au>2016-10-27 21:52:59 +1100
commit39715bf972ed4fee18fe5409609a971fb16b1771 (patch)
tree1d423c94bc8d3199a42f16b6296c9d96e929982b /Documentation
parent09b7e37b18eecc1e347f4b1a3bc863f32801f634 (diff)
powerpc/process: Fix CONFIG_ALIVEC typo in restore_tm_state()
It should be ALTIVEC, not ALIVEC. Cyril explains: If a thread performs a transaction with altivec and then gets preempted for whatever reason, this bug may cause the kernel to not re-enable altivec when that thread runs again. This will result in an altivec unavailable fault, when that fault happens inside a user transaction the kernel has no choice but to enable altivec and doom the transaction. The result is that transactions using altivec may get aborted more often than they should. The difficulty in catching this with a selftest is my deliberate use of the word may above. Optimisations to avoid FPU/altivec/VSX faults mean that the kernel will always leave them on for 255 switches. This code prevents the kernel turning it off if it got to the 256th switch (and userspace was transactional). Fixes: dc16b553c949 ("powerpc: Always restore FPU/VEC/VSX if hardware transactional memory in use") Reviewed-by: Cyril Bur <cyrilbur@gmail.com> Signed-off-by: Valentin Rothberg <valentinrothberg@gmail.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'Documentation')