From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.31; helo=mga06.intel.com; envelope-from=jiewen.yao@intel.com; receiver=edk2-devel@lists.01.org Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (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 ACC1821A1099D for ; Mon, 27 Nov 2017 05:57:03 -0800 (PST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Nov 2017 06:01:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,465,1505804400"; d="scan'208";a="180675381" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga005.fm.intel.com with ESMTP; 27 Nov 2017 06:01:24 -0800 Received: from fmsmsx112.amr.corp.intel.com (10.18.116.6) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 27 Nov 2017 06:01:24 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX112.amr.corp.intel.com (10.18.116.6) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 27 Nov 2017 06:01:24 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.175]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.218]) with mapi id 14.03.0319.002; Mon, 27 Nov 2017 22:01:22 +0800 From: "Yao, Jiewen" To: Amit kumar , "edk2-devel@lists.01.org" Thread-Topic: Unable to Loacte EdkiiIoMmuProtocol. Thread-Index: AQHTZ3GFK3EKnpbf70uEnAvm8Ns/X6MoQX6A Date: Mon, 27 Nov 2017 14:01:22 +0000 Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503AA2E730@shsmsx102.ccr.corp.intel.com> References: In-Reply-To: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDcxZDc4OTctMGJjOC00MWE3LWJiMWUtNzFjNTI2OTY0MThjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJEZHdPV1I5RSt0M3RGZGpDbUpqUStDNDZUM3BZTEZQME0wZm5RdktLaUpibzhFSFNXRHJldmZQTHFoRkl5eHByIn0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: Unable to Loacte EdkiiIoMmuProtocol. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 13:57:03 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You need include a driver to produce gEdkiiIoMmuProtocolGuid. One sample is IntelSiliconPkg\Feature\VTd\IntelVTdDxe Thank you Yao Jiewen > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Am= it > kumar > Sent: Monday, November 27, 2017 7:24 PM > To: edk2-devel@lists.01.org > Subject: [edk2] Unable to Loacte EdkiiIoMmuProtocol. >=20 > Hi. > I am trying to allocate a mem buffer above 4Gb address but the allocation > since i am unable to locate EdkiiIoMmuProtocol. >=20 > Status =3D gBS->LocateProtocol (&gEdkiiIoMmuProtocolGuid, NULL, (VOID > **)&mIoMmuProtocol); > Status =3D mIoMmuProtocol->AllocateBuffer ( > mIoMmuProtocol, > MaxAllocateType, > EfiBootServicesData, > 1, > HostAddress, > EDKII_IOMMU_ATTRIBUTE_DUAL_ADDRESS_CYCLE > ); >=20 >=20 > can somebody tell me the right way to do it. ? >=20 >=20 > Best Regards > Amit Kumar >=20 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel