From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=pass header.i=@nvidia.com header.s=n1 header.b=qNU02sOu; spf=pass (domain: nvidia.com, ip: 216.228.121.65, mailfrom: jbrasen@nvidia.com) Received: from hqemgate16.nvidia.com (hqemgate16.nvidia.com [216.228.121.65]) by groups.io with SMTP; Thu, 23 May 2019 09:55:33 -0700 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Thu, 23 May 2019 09:55:32 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Thu, 23 May 2019 09:55:32 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 23 May 2019 09:55:32 -0700 Received: from HQMAIL112.nvidia.com (172.18.146.18) by HQMAIL105.nvidia.com (172.20.187.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 23 May 2019 16:55:32 +0000 Received: from HQMAIL109.nvidia.com (172.20.187.15) by HQMAIL112.nvidia.com (172.18.146.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 23 May 2019 16:55:32 +0000 Received: from NAM02-CY1-obe.outbound.protection.outlook.com (104.47.37.56) by HQMAIL109.nvidia.com (172.20.187.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 23 May 2019 16:55:32 +0000 Received: from MWHPR12MB1488.namprd12.prod.outlook.com (10.172.55.145) by MWHPR12MB1839.namprd12.prod.outlook.com (10.175.55.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.15; Thu, 23 May 2019 16:55:30 +0000 Received: from MWHPR12MB1488.namprd12.prod.outlook.com ([fe80::e1ab:ec0b:beea:1729]) by MWHPR12MB1488.namprd12.prod.outlook.com ([fe80::e1ab:ec0b:beea:1729%10]) with mapi id 15.20.1922.018; Thu, 23 May 2019 16:55:30 +0000 From: "Jeff Brasen" To: "Jin, Eric" , Supreeth Venkatesh , "devel@edk2.groups.io" Subject: Re: [edk2-test] Location of tests for vendor/edk2 specific protocols Thread-Topic: [edk2-test] Location of tests for vendor/edk2 specific protocols Thread-Index: AdTv7QSRSyGgoloHR2qzBexAPSYdlQBlVvFSAFi2PdADBEPUAASkf+YY Date: Thu, 23 May 2019 16:55:30 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=jbrasen@nvidia.com; x-originating-ip: [216.228.112.22] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 24640145-f160-49ad-bf62-08d6df9f76ff x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020);SRVR:MWHPR12MB1839; x-ms-traffictypediagnostic: MWHPR12MB1839: x-ms-exchange-purlcount: 7 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 00462943DE x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(39860400002)(366004)(346002)(396003)(136003)(376002)(189003)(199004)(52314003)(40434004)(8676002)(6116002)(7736002)(19627405001)(86362001)(486006)(81166006)(3846002)(966005)(26005)(2501003)(105004)(110136005)(11346002)(186003)(76236002)(99286004)(81156014)(53546011)(6506007)(71190400001)(71200400001)(102836004)(74316002)(476003)(446003)(14454004)(8936002)(7696005)(76116006)(66446008)(316002)(66476007)(76176011)(64756008)(66556008)(561944003)(6306002)(54896002)(6246003)(73956011)(236005)(9686003)(91956017)(66946007)(5660300002)(19627235002)(33656002)(66066001)(25786009)(55016002)(68736007)(256004)(14444005)(5024004)(606006)(6436002)(2906002)(229853002)(478600001)(53936002)(52536014);DIR:OUT;SFP:1101;SCL:1;SRVR:MWHPR12MB1839;H:MWHPR12MB1488.namprd12.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;MX:1;A:1; received-spf: None (protection.outlook.com: nvidia.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: QMSBLDkBwbwjumFskW9/wnXE+0KzUrV/LvZmRkDh3lQOQCNylAgNX5FJUhOxCRLefkpYfLje6gWS96sDiGvlTuIxFyB66JhwkvYmacgFuGZ4R3lCQfTMufh/yFAd/tl12V2AB2Z0VfeFo0QMasEJ/EcQLUTJBrsDVzUrzy9AEtilnIBUxW3L1G2nG2P+vB2IPW2G+s6XkN4PBCciYbngGs2xbWBO9aaduvkYgzLeQVnIV6RppkJsvbhPNDQJYgOEIEXpEKSB6CBKLShNLPy2+1gQDavYCE/uTirWExNWURmIQh1OJ0i8iOAXnghIzZMPxPmFknZ/6QHgFpa8ZpG3yzbudL/QoHAPBP+CUzzVlfGQIItidcaTihidpMVXqnQZHU/hpGErGhqQHfBZPNgxIFvwunKDAOykDUSfsjO/9N4= MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 24640145-f160-49ad-bf62-08d6df9f76ff X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2019 16:55:30.7449 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 43083d15-7273-40c1-b7db-39efd9ccc17a X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: jbrasen@nvidia.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR12MB1839 Return-Path: jbrasen@nvidia.com X-OriginatorOrg: Nvidia.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1558630532; bh=zjCeSFDZ4W0fb+OZCDLVvyMsk7m9lZXf0ZvJYLhe52A=; h=X-PGP-Universal:From:To:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:authentication-results:x-originating-ip: x-ms-publictraffictype:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-ms-exchange-purlcount:x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers:x-forefront-prvs: x-forefront-antispam-report:received-spf: x-ms-exchange-senderadcheck:x-microsoft-antispam-message-info: MIME-Version:X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-CrossTenant-mailboxtype: X-MS-Exchange-CrossTenant-userprincipalname: X-MS-Exchange-Transport-CrossTenantHeadersStamped:X-OriginatorOrg: Content-Language:Content-Type; b=qNU02sOucDB801BRkaNz4/9QkDPrKWij5+FbMy6ls7CuAP244l2B4428n4HAy4O9f tYJG4cXJQbrjMX1a+DZMBNpy1/P2AsVoKUbpKjJTRIpH5SGPWgrpDoYzCViOt5FXXL jjlIpLNZcAui+bSJ6nr8KbpiiK5AQjBSUYJT1JwFm3615HxAVythxabWZDlfIgJr/x paoOJAXy6xyeu1eQpx5dT7RjCOf9A/DiYsajqHCsTutvZue3/zkFKkawdAuTh51po2 gupaARGB17z7m/p3Baulq7puNXVz6PQDQmFD4uA8hVdaROYgbH6VfQOCSHrk2AVk68 +U4QSoroSMjPA== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_MWHPR12MB148878DF5EDF95F946F2E80ACB010MWHPR12MB1488namp_" --_000_MWHPR12MB148878DF5EDF95F946F2E80ACB010MWHPR12MB1488namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I finally got around to creating the feature request bug: https://bugzilla.= tianocore.org/show_bug.cgi?id=3D1839 Thanks, Jeff ________________________________ From: Jin, Eric Sent: Monday, April 29, 2019 8:03 PM To: Supreeth Venkatesh; devel@edk2.groups.io; Jeff Brasen Cc: Jin, Eric Subject: RE: [edk2-test] Location of tests for vendor/edk2 specific protoc= ols Hi Jeff, For the test for non-standard or vendor specific protocols, in my initial = idea, I would like to see them on a separate space and can be built with SC= T infrastructure thru description files and build scripts provided by vendo= r. Anyone can fetch the UEFI SCT or other specific test with his/her purpose/= interest in this way easily. BTW, documents or spec link need be provided f= or user to understand test object and contribute test better. Anyway, it is a good start to record the request in Bugzilla Feature Reque= st for further discussion. Best Regards Eric From: Supreeth Venkatesh Sent: Monday, April 15, 2019 1:25 AM To: devel@edk2.groups.io; Jeff Brasen (jbrasen@nvidia.com) Cc: Jin, Eric Subject: RE: [edk2-test] Location of tests for vendor/edk2 specific protoc= ols + Eric Thanks Jeff for bringing this up. As mentioned during our discussion on this topic briefly @ UEFI Plugfest 2= 019, I definitely like to see these non-standard protocol tests become part= of test suite. However, there has been no proposal yet, though there were proposals relat= ed to SBBR (Arm=92s Server Base Boot Requirements). Currently, any new platform tests added have to be added to UEFI SCT descr= iption files and build scripts for it to be included as part of test suite. May I request you to create Bugzilla Feature Request @ https://bugzilla.ti= anocore.org/ under =93edk-test=94 product and =93UEFI-SCT=94 component, as = well expand on how you like this to be implemented? Supreeth From: devel@edk2.groups.io > On Behalf Of Jeff Brasen via Groups.Io Sent: Friday, April 12, 2019 5:53 PM To: devel@edk2.groups.io Subject: [edk2-devel] [edk2-test] Location of tests for vendor/edk2 specif= ic protocols Now that we have the edk2-test repo with the SCT infrastructure, has there= been any thought for where tests that use this for non-standardized protoc= ols should live? My initial thought is along with the protocols in edk2/edk= 2-platforms. For example if you had Silicon/NVIDIA/Include/Procotol/x.h you= would have Silicon/NVIDIA/TestCase/x/ for this. Has there been any thought= s/plans on this? Thanks, Jeff ________________________________ This email message is for the sole use of the intended recipient(s) and ma= y contain confidential information. Any unauthorized review, use, disclosu= re or distribution is prohibited. If you are not the intended recipient, p= lease contact the sender by reply email and destroy all copies of the origi= nal message. ________________________________ IMPORTANT NOTICE: The contents of this email and any attachments are confi= dential and may also be privileged. If you are not the intended recipient, = please notify the sender immediately and do not disclose the contents to an= y other person, use it for any purpose, or store or copy the information in= any medium. Thank you. --_000_MWHPR12MB148878DF5EDF95F946F2E80ACB010MWHPR12MB1488namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
I finally got around to creating the feature request bug: h= ttps://bugzilla.tianocore.org/show_bug.cgi?id=3D1839

Thanks,

Jeff


From: Jin, Eric <eric.j= in@intel.com>
Sent: Monday, April 29, 2019 8:03 PM
To: Supreeth Venkatesh; devel@edk2.groups.io; Jeff Brasen
Cc: Jin, Eric
Subject: RE: [edk2-test] Location of tests for vendor/edk2 specific= protocols
 

Hi Jeff,

 

For the test for non-standard or vendor specific = protocols, in my initial idea, I would like to see them on a separate space= and can be built with SCT infrastructure thru description files and build = scripts provided by vendor.

Anyone can fetch the UEFI SCT or other specific t= est with his/her purpose/interest in this way easily. BTW, documents or spe= c link need be provided for user to understand test object and contribute t= est better.  

 

Anyway, it is a good start to record the request = in Bugzilla Feature Request for further discussion.

 

Best Regards

Eric

 

From: Supreeth Venkatesh <Supreeth.Venk= atesh@arm.com>
Sent: Monday, April 15, 2019 1:25 AM
To: devel@edk2.groups.io; Jeff Brasen (jbrasen@nvidia.com) <jbra= sen@nvidia.com>
Cc: Jin, Eric <eric.jin@intel.com>
Subject: RE: [edk2-test] Location of tests for vendor/edk2 specific= protocols

 

+ Eric

Thanks Jeff for bringing this up.

As mentioned during our discussion on this topic = briefly @ UEFI Plugfest 2019, I definitely like to see these non-standard p= rotocol tests become part of test suite.

However, there has been no proposal yet, though t= here were proposals related to SBBR (Arm=92s Server Base Boot Requirements)= .

 

Currently, any new platform tests added have to b= e added to UEFI SCT description files and build scripts for it to be includ= ed as part of test suite.

May I request you to create Bugzilla Feature Requ= est @ https://bugzilla.tianocore.org/ under =93edk-test=94 product and =93UE= FI-SCT=94 component, as well expand on how you like this to be implemented?=

 

Supreeth

 

 

&nb= sp;

Now that we have the edk2-test repo with the SCT = infrastructure, has there been any thought for where tests that use this fo= r non-standardized protocols should live? My initial thought is along with = the protocols in edk2/edk2-platforms. For example if you had Silicon/NVIDIA/Include/Procotol/x.h you would have= Silicon/NVIDIA/TestCase/x/ for this. Has there been any thoughts/plans on = this?

 

Thanks,
Jeff

 


This email message is for the sole use of the int= ended recipient(s) and may contain confidential information.  Any unau= thorized review, use, disclosure or distribution is prohibited.  If yo= u are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.=


IMPORTANT NOTICE: The contents of this email and = any attachments are confidential and may also be privileged. If you are not= the intended recipient, please notify the sender immediately and do not di= sclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. T= hank you.

--_000_MWHPR12MB148878DF5EDF95F946F2E80ACB010MWHPR12MB1488namp_--