From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mx.groups.io with SMTP id smtpd.web09.7518.1628163895243211937 for ; Thu, 05 Aug 2021 04:44:55 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@intel.onmicrosoft.com header.s=selector2-intel-onmicrosoft-com header.b=SyAaLtYd; spf=pass (domain: intel.com, ip: 134.134.136.65, mailfrom: dandan.bi@intel.com) X-IronPort-AV: E=McAfee;i="6200,9189,10066"; a="214161125" X-IronPort-AV: E=Sophos;i="5.84,296,1620716400"; d="scan'208,217";a="214161125" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Aug 2021 04:44:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.84,296,1620716400"; d="scan'208,217";a="586185217" Received: from fmsmsx601.amr.corp.intel.com ([10.18.126.81]) by fmsmga001.fm.intel.com with ESMTP; 05 Aug 2021 04:44:41 -0700 Received: from fmsmsx607.amr.corp.intel.com (10.18.126.87) by fmsmsx601.amr.corp.intel.com (10.18.126.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10; Thu, 5 Aug 2021 04:44:40 -0700 Received: from fmsmsx603.amr.corp.intel.com (10.18.126.83) by fmsmsx607.amr.corp.intel.com (10.18.126.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10; Thu, 5 Aug 2021 04:44:40 -0700 Received: from fmsedg602.ED.cps.intel.com (10.1.192.136) by fmsmsx603.amr.corp.intel.com (10.18.126.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10 via Frontend Transport; Thu, 5 Aug 2021 04:44:40 -0700 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.176) by edgegateway.intel.com (192.55.55.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2242.10; Thu, 5 Aug 2021 04:44:40 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DrEyxULV0gL1oxN/QQicBLIpYkOeytqhpe3QW/yjEhj0Oga9BJgvYS8NSV8+hyrxevt94kIk2iEbv2wMOBGEViFueJ/zK2SvLMbCZhbyBwoXdAX8XUQo8B542Kkp5aaA7JkOgkKw0RzI7IxKPWQ9Nt/WC71Q5heIjPWLphl0CZoY5g8zL2+rBHzKrWod4shikciEO/tUSRZIfsAmqhbG5xWwXiLf+BmMOGs6WeeZnaR8rY6z3u2E5xdwekFjGUmc8pl7j++0r+RH/eU4sTI2wFJWngGn9q4ReuXaWC7L52Vy1o4ezdZSxiraqXGVlziFYtwUwrBz+NJSebLuX7oxJA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X/FnrT9Zq0yQ6L5WEH1adl68AxwtulKcnK5nU8xHIbc=; b=jpTt3qBDbwzcZvJPEdQWQZHOBPc1BjUS5mVkYvE+9tRcszqAd22MBEAhlKIBMvaGzWFnjtM6bL/tHQMSMdv3vqHGJKwHvVmmaFo/fc4UasbYMFEuIESSOmcVgY9S521rQCm62hulnbf6WK1+JsFkUbudzfvLzA+49ES25fMR+azLuptEILr4fh8aqJSIwKuqTn9nTpUcz9LiBYUCmP2fHwqUyDRLW/6pmv3JAz6YAYxs+1wEqqfzxFVS8vuNGThUxSWa47T8cTtGofZDeq0RBOXE7ItUFnpek3ppDX2+Ix+esAPJB60PbYgb5DP7DIIvrwpfn63zKOEi08gEM/HD2Q== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X/FnrT9Zq0yQ6L5WEH1adl68AxwtulKcnK5nU8xHIbc=; b=SyAaLtYdSBJSXS2Mvk/wB4n7YDRqhltIE+tgv6X1YtWp4BiFKVjuwxTia0miqnp/vDb5hwCh/FuElw4v4yLqRceR5+dRoAEQCOonSLsUsbaVnKZUZHIToa09oEM0kq+GyjIFiIz2DsVMiNPaXSUTDkPJFt9KGsemkVujaeC/BL0= Received: from DM4PR11MB5453.namprd11.prod.outlook.com (2603:10b6:5:398::15) by DM4PR11MB5453.namprd11.prod.outlook.com (2603:10b6:5:398::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4373.18; Thu, 5 Aug 2021 11:44:38 +0000 Received: from DM4PR11MB5453.namprd11.prod.outlook.com ([fe80::38aa:9c52:efcd:4652]) by DM4PR11MB5453.namprd11.prod.outlook.com ([fe80::38aa:9c52:efcd:4652%3]) with mapi id 15.20.4373.026; Thu, 5 Aug 2021 11:44:38 +0000 From: "Dandan Bi" To: "kun.q@outlook.com" , "devel@edk2.groups.io" CC: "Wu, Hao A" , "Wang, Jian J" , gaoliming , "Yao, Jiewen" , "Bi, Dandan" Subject: Is there any use case of FirmwarePerformanceStandaloneMm.inf now? Thread-Topic: Is there any use case of FirmwarePerformanceStandaloneMm.inf now? Thread-Index: AdeJ7OKxbanYfrbbRCmTrRGRw00jcw== Date: Thu, 5 Aug 2021 11:44:38 +0000 Message-ID: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: outlook.com; dkim=none (message not signed) header.d=none;outlook.com; dmarc=none action=none header.from=intel.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 79916f7d-887f-483e-110d-08d958066815 x-ms-traffictypediagnostic: DM4PR11MB5453: x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: JuCd+4QOylkTqBb1o6PFRq/xgrtUOrYgwxuFMla0+OY9EYvOCKkOYCNog9XrF2Buu+LWXJIFxiFhpoYCv5Ka3BA/Nj3UHOT+GZUKeVxeif0GvJ2CR7y/5dXK9OkZC4BGtqh/Qib6zWXiKcXbJLaSxbX+U1EKJp3lb1M+CdJjHMr2EOmM/Ggd6i/trfLQp7crtZwkpT/8y38peh7b91J0jEiAox5mrM9A8pWVUf+41YrPZklwADhcddfSmoOyyi3OdQyXHCXJBL9njP7Lvo2RhUQRIYRo9gJzGhoJd+Nj3lkwYhjTF3lHNwS6uP+NW3J6JdOmtqBPbdRTIlnz2ppGEO3ug9FzqxrRUycUxb4NsrVV5EXdKj9Xw6mpQcdoW0uYT5QZapAPLR74VJFLiJUh20VaENGrPiBqirxJ6nAyCT7NgwyH+tcuvFTd7JAaHj42+V5wZmEO0sIM7vOwhL1SbKaVjVI9kN/0jaloKfSVSb4t88rMTfk795siGINqyLUqkpLLYhvERON6geXeYkLs36gFUZ10IC0Oe5EdzX1jec0Bm0eXg1j9JHagG7z2B6N3ElxFA7Ske2dbNd5nhWJaO33Txgbuoyrz8lV+3O0cl3mf90vIr98CzQ+LKE48rWo7UxfEmSdDbyXmzLKPjTrwvRcO7YtZJwGSJRj9ddxc31bVrVGtR07J0NLa+DCqm5fFzF+acdG221//csympRMD/w== x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DM4PR11MB5453.namprd11.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(366004)(39860400002)(136003)(376002)(346002)(396003)(4326008)(38070700005)(66476007)(7696005)(107886003)(66556008)(86362001)(110136005)(316002)(76116006)(6506007)(66946007)(66446008)(64756008)(55016002)(54906003)(478600001)(71200400001)(33656002)(8936002)(83380400001)(8676002)(5660300002)(122000001)(9686003)(26005)(38100700002)(9326002)(2906002)(52536014)(186003);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?GKeG5HQzTVsQPeQEPcErmpmAfhU+/orYVhTmqqDTUOoMi0IptWHLwuV14lQc?= =?us-ascii?Q?hfM89J9srem2o2SjCiVB0mXcuNnE1b5lZ4ftb2tZTZHRgufXnpk+QtzaL5yI?= =?us-ascii?Q?MX1/8I3aMalCChIzWXPm+5S77UAebfqHP/C47yAzwlAJ9JfBqStEAvRsSORV?= =?us-ascii?Q?ylFD/hOiykQIJWYiScrvav59PmkTvBsd75yW0qLfPsDA17a+lyQTm0ep11xi?= =?us-ascii?Q?G/O1gofwKhPJ48UGJDZqRIUNd30gkmmWrBV6jlno4T6fI1FmeF4FYdXfeKdm?= =?us-ascii?Q?4XpHZsvrhQ+in1QyJaLLvz+RytSPgtvAppC62gsiCrWoSruerM78JgZZnl5f?= =?us-ascii?Q?Pvi7XOMKGiRDYdBRFKA7T/+mosYOFoumciGR+y4NazsCNV5LuGwNevDLL6gM?= =?us-ascii?Q?zNm9XjtQ292mrOmj2ucEafsAfSB2pPpKiXHNeppOCgYl4BMtdjWLPQPR6Bg8?= =?us-ascii?Q?N2Rk7zwEWwleCUJ6COMnRsGAzMlF/gpCeX1ZqjzjOiB0XgwRP1/1Fn/nG1Vi?= =?us-ascii?Q?aDP30qQIOIWfJjQDy2Sl+48SKH6CQz1nEuBW5p73spxjE5J8jLTWVPtvakZD?= =?us-ascii?Q?VKbNJhyWhRyA2fM7Pr2vgKnvhb9v7JH2ijeHQ1fh2C+BZfpcdfmAjR6dseUy?= =?us-ascii?Q?MKsYyi1bd2eVLJDDT9fl/cEuucbhmDKmr5oLHm4AXWMv2mcEtvSsj/Lm2BWL?= =?us-ascii?Q?Tn1ysK6Uq3/wSinxsrvd0afNLT3k1mXwLco9zFmVx9xLfL7PzopAvnBeuuFI?= =?us-ascii?Q?u0NMXC/QgTJjzI/719vC8XxBoygoeiwDQBByyUuJMXkULKjqeWKIse5dP+Ue?= =?us-ascii?Q?pDCed97k/74lO6sWKhtB0/Cwjbb4PHgcfKPU4YN6SnFAl0UzQ2NUQLyvjpfF?= =?us-ascii?Q?LODKJMxjVqqrbDB625DLuhFa/P7rKep4s/ML8vZlQFA9bjDUBTHjzCPdy7Su?= =?us-ascii?Q?r0h2pREcwHpcio6U/qbj0iJKz30x0oGjNDRkaaxaeXr0BFodiFzy8+h+Qaw+?= =?us-ascii?Q?qe+q4XvO82VpG9U99iwhctqm9OJdhvTdQrJKHeEUzlfgGg5hAg/YnpyOEFSi?= =?us-ascii?Q?cEpqjl8g+bn2qK6SEHwJfRGu5MjvGL/4CW0TTcWzV1y6fZY1z0RC0h9DEyH3?= =?us-ascii?Q?+Dt9A7n49t0xtS9B4+v6dA4PmqQGgHnwGwR8KzdMzKSuApoT+hbjgxRMX2ID?= =?us-ascii?Q?Qw7xAHRCKCq+tSl/ggxltnHg+ARThfb89p03044M7sWwG6/YFsHiDbe95VGR?= =?us-ascii?Q?nLxH5wx40GvcXM/NVvlTSviODAkqDV0RmzIFdcE0EaSnwHev5h7bg4yLGYxw?= =?us-ascii?Q?fFk=3D?= MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: DM4PR11MB5453.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 79916f7d-887f-483e-110d-08d958066815 X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Aug 2021 11:44:38.7620 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: PgPVWPEY2P2ftbQneU5ZGmgyzyCuIDIsZX11qUtFbpfaFHcSwWgBhpZjF/ilH8g7LbBi+1kvQuJdcP34Xu8klA== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR11MB5453 Return-Path: dandan.bi@intel.com X-OriginatorOrg: intel.com Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DM4PR11MB5453179A968C2C7F6B425EAAEAF29DM4PR11MB5453namp_" --_000_DM4PR11MB5453179A968C2C7F6B425EAAEAF29DM4PR11MB5453namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Kun, I plan to make some change for FirmwarePerformanceSmm.inf, may also update = the behavior of FirmwarePerformanceStandaloneMm.inf as they are sharing cod= es now. And I saw you are the submitter of this driver. Could you help clarify foll= owing questions ? Thanks in advance. 1. Do you have the use case to leverage FirmwarePerformanceStandaloneMm.= inf to collect Standalone MM performance data now? 2. Do you have any Library/module used by StandaloneMmCore to collect St= andalone MM performance data and report the data to FirmwarePerformanceStan= daloneMm like the SmmCorePerformanceLib used for SMM core? 3. I plan to move some logic from FirmwarePerformanceDataTableSmm to Smm= CorePerformanceLib as below. Do you think is it ok just to remove them from= FirmwarePerformanceStandaloneMm.inf now? If there is not any module to report Standalone MM performance data to Firm= warePerformanceStandaloneMm.inf, I think it should be OK to remove them fro= m FirmwarePerformanceStandaloneMm now. Change: SMM performance data collection now: 1. SmmCorePerformanceLib collect all the performance data in SMM and rep= ort the data to FirmwarePerformanceDataTableSmm through status code. 2. DxeCorePerformanceLib will communicate with FirmwarePerformanceDataTa= bleSmm to get the SMM performance data and allocate performance table to st= ore all the performance data. Now I want to simplify the process to make DxeCorePerformanceLib communicat= e with SmmCorePerformanceLib directly to collect SMM performance data, so F= irmwarePerformanceDataTableSmm don't need to get the SMM performance data f= rom SmmCorePerformanceLib and register SMI handler for the communication wi= th DxeCorePerformanceLib. For FirmwarePerformanceStandaloneMm.inf, just remove this logic if there is= no module to prepare MM performance data to it now. Thanks, Dandan --_000_DM4PR11MB5453179A968C2C7F6B425EAAEAF29DM4PR11MB5453namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Kun,

 

I plan to make some chang= e for FirmwarePerformanceSmm.inf, may also update the behavior of FirmwareP= erformanceStandaloneMm.inf as they are sharing codes now.

And I saw you are the sub= mitter of this driver. Could you help clarify following questions ? Thanks = in advance.

 

  1. Do you have the use case to leverage FirmwarePerformanceStandaloneMm.inf to= collect Standalone MM performance data now?
  2. Do you have any Library/module used by StandaloneMmCore to collect Standalo= ne MM performance data and report the data to FirmwarePerformanceStandalone= Mm like the SmmCorePerformanceLib used for SMM core?
  3. I plan to move some logic from FirmwarePerformanceDataTableSmm to SmmCorePe= rformanceLib as below. Do you think is it ok just to remove them from Firmw= arePerformanceStandaloneMm.inf now?

If there is not a= ny module to report Standalone MM performance data to FirmwarePerformanceSt= andaloneMm.inf, I think it should be OK to remove them from FirmwarePerform= anceStandaloneMm now.

 

 

Change:

SMM performance data collection now:

  1. SmmCorePerformanceLib collect all the performance data in SMM and report th= e data to FirmwarePerformanceDataTableSmm through status code.
  2. DxeCorePerformanceLib will communicate with FirmwarePerformanceDataTableSmm= to get the SMM performance data and allocate performance table to store al= l the performance data.

Now I want to simplify th= e process to make DxeCorePerformanceLib communicate with SmmCorePerformance= Lib directly to collect SMM performance data, so FirmwarePerformanceDataTab= leSmm don’t need to get the SMM performance data from SmmCorePerformanceLib and register SMI handler for the communica= tion with DxeCorePerformanceLib.

For FirmwarePerformanceStandaloneMm.inf, just remove= this logic if there is no module to prepare MM performance data to it now.

 

 

Thanks,

Dandan

--_000_DM4PR11MB5453179A968C2C7F6B425EAAEAF29DM4PR11MB5453namp_--