linux-kernel - Re: [PATCH 10/11] pciehp: add support for bridge resource reallocation

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100116045911.GI22215@ldl.fc.hp.com>
Date:	Fri, 15 Jan 2010 21:59:11 -0700
From:	Alex Chiang <achiang@...com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH 10/11] pciehp: add support for bridge resource
	reallocation

* Yinghai Lu <yinghai@...nel.org>:
> From: Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
> 
> With this patch, pciehp driver try to clear PCI bridge resources to
> parent bridge (root port or switch downstream port) of the slot
> 
> so we can shrink pci bridge resource for those port
> 
> This feature is enabled when 'pciehp_realloc' option is specified.
> 
> -v2: make it could be appiled after Yinghai patchset that touch pci bridge
>      resource also remove poweron check, because pci_bridge_release_res will
>      check child at first

Same comment as my earlier patch. Why not just make this the
default behavior, instead of introducing yet another command line
parameter for users to guess at?

/ac

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/