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
..
linux	FreeBSD: make adjustments for the standalone environment	2020-10-13 21:05:49 -07:00
spl	Introduce CPU_SEQID_UNSTABLE	2020-11-02 11:51:12 -08:00
zfs	Remove duplicate cond_resched() definition	2020-10-31 09:37:56 -07:00
Makefile.am	Add FreeBSD support to OpenZFS	2020-04-14 11:36:28 -07:00