From: "Ni, Ruiyu" <ruiyu.ni@Intel.com>
To: Star Zeng <star.zeng@intel.com>, edk2-devel@lists.01.org
Cc: Tomson Chang <tomson.chang@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Jenny Huang <jenny.huang@intel.com>,
Amy Chan <amy.chan@intel.com>
Subject: Re: [PATCH] IntelSiliconPkg IntelVTdDxe: Optimize when func 0 is not implemented
Date: Thu, 13 Sep 2018 11:10:44 +0800 [thread overview]
Message-ID: <7a0c6bc9-eb4d-6e84-8bd1-fac8bab6e1ed@Intel.com> (raw)
In-Reply-To: <1536804602-13240-1-git-send-email-star.zeng@intel.com>
On 9/13/2018 10:10 AM, Star Zeng wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1169
>
> PCI spec:
> They are also required to always implement function 0 in the device.
> Implementing other functions is optional and may be assigned in any
> order (i.e., a two-function device must respond to function 0 but
> can choose any of the other possible function numbers (1-7) for the
> second function).
>
> This patch updates ScanPciBus() to not scan other functions if
> function 0 is not implemented.
>
> Test done:
> Added debug code below in the second loop of ScanPciBus(),
> compared the debug logs with and without this patch, many
> non-0 unimplemented functions are skipped correctly.
>
> DEBUG ((
> DEBUG_INFO,
> "%a() B%02xD%02xF%02x VendorId: %04x DeviceId: %04x\n",
> __FUNCTION__,
> Bus,
> Device,
> Function,
> VendorID,
> DeviceID
> ));
>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Rangasai V Chaganty <rangasai.v.chaganty@intel.com>
> Cc: Tomson Chang <tomson.chang@intel.com>
> Cc: Jenny Huang <jenny.huang@intel.com>
> Cc: Amy Chan <amy.chan@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Star Zeng <star.zeng@intel.com>
> ---
> IntelSiliconPkg/Feature/VTd/IntelVTdDxe/PciInfo.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/PciInfo.c b/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/PciInfo.c
> index 36750b3f1d9c..305995de032c 100644
> --- a/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/PciInfo.c
> +++ b/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/PciInfo.c
> @@ -1,6 +1,6 @@
> /** @file
>
> - Copyright (c) 2017, Intel Corporation. All rights reserved.<BR>
> + Copyright (c) 2017 - 2018, Intel Corporation. All rights reserved.<BR>
> This program and the accompanying materials
> are licensed and made available under the terms and conditions of the BSD License
> which accompanies this distribution. The full text of the license may be found at
> @@ -247,6 +247,12 @@ ScanPciBus (
> VendorID = PciSegmentRead16 (PCI_SEGMENT_LIB_ADDRESS(Segment, Bus, Device, Function, PCI_VENDOR_ID_OFFSET));
> DeviceID = PciSegmentRead16 (PCI_SEGMENT_LIB_ADDRESS(Segment, Bus, Device, Function, PCI_DEVICE_ID_OFFSET));
> if (VendorID == 0xFFFF && DeviceID == 0xFFFF) {
> + if (Function == 0) {
> + //
> + // If function 0 is not implemented, do not scan other functions.
> + //
> + break;
> + }
> continue;
> }
>
>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
--
Thanks,
Ray
next prev parent reply other threads:[~2018-09-13 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 2:10 [PATCH] IntelSiliconPkg IntelVTdDxe: Optimize when func 0 is not implemented Star Zeng
2018-09-13 3:10 ` Ni, Ruiyu [this message]
2018-09-13 5:28 ` Yao, Jiewen
2018-09-13 6:29 ` Zeng, Star
2018-09-13 6:42 ` Yao, Jiewen
2018-09-13 10:27 ` Zeng, Star
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=7a0c6bc9-eb4d-6e84-8bd1-fac8bab6e1ed@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