From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 71D5110ED656 for ; Fri, 27 Mar 2026 10:19:22 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.1265330.1556311 (Exim 4.92) (envelope-from ) id 1w64HX-0005Kv-LJ; Fri, 27 Mar 2026 10:19:11 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1265330.1556311; Fri, 27 Mar 2026 10:19:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1w64HX-0005Ko-I5; Fri, 27 Mar 2026 10:19:11 +0000 Received: by outflank-mailman (input) for mailman id 1265330; Fri, 27 Mar 2026 10:19:10 +0000 Received: from mx.expurgate.net ([195.190.135.10]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1w64HV-0005Ke-Ov for xen-devel@lists.xenproject.org; Fri, 27 Mar 2026 10:19:09 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1w64HU-006BHL-Q1 for xen-devel@lists.xenproject.org; Fri, 27 Mar 2026 11:19:09 +0100 Received: from [10.42.69.4] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 69c65996-2eae-0a2a0a5409dd-0a2a4504b988-26 for ; Fri, 27 Mar 2026 11:19:08 +0100 Received: from [202.12.124.147] (helo=fout-b4-smtp.messagingengine.com) by tlsNG-ebf023.mxtls.expurgate.net with ESMTPS (eXpurgate 4.55.2) (envelope-from ) id 69c6599b-c823-0a2a45040019-ca0c7c93a529-3 for ; Fri, 27 Mar 2026 11:19:08 +0100 Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailfout.stl.internal (Postfix) with ESMTP id 968781D00071; Fri, 27 Mar 2026 06:19:06 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-01.internal (MEProxy); Fri, 27 Mar 2026 06:19:06 -0400 Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 27 Mar 2026 06:19:05 -0400 (EDT) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=fm1 header.d=invisiblethingslab.com header.i="@invisiblethingslab.com" header.h="Cc:Content-Type:Date:From:Message-ID:MIME-Version:Subject:To"; dkim=pass header.s=fm1 header.d=messagingengine.com header.i="@messagingengine.com" header.h="Cc:Content-Type:Date:Feedback-ID:From:Message-ID:MIME-Version:Subject:To:X-ME-Proxy:X-ME-Sender" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= invisiblethingslab.com; h=cc:cc:content-type:content-type:date :date:from:from:in-reply-to:message-id:mime-version:reply-to :subject:subject:to:to; s=fm1; t=1774606746; x=1774693146; bh=T9 PMY9DFdJXlLu5egrUOc86EVZd3HqqVfAflpl48KNk=; b=feF7A+aIZjtTc9UhQl Oh68hIOy69XaJFb/Oy74EySbnn17JqIIktOi6vGR5ZEOdkidbfYfEdNaik3J+xts ISweGonz6+x/bGZtj2SEx826/5mmrJuZLEXl0nQTynbp6hnIgsbdxaFRaT2GeNR2 520kX1Uo6RkEhWFmKdi/1G591SCjPbb6ynY4UWEdfd3Ql3dB4PQuy7FdCB9kgNa3 vPPLbYQ2FHNLGtPe3zi/uZ8CLuKPmvkl7sG4D584Dy2rESOmUy9FP+wFM+un1uwk Hfd/AWUpBi5OTgKxX12p3TrE1Fwi0BIl+zvY27at4TahB7DUdaB6sX93a9ajzM16 pm3A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1774606746; x= 1774693146; bh=T9PMY9DFdJXlLu5egrUOc86EVZd3HqqVfAflpl48KNk=; b=S BPV9v7CiS4jwqPvjiXIU1KjoqYJtRWteOWdKsWau4e5mDeaJYnyoUgUIvgO2mVoa B3j9EtB2+izFj0yky2hGy5swZZJYk9QgSu5LVc0ovbKqXT5i3K0RexXf+DpGmgjR yRJv+j9UU8t1akFQS+syEc4H69nRd6TOgDTv5TeulghXNnKXiLf38IUD+KrACNUN 7ppPukjD7k6/2fNxk7rSPkO59YDmwe5gx3O+JhhglBmgh2AM2mnPb9jVllv7snCV r9Z+XZEfbGG6CE6tppBM9QWXcVTJFc2HDIH14cYAm+YmQIL/QZMpbWNh8ZzL4YP0 pup55Q8S1HRMNjLMMSHMw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdeffedttddvucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepfffhvfevuffkgggtugesghdtreertddtjeenucfhrhhomhepofgrrhgvkhcuofgr rhgtiiihkhhofihskhhiqdfikphrvggtkhhiuceomhgrrhhmrghrvghksehinhhvihhsih gslhgvthhhihhnghhslhgrsgdrtghomheqnecuggftrfgrthhtvghrnhepvdelvedtfedt jeegtedvieduveejteehiefgfefhfeeuvdfhudffgfekjedtfeetnecuffhomhgrihhnpe hgihhtlhgrsgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehmrghrmhgrrhgvkhesihhnvhhishhisghlvghthhhinhhgshhlrggsrd gtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprhgtphhtthho peigvghnqdguvghvvghlsehlihhsthhsrdigvghnphhrohhjvggtthdrohhrghdprhgtph htthhopehjsggvuhhlihgthhesshhushgvrdgtohhm X-ME-Proxy: Feedback-ID: i1568416f:Fastmail Date: Fri, 27 Mar 2026 11:19:04 +0100 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= To: xen-devel Cc: Jan Beulich Subject: IOMMU faults after S3 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jyaOBGeUZIKSV3mQ" Content-Disposition: inline X-purgate-ID: tlsNG-ebf023/1774606748-B8A8E9D1-38D921FA/0/0 X-purgate-type: clean X-purgate-size: 3021 --jyaOBGeUZIKSV3mQ Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Date: Fri, 27 Mar 2026 11:19:04 +0100 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= To: xen-devel Cc: Jan Beulich Subject: IOMMU faults after S3 Hi, I noticed that on some systems, there are a lot of IOMMU faults after S3. I can see it also on a laptop with MTL, but it affects also the ADL gitlab runner: https://gitlab.com/xen-project/hardware/xen/-/jobs/13661033722 (XEN) [ 37.201160] [VT-D]DMAR:[DMA Write] Request device [0000:00:1e.= 6] fault addr 0 (XEN) [ 37.201164] [VT-D]DMAR: reason 02 - Present bit in context ent= ry is clear (XEN) [ 37.202332] [VT-D]DMAR:[DMA Write] Request device [0000:00:1e.= 6] fault addr 0 (XEN) [ 37.202339] [VT-D]DMAR: reason 02 - Present bit in context ent= ry is clear Interestingly, the 0000:00:1e.6 device is not even listed by lspci. The issue is present only on staging, not staging-4.21. Bisect says: 5ec93b2f19ff8873fca65d38c1164b0a56d3898b is the first bad commit commit 5ec93b2f19ff8873fca65d38c1164b0a56d3898b Author: Jan Beulich Date: Thu Jan 22 14:13:35 2026 +0100 x86/HPET: drop .set_affinity hook =20 No IRQ balancing is supposed to be happening on the broadcast IRQs. The only entity responsible for fiddling with the CPU affinities is set_channel_irq_affinity(). They shouldn't even be fiddled with when offlining a CPU: A CPU going down can't at the same time be idle. Some properties (->arch.cpu_mask in particular) may transiently reference an offline CPU, but that'll be adjusted as soon as a channel goes into act= ive use again. =20 Along with adjusting fixup_irqs() (in a more general way, i.e. covering= all vectors which are marked in use globally), also adjust section placemen= t of used_vectors. =20 Signed-off-by: Jan Beulich Reviewed-by: Roger Pau Monn=C3=A9 xen/arch/x86/hpet.c | 17 ----------------- xen/arch/x86/irq.c | 12 ++++++++---- 2 files changed, 8 insertions(+), 21 deletions(-) --=20 Best Regards, Marek Marczykowski-G=C3=B3recki Invisible Things Lab --jyaOBGeUZIKSV3mQ Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmnGWZgACgkQ24/THMrX 1yxPjggAlPAFrHJ3jn1JcEeCvilGgls72KrF6WHOREZbKKPWqB00Meiv16+T1FYp BLDPL0mzb5MqUj4JxJMAs8Urw01629MTCrU0xPyRKnT3YeMVKDzhg+OJzLCwX+ra pOIcnJ826uu2UTq1MG41thQoqadOiq71opndqOlPnN5cva4RQsaWnPa++tAU+2bi MYvHMBPeMoPOGILlrGloTbZLhA+VlKCS0VxUbijKa6+w4GNg8/mSfhIT1P7PeF/7 lfNjDAfRAokfn71Xnr1srWjCDzRRnlkwJxYemiaediaygZ9VOphXX/sfu2KmtfUe o5n/NaS4Ykd4kDxsZiHdFV3c01OsIA== =MTO3 -----END PGP SIGNATURE----- --jyaOBGeUZIKSV3mQ--