From: "Dong, Eric" <eric.dong@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] MdeModulePkg/PciBus: Fix bug that PCI BUS claims too much resource
Date: Mon, 23 Oct 2017 07:16:10 +0000 [thread overview]
Message-ID: <ED077930C258884BBCB450DB737E66224AA3D408@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20171020095608.161848-1-ruiyu.ni@intel.com>
Reviewed-by: Eric Dong <eric.dong@intel.com>
> -----Original Message-----
> From: Ni, Ruiyu
> Sent: Friday, October 20, 2017 5:56 PM
> To: edk2-devel@lists.01.org
> Cc: Dong, Eric <eric.dong@intel.com>
> Subject: [PATCH] MdeModulePkg/PciBus: Fix bug that PCI BUS claims too
> much resource
>
> The bug was caused by 728d74973c9262b6c7b7ef4be213223d55affec3
> "MdeModulePkg/PciBus: Count multiple hotplug resource paddings".
>
> The patch firstly updated the Bridge->Alignment to the maximum alignment
> of all devices under the bridge, then aligned the
> Bridge->Length to Bridge->Alignment.
> It caused too much resources were claimed.
>
> The new patch firstly aligns Bridge->Length to Bridge->Alignment, then
> updates the Bridge->Alignment to the maximum alignment of all devices
> under the bridge.
> Because the step to update the Bridge->Alignment is to make sure the
> resource allocated to the bus under the Bridge meets all devices alignment.
> But the Bridge->Length doesn't have to align to the maximum alignment.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> ---
> .../Bus/Pci/PciBusDxe/PciResourceSupport.c | 24 +++++++++++----------
> -
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/MdeModulePkg/Bus/Pci/PciBusDxe/PciResourceSupport.c
> b/MdeModulePkg/Bus/Pci/PciBusDxe/PciResourceSupport.c
> index 8dbe9a0038..2f713fcee9 100644
> --- a/MdeModulePkg/Bus/Pci/PciBusDxe/PciResourceSupport.c
> +++ b/MdeModulePkg/Bus/Pci/PciBusDxe/PciResourceSupport.c
> @@ -389,18 +389,7 @@ CalculateResourceAperture (
> }
>
> //
> - // Adjust the bridge's alignment to the MAX (first) alignment of all children.
> - //
> - CurrentLink = Bridge->ChildList.ForwardLink;
> - if (CurrentLink != &Bridge->ChildList) {
> - Node = RESOURCE_NODE_FROM_LINK (CurrentLink);
> - if (Node->Alignment > Bridge->Alignment) {
> - Bridge->Alignment = Node->Alignment;
> - }
> - }
> -
> - //
> - // At last, adjust the aperture with the bridge's alignment
> + // Adjust the aperture with the bridge's alignment
> //
> Aperture[PciResUsageTypical] = ALIGN_VALUE
> (Aperture[PciResUsageTypical], Bridge->Alignment + 1);
> Aperture[PciResUsagePadding] = ALIGN_VALUE
> (Aperture[PciResUsagePadding], Bridge->Alignment + 1); @@ -410,6 +399,17
> @@ CalculateResourceAperture (
> // Use the larger one between the padding resource and actual occupied
> resource.
> //
> Bridge->Length = MAX (Aperture[PciResUsageTypical],
> Aperture[PciResUsagePadding]);
> +
> + //
> + // Adjust the bridge's alignment to the MAX (first) alignment of all children.
> + //
> + CurrentLink = Bridge->ChildList.ForwardLink; if (CurrentLink !=
> + &Bridge->ChildList) {
> + Node = RESOURCE_NODE_FROM_LINK (CurrentLink);
> + if (Node->Alignment > Bridge->Alignment) {
> + Bridge->Alignment = Node->Alignment;
> + }
> + }
> }
>
> /**
> --
> 2.12.2.windows.2
prev parent reply other threads:[~2017-10-23 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:56 [PATCH] MdeModulePkg/PciBus: Fix bug that PCI BUS claims too much resource Ruiyu Ni
2017-10-23 7:16 ` Dong, Eric [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ED077930C258884BBCB450DB737E66224AA3D408@shsmsx102.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox