From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 280AD34F25E for ; Wed, 17 Dec 2025 17:37:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765993072; cv=none; b=g7YvThXTCR9Ubd1ZbjdRyFV3t6j3ieG5xL3Teh0e4VoityrXzBuDDA7IaiGWvPC1jD2SV6seiH8YNPeS/+ga+i2MaMZxje2qVm85lh7CHk7xJxDznMk0JQGNqTuJepdhdodBZOKlVzD63i5kKHCjE+z8a2EqUCWUz48uGp4zAI4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765993072; c=relaxed/simple; bh=vYvaIKT5Xi4f/Wr4SqpcCFZoR6ZtQCOTHcIuOzVAycI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=nNCEL72+NLXOoy14Me56SQ8jv825NOqIEUu0p/CxB5Nz0xWylIjCsokxqvV5UjUisSQ9EH4TLKtDjbn8by5rnH8LGjd7rGQWO9YhIq4isxNpy31BYfOmDQGLXvMSNupeWTHXGHEZVne5gIsXot1WujLBc7Sbgjn/RfsvF2wbzG4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=BeIYzJVB; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=JRvY0Ayp; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="BeIYzJVB"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="JRvY0Ayp" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1765993068; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iwbwkDX6ioPU48baEkSJK5UD8g6R1KXCYkL7X8KBz98=; b=BeIYzJVB1X1C063wO3rwDtyGTiwvRLrAl1aO4bKztjewxO54y0LyNMHkNn//cuSomo4FFe fsIpE+9w8IBza2oQc1TJQARAguo5vzN/KFjEDftMWk8GULIRXsXVTSS+K0oN6oAam8a+AO I5RWcnaF/Jcr26ji/PLBrnk4Lj9Lc8+u+WsuAVQiZXzdsgFTL3oXhpSD4cxa5RpzpgeJ1E JCmEQzV94jcaf4TkXYomSgC/diezUtXwh36ym+8NGvFlvuWHCIkv+Q84SL67BmI5XNa9VE G0TBA1Ro+tO4YxDmipD4TDYLOulTu7mnkpXwH7XRj1zNfnff0NQIVI9j0UAMCg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1765993068; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iwbwkDX6ioPU48baEkSJK5UD8g6R1KXCYkL7X8KBz98=; b=JRvY0Aypc+3yUrWc2nUkyqy4zRxBnr8RDsRt69l5eyWqCSffNb3msoAt+JUtrDXrK6Xi8i gV7F5LshYvK+DkDQ== To: Luigi Rizzo Cc: LKML , x86@kernel.org Subject: Re: [patch V2 0/3] x86/irq: Bugfix and cleanup for posted MSI interrupts In-Reply-To: References: <20251125214446.766096680@linutronix.de> Date: Wed, 17 Dec 2025 18:37:46 +0100 Message-ID: <875xa5c8lx.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Wed, Dec 17 2025 at 18:03, Luigi Rizzo wrote: > On Tue, Nov 25, 2025 at 10:50=E2=80=AFPM Thomas Gleixner wrote: >> >> A small update to V1 which can be found here: >> >> https://lore.kernel.org/lkml/20251125101912.564125647@linutronix.de >> >> Luigi reported that the retrigger mechanism for posted MSI interrupts is >> broken. That happens because retrigger sends an IPI to the actual alloca= ted >> vector, which is handled correctly, but lacks an EOI. That leaves a stale >> APIC ISR bit around. >> >> The following series addresses this and does some related cleanups in th= at >> area on top. > > What is happening with this series, is there any blocker ? I don't think so. It's probably because people were traveling to Japan or distracted otherwise. I'll take care of it now. Thanks, tglx