From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.93; helo=mga11.intel.com; envelope-from=ruiyu.ni@intel.com; receiver=edk2-devel@lists.01.org Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 689C1203B8589 for ; Sun, 27 May 2018 19:56:00 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 May 2018 19:56:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,450,1520924400"; d="scan'208";a="44408157" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga007.jf.intel.com with ESMTP; 27 May 2018 19:55:59 -0700 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 27 May 2018 19:55:59 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by fmsmsx110.amr.corp.intel.com (10.18.116.10) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 27 May 2018 19:55:59 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.87]) by shsmsx102.ccr.corp.intel.com ([169.254.2.134]) with mapi id 14.03.0319.002; Mon, 28 May 2018 10:55:54 +0800 From: "Ni, Ruiyu" To: Laszlo Ersek CC: edk2-devel-01 Thread-Topic: [edk2] PciSegmentInfoLib instances Thread-Index: AQHT8mkEBmp+unsLGEqavNuCAE/7eqREdiuw Date: Mon, 28 May 2018 02:55:53 +0000 Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BD0C8CB@SHSMSX104.ccr.corp.intel.com> References: <110011b4-f9cc-9f8b-53f8-f12cfe7416b2@redhat.com> In-Reply-To: <110011b4-f9cc-9f8b-53f8-f12cfe7416b2@redhat.com> Accept-Language: en-US, zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: PciSegmentInfoLib instances X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 02:56:00 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable No. There is no such instance. My understanding: Segment is just to separate the PCI devices to different groups. Each group of devices use the continuous BUS/IO/MMIO resource. Each group has a BASE PCIE address that can be used to access PCIE configur= ation in MMIO way. So with the above understanding, even a platform which has single segment c= an be implemented as a multiple segments platform. Thanks/Ray > -----Original Message----- > From: edk2-devel On Behalf Of Laszlo > Ersek > Sent: Wednesday, May 23, 2018 3:38 PM > To: Ni, Ruiyu > Cc: edk2-devel-01 > Subject: [edk2] PciSegmentInfoLib instances >=20 > Hi Ray, >=20 > do you know of any open source, non-Null, PciSegmentInfoLib instance? > (Possibly outside of edk2?) >=20 > More precisely, it's not the PciSegmentInfoLib instance itself that's of > particular interest, but the hardware and the platform support code that > offer multiple PCIe segments. >=20 > Thanks > Laszlo > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel