Mateusz Guzik 09eb36ce3d Introduce CPU_SEQID_UNSTABLE ... Current CPU_SEQID users don't care about possibly changing CPU ID, but enclose it within kpreempt disable/enable in order to fend off warnings from Linux's CONFIG_DEBUG_PREEMPT. There is no need to do it. The expected way to get CPU ID while allowing for migration is to use raw_smp_processor_id. In order to make this future-proof this patch keeps CPU_SEQID as is and introduces CPU_SEQID_UNSTABLE instead, to make it clear that consumers explicitly want this behavior. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Ryan Moeller <ryan@iXsystems.com> Reviewed-by: Matt Macy <mmacy@FreeBSD.org> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com> Closes #11142		2020-11-02 11:51:12 -08:00
..
algs	ICP: gcm: Allocate hash subkey table separately	2020-10-30 15:24:21 -07:00
api	Remove checks for null out value in encryption paths	2020-03-26 10:41:57 -07:00
asm-x86_64	ICP: gcm: Allocate hash subkey table separately	2020-10-30 15:24:21 -07:00
core	Introduce CPU_SEQID_UNSTABLE	2020-11-02 11:51:12 -08:00
include	ICP: gcm: Allocate hash subkey table separately	2020-10-30 15:24:21 -07:00
io	ICP: gcm: Allocate hash subkey table separately	2020-10-30 15:24:21 -07:00
os	Replace sprintf()->snprintf() and strcpy()->strlcpy()	2020-06-07 11:42:12 -07:00
spi	Fix strdup conflict on other platforms	2019-10-10 09:47:06 -07:00
illumos-crypto.c	Fix typos in modules/icp/	2019-08-30 14:26:07 -07:00
Makefile.in	Cleanup linux module kbuild files	2020-06-10 09:24:15 -07:00