linux-kernel - Re: [PATCH v7 08/17] ACPI: pci_link: Clear the dependencies after probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aS5q28HPYLzK6h8r@sunil-laptop>
Date: Tue, 2 Dec 2025 09:58:11 +0530
From: Sunil V L <sunilvl@...tanamicro.com>
To: huyuye <huyuye812@....com>
Cc: ajones@...tanamicro.com, anup@...infault.org, aou@...s.berkeley.edu,
	atishp@...osinc.com, bhelgaas@...gle.com, catalin.marinas@....com,
	conor.dooley@...rochip.com, dfustini@...storrent.com,
	haibo1.xu@...el.com, lenb@...nel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, linux-riscv@...ts.infradead.org,
	palmer@...belt.com, rafael@...nel.org, robert.moore@...el.com,
	samuel.holland@...ive.com, tglx@...utronix.de, will@...nel.org,
	dai.hualiang@....com.cn, deng.weixian@....com.cn,
	guo.chang2@....com.cn, liu.qingtao2@....com.cn,
	wu.jiabao@....com.cn, lin.yongchun@....com.cn, hu.yuye@....com.cn,
	zhang.longxiang@....com.cn
Subject: Re: [PATCH v7 08/17] ACPI: pci_link: Clear the dependencies after
 probe

On Mon, Dec 01, 2025 at 10:12:29PM +0800, huyuye wrote:
> > Hi, sunilvl
> 
> > Based on the above patch, I understand that you previously >resolved dependencies between Link devices and PCI Host Bridges by >calling acpi_dev_clear_dependencies(device). I would like to ask: >on RISC‑V platforms, if we need to manage dependencies between >multiple PCI Host Bridges, could this be addressed by adding a >call to acpi_dev_clear_dependencies(device) at the end of the >acpi_pci_root_add enumeration function?
> 
> > Initialization order dependencies can be defined via the ACPI >_DEP method in the DSDT. For example, if host bridge B depends on >host bridge A, bridge B should not be enumerated until bridge A is >fully initialized.
> 
> > Yes, that should work.
> > Regards,
> > Sunil
> 
> Hi,Sunil
> 
> I'm truly honored by your affirmation of my answer.Do you think this solution has a chance of being accepted into the upstream kernel? Are there any unintended side effects we may have overlooked?
> 
Acceptance of this solution depends on the PCI/ACPI maintainers. To help
them evaluate it, you should clearly describe why your platform requires
this dependency in the patch.

Regards
Sunil