From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from esa4.dell-outbound.iphmx.com (esa4.dell-outbound.iphmx.com [68.232.149.214]) (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 0892921A0912C for ; Thu, 18 May 2017 08:25:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1495121122; x=1526657122; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=msr+k0fcaa//ScrdX5ajKVtwa1ByfyxHwji9odc/yJE=; b=A4lMg63gafVCliBiU1ZCuOcNqcYrsOToZSgLLBtXU9byinkLGc/GmkqN 13P8aiVrChL8qWDhVU1h8vd0xJkRqMfBYB+nazHeu3Sj7esGHjansnjY4 CI9VUFXyeCfM7DkMweqEW8ifckIp4s9/OXYYauJxC6GbgWx4E/Cf2Bthh Y=; Received: from esa3.dell-outbound2.iphmx.com ([68.232.154.63]) by esa4.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2017 10:25:22 -0500 From: Received: from ausxippc110.us.dell.com ([143.166.85.200]) by esa3.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2017 21:23:03 +0600 X-LoopCount0: from 10.170.28.39 X-IronPort-AV: E=Sophos;i="5.38,359,1491282000"; d="scan'208";a="508227345" To: CC: Thread-Topic: [edk2] SMBios configuration table not present until late stage of boot Thread-Index: AQHSz+ehEWck5aHbMEO/S5aTA4VLW6H6MF/AgABWWYD//6zRkA== Date: Thu, 18 May 2017 15:25:20 +0000 Message-ID: <800d8d0d8b4841eaa43d75d0939b6521@ausx13mps335.AMER.DELL.COM> References: <1548dc48-890d-29e0-0bdc-5df3ce545e5b@solarflare.com> <83202bed-050e-cf5d-a3f3-13b8a83ad739@solarflare.com> In-Reply-To: <83202bed-050e-cf5d-a3f3-13b8a83ad739@solarflare.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titusconfig: No Restrictions 04051212 x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvIiwiaWQiOiJiMjdhZDg0Zi00OTNlLTQyZDktOWE0Ni01NGExYzhhNzNiZjIiLCJwcm9wcyI6W3sibiI6IkNsYXNzaWZpY2F0aW9uIiwidmFscyI6W3sidmFsdWUiOiJObyBSZXN0cmljdGlvbnMifV19LHsibiI6IlN1YmxhYmVscyIsInZhbHMiOltdfSx7Im4iOiJFeHRlcm5hbENvcnJlc3BvbmRlbmNlIiwidmFscyI6W119XX0sIlN1YmplY3RMYWJlbHMiOltdLCJUTUNWZXJzaW9uIjoiMTYuMi4xMS4wIiwiVHJ1c3RlZExhYmVsSGFzaCI6InFpT0U0cnhaWkFFeXRPajBjQ3lPRFp4VStBdkMrXC8xTnd1RjdnVWNLZnFnPSJ9 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.143.242.75] MIME-Version: 1.0 Subject: Re: SMBios configuration table not present until late stage of boot 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: Thu, 18 May 2017 15:25:23 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable It is a tricky problem. What I would like is for a new protocol to be defined, which should not rely on devices, to contain certain identifying information like this that would be useful to device drivers. It could be created early in DXE. What I fear is some future requirement that SMBIOS be made available at some definitive time pre-OS boot. You may have to get support from the BIOS vendor. If you are doing a driver for a particular system, that might not be too bad of a solution; but if you're trying to develop some generic driver, I don't have a good suggestion. Regards, Jim -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Toma= s Pilar (tpilar) Sent: Thursday, May 18, 2017 10:14 AM To: Dailey, Jim Cc: edk2-devel@lists.01.org Subject: Re: [edk2] SMBios configuration table not present until late stage= of boot This does make sense. Do you have a suggestion how I would go about=20 finding/creating a unique identifier for the system during preboot? Cheers, Tom On 18/05/17 16:11, Jim.Dailey@dell.com wrote: > Not a helpful comment, but I wanted to air my feelings on the topic: > > I view SMBIOS as data strictly for OS-level consumption and not for > any pre-boot code. I'm sure I'm in the minority, however. > > One of the problems is that the BIOS needs to have scanned all > devices/resources and perhaps executed a connect all before the > tables can be generated (or at least completed). > > Regards, > Jim > > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of To= mas Pilar (tpilar) > Sent: Thursday, May 18, 2017 10:01 AM > To: edk2-devel@lists.01.org > Subject: [edk2] SMBios configuration table not present until late stage o= f boot > > Hi, > > I am trying to read the system UUID from the System Table (Type 1) in > the SMBios set of tables. I am doing this during DriverBinding.Start() > part of the UEFI_DRIVER initialisation. Unfortunately the > gST->ConfigurationTable only contains 6 tables and SMBios is not one of > them. > > Once I boot into UEFI shell or start a PXE booting process, the > gST->ConfigurationTable now contains 8 tables and SMBios is one of the > two new tables. If I however only boot to a HDD, this never seems to > happen. > > Can someone offer some insight why this might be so and how would I go > about forcing the platform to provide the SMBios in > gST->ConfigurationTable at a sensible point? > > Incidentally it seems ExitBootServices is not signaled on this platform > if the boot goes through to HDD either, which is another strange thing ..= . > > Cheers, > Tom > > > > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel