From dd902d015a202e4cabb8fdadd307ec9a3dc38251 Mon Sep 17 00:00:00 2001 From: Gleb Smirnoff Date: Wed, 25 Sep 2019 18:26:31 +0000 Subject: Add debugging facility EPOCH_TRACE that checks that epochs entered are properly nested and warns about recursive entrances. Unlike with locks, there is nothing fundamentally wrong with such use, the intent of tracer is to help to review complex epoch-protected code paths, and we mean the network stack here. Reviewed by: hselasky Sponsored by: Netflix Pull Request: https://reviews.freebsd.org/D21610 --- sys/sys/proc.h | 1 + 1 file changed, 1 insertion(+) (limited to 'sys/sys/proc.h') diff --git a/sys/sys/proc.h b/sys/sys/proc.h index ae605a1266dd..8edca8ad889b 100644 --- a/sys/sys/proc.h +++ b/sys/sys/proc.h @@ -367,6 +367,7 @@ struct thread { void *td_lkpi_task; /* LinuxKPI task struct pointer */ struct epoch_tracker *td_et; /* (k) compat KPI spare tracker */ int td_pmcpend; + SLIST_HEAD(, epoch_tracker) td_epochs; }; struct thread0_storage { -- cgit v1.2.3