From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ammarfaizi2@gnuweeb.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
	server-vie001.gnuweeb.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,URIBL_ZEN_BLOCKED_OPENDNS
	autolearn=ham autolearn_force=no version=3.4.6
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org;
	s=new2025; t=1754755422;
	bh=EypI9G8Vr/nQW0k5/vP9i30wLp/EuxAkr8epbMXEq+Y=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:In-Reply-To:Message-ID:Date:From:Reply-To:Subject:To:
	 Cc:In-Reply-To:References:Resent-Date:Resent-From:Resent-To:
	 Resent-Cc:User-Agent:Content-Type:Content-Transfer-Encoding;
	b=h+V6mZ+SgWAby2j9+p+g30xLkGtTcRMllYCkbr9s7YwmujbweFCOznJxvtij8NUrb
	 1+8cpsF+rMvuZEWDRHrKG1ufVKLgKCkIqFOICDZhc07OFrFecwvhUK3DDh4US7u0FO
	 hvh7PlGtAEH8XM7bgzP8T/D8k0NuI98wyc2QBE4QEdvMjhQa1IHwXbWoleomnkRJu2
	 oSmmOuqxf3pa32No444zkW3Nmz2lfasTrrNS0VhcKV1YkOyNdjSPNF9/V5y4lftc8C
	 1JEBRUwTxEEy2aOfTTWvUtGe55Ys1xUjhXFWoOLJu4xHXr8aXTCzBnAty7Dc4jVdh7
	 OE1zQ+E+vB2VQ==
Received: from linux.gnuweeb.org (unknown [182.253.126.185])
	by server-vie001.gnuweeb.org (Postfix) with ESMTPSA id B4D083127D72;
	Sat,  9 Aug 2025 16:03:38 +0000 (UTC)
Date: Sat, 9 Aug 2025 23:03:35 +0700
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Nam Cao <namcao@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>, Lukas Wunner <lukas@wunner.de>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux PCI Mailing List <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rob Herring <robh@kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Krzysztof Wilczynski <kwilczynski@kernel.org>,
	Armando Budianto <sprite@gnuweeb.org>,
	Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
	gwml@vger.gnuweeb.org, namcaov@gmail.com
Subject: Re: [GIT PULL v2] PCI changes for v6.17
Message-ID: <aJdxVy1i3wGTvU3b@linux.gnuweeb.org>
References: <aJQ19UvTviTNbNk4@linux.gnuweeb.org>
 <aJXYhfc/6DfcqfqF@linux.gnuweeb.org>
 <aJXdMPW4uQm6Tmyx@linux.gnuweeb.org>
 <87ectlr8l4.fsf@yellow.woof>
 <aJZ/rum9bZqZInr+@biznet-home.integral.gnuweeb.org>
 <20250809043409.wLu40x1p@linutronix.de>
 <aJdNB8zITrkZ3n6r@linux.gnuweeb.org>
 <20250809144927.eUbR3MXg@linutronix.de>
 <aJdmGwFU6b9zh1BO@linux.gnuweeb.org>
 <87wm7ch5of.fsf@yellow.woof>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87wm7ch5of.fsf@yellow.woof>
X-Gw-Outgoing-Server-Hash: 01afd303c8b96d0c1d5e80aa96a4ee40ec69888f786fa24107c0862c0644af79
List-Id: <gwml.vger.gnuweeb.org>

On Sat, Aug 09, 2025 at 05:32:16PM +0200, Nam Cao wrote:
> So unlike what VMD doc says, it actually can have non-MSI-X children devices!

If that's the conclusion, then Intel VMD doc also needs fixing :/

> Please discard the reverts and the diff I sent you, and try the diff
> below. I believe your machine will work now.

Yes, I can confirm it's now clean. Just to verify both sides, here is
the last result:

  https://gist.github.com/ammarfaizi2/72578d2b4cc385fbdb5faee69013d530

If that one fix is final, then:

Tested-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>

Thanks for the debugging work.

It's probably too late to get the fix in mainline before rc1. But if it
can go upstream sooner, that would be great.

-- 
Ammar Faizi