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
..
kcf_callprov.c	Fix spelling	2017-01-03 11:31:18 -06:00
kcf_mech_tabs.c	Fix typos in modules/icp/	2019-08-30 14:26:07 -07:00
kcf_prov_lib.c	Add convenience wrappers for common uio usage	2020-06-14 10:09:55 -07:00
kcf_prov_tabs.c	Add missing *_destroy/*_fini calls	2017-05-04 19:26:28 -04:00
kcf_sched.c	Introduce CPU_SEQID_UNSTABLE	2020-11-02 11:51:12 -08:00