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 A0B2F253B60; Tue, 25 Mar 2025 08:11:12 +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=1742890274; cv=none; b=HB/+k7Pz5rOeNDD+jSSIaJUWF0mPaTcVNEKJlnR7mkeZnPxKtFhCKs9qP7+/ensCOTmGzE1CFTFxr7oaWvXVjYg4lMDj7aUV6meVgqXzk4jYyTYbRsGEhk1rc1h4JF82i4rlZHTt+EGFWL0VRfW6614kNOj8F4be2VLok4x5B2Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1742890274; c=relaxed/simple; bh=8gjoMs+t6/hW1hSlaknfnqD78WUml+/4v7BFGq/X2W8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Wp+PopehmVBy3jDuyF0J4x/fGRfi3W7i6YuvsbRCABYl8eGxM56cQYwlKRgzdpHdhjNwhTeXuSIOs+DRCEDP6jQcak34gW5BJStaaj3D66akKMN4vuhAx1HNN+wwbgJbWdiRewfTBix4X7M0otAg54ZwIt3RPmRsceWvt+lYQWg= 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=xuu9Wv6p; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=zawn//iF; 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="xuu9Wv6p"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="zawn//iF" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1742890269; 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=gBlYuYPxuiW4f/YH3m2JiPO9h8/st5bDHO18kaoaxWU=; b=xuu9Wv6psqJzPFfn8nMntVCSCH9iODJd96EJ94rTd8BA3tpxSRI7FC+Z8px+3BfOtKWwz4 EQNAYMOijbgOFFS7+rH/VfTxOn3FxTl5i4udS+twC9fl5AXSJ702DONji18Nfzufxt3P8k hAJMo9n336BIMnf84oX/JXqSA0j0lKk6zhJuprnlWpwoGcrlYJRF1G/qysdW9NOceQ8IWz AxC3zXeAMYHxivQJvG3CSp+tbm0DA65C8MoZL07GOeZp7AaIlLeLgXZ217wNE9p4f98eNQ FWWjzyRHu5AOK9111zSqok0p+97KrvNlYKC5GAOPqqYwJuqrraND0jAhG6UZfA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1742890269; 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=gBlYuYPxuiW4f/YH3m2JiPO9h8/st5bDHO18kaoaxWU=; b=zawn//iFOlyQCFAWgDgHOmxcNuu0Ak6JkpKA/7TZ4dwphNSIIW3fFEFxxZVI3iFGgo16uU kGLzpS+oUoMNZnBg== To: Roger Pau =?utf-8?Q?Monn=C3=A9?= , Daniel Gomez Cc: =?utf-8?B?SsO8cmdlbiBHcm/Dnw==?= , Bjorn Helgaas , linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org, linux-pci@vger.kernel.org, Bjorn Helgaas , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" Subject: Re: [PATCH v3 3/3] PCI/MSI: Convert pci_msi_ignore_mask to per MSI domain flag In-Reply-To: References: <20250320210741.GA1099701@bhelgaas> <846c80f8-b80f-49fd-8a50-3fe8a473b8ec@suse.com> Date: Tue, 25 Mar 2025 09:11:08 +0100 Message-ID: <87y0wtzg0z.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 Mon, Mar 24 2025 at 20:18, Roger Pau Monn=C3=A9 wrote: > On Mon, Mar 24, 2025 at 07:58:14PM +0100, Daniel Gomez wrote: >> The issue is that info appears to be uninitialized. So, this worked for = me: > > Indeed, irq_domain->host_data is NULL, there's no msi_domain_info. As > this is x86, I was expecting x86 ot always use > x86_init_dev_msi_info(), but that doesn't seem to be the case. I > would like to better understand this. Indeed. On x86 this should not happen at all. On architectures, which do not use (hierarchical) interrupt domains, it will return NULL. So I really want to understand why this happens on x86 before such a "fix" is deployed. Thanks, tglx