[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h6r2pm1a.ffs@tglx>
Date: Tue, 20 Jun 2023 10:37:05 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Xin Li <xin3.li@...el.com>, linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org, iommu@...ts.linux.dev,
linux-hyperv@...r.kernel.org, linux-perf-users@...r.kernel.org,
x86@...nel.org
Cc: mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
hpa@...or.com, steve.wahl@....com, mike.travis@....com,
dimitri.sivanich@....com, russ.anderson@....com,
dvhart@...radead.org, andy@...radead.org, joro@...tes.org,
suravee.suthikulpanit@....com, will@...nel.org,
robin.murphy@....com, kys@...rosoft.com, haiyangz@...rosoft.com,
wei.liu@...nel.org, decui@...rosoft.com, dwmw2@...radead.org,
baolu.lu@...ux.intel.com, peterz@...radead.org, acme@...nel.org,
mark.rutland@....com, alexander.shishkin@...ux.intel.com,
jolsa@...nel.org, namhyung@...nel.org, irogers@...gle.com,
adrian.hunter@...el.com, xin3.li@...el.com, seanjc@...gle.com,
jiangshanlai@...il.com, jgg@...pe.ca, yangtiezhu@...ngson.cn
Subject: Re: [PATCH 2/3] x86/vector: Replace IRQ_MOVE_CLEANUP_VECTOR with a
timer callback
On Mon, Jun 19 2023 at 16:16, Xin Li wrote:
> +/*
> + * Called with vector_lock held
> + */
Such a comment is patently bad.
> +static void __vector_cleanup(struct vector_cleanup *cl, bool check_irr)
> {
....
lockdep_assert_held(&vector_lock);
Documents the requirement clearly _and_ catches any caller which does not
hold the lock when lockdep is enabled.
Thanks,
tglx
Powered by blists - more mailing lists