From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.136, mailfrom: isaac.w.oram@intel.com) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by groups.io with SMTP; Thu, 13 Jun 2019 17:55:02 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jun 2019 17:55:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,371,1557212400"; d="scan'208,217";a="184804258" Received: from orsmsx104.amr.corp.intel.com ([10.22.225.131]) by fmsmga002.fm.intel.com with ESMTP; 13 Jun 2019 17:55:01 -0700 Received: from orsmsx123.amr.corp.intel.com (10.22.240.116) by ORSMSX104.amr.corp.intel.com (10.22.225.131) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 13 Jun 2019 17:55:01 -0700 Received: from orsmsx116.amr.corp.intel.com ([169.254.7.166]) by ORSMSX123.amr.corp.intel.com ([169.254.1.55]) with mapi id 14.03.0415.000; Thu, 13 Jun 2019 17:55:01 -0700 From: "Oram, Isaac W" To: "Gao, Liming" , "Yao, Jiewen" , "Dong, Eric" , "devel@edk2.groups.io" , "Kinney, Michael D" Subject: Re: [RFC][edk2-platform][Add new packages in Platform\Intel directory] Thread-Topic: [RFC][edk2-platform][Add new packages in Platform\Intel directory] Thread-Index: AQHVF4VesjHIV4fYq02QttUGV8OTt6aE3T9w//983wCABLxhoIAAeBKAgAAFGICAAALWAIABJ2XggA3NXgCAAdhn0A== Date: Fri, 14 Jun 2019 00:55:00 +0000 Message-ID: <3155A53C14BABF45A364D10949B7414C9711DB1B@ORSMSX116.amr.corp.intel.com> References: <74D8A39837DF1E4DA445A8C0B3885C503F67FA7A@shsmsx102.ccr.corp.intel.com> <74D8A39837DF1E4DA445A8C0B3885C503F67FB10@shsmsx102.ccr.corp.intel.com> <74D8A39837DF1E4DA445A8C0B3885C503F686731@shsmsx102.ccr.corp.intel.com> <74D8A39837DF1E4DA445A8C0B3885C503F6867EA@shsmsx102.ccr.corp.intel.com> <3155A53C14BABF45A364D10949B7414C970FE0D0@ORSMSX116.amr.corp.intel.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E47DC8E@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E47DC8E@SHSMSX104.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-reaction: no-action dlp-version: 11.0.600.7 x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Return-Path: isaac.w.oram@intel.com Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3155A53C14BABF45A364D10949B7414C9711DB1BORSMSX116amrcor_" --_000_3155A53C14BABF45A364D10949B7414C9711DB1BORSMSX116amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This looks good to me. I would suggest that we also capture an overview of= the organization and the targeted contents of the different packages in th= e Platform/Intel/Readme.md or maybe a wiki page. Thanks, Isaac From: Gao, Liming Sent: Wednesday, June 12, 2019 6:27 AM To: Oram, Isaac W ; Yao, Jiewen ; Dong, Eric ; devel@edk2.groups.io; Kinney, Michae= l D Cc: Gao, Liming Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] Isaac and Eric: Here is the proposal for new packages in Platform\Intel directory. BoardModulePkg: This package includes the libraries shared between the diff= erent board packages. Those libraries are linked by the drivers in the boar= d packages. DebugFeaturePkg: This package provides the debug features, such as debug li= brary, debug method. ManageabilityFeaturePkg: This package provides the system management driver= , such as Ipmi, Smbios. DeviceFeaturePkg: This package provides the different device support, such = as SIO controller, Network. UserInterfaceFeaturePkg: This package provides UI related modules, such as = Logo, Setup page. Thanks Liming From: Oram, Isaac W Sent: Tuesday, June 4, 2019 4:25 PM To: Yao, Jiewen >; Dong, = Eric >; devel@edk2.groups.i= o; Gao, Liming >; Kinney, Michael D > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] Eric, I have envisioned less granular packages for advanced features. One of the= goals for MinPlatform is to improve usability during porting. The idea is= that you would do basic board porting with minimal effort to get your syst= em functional. Then you would enable additional features by adding collect= ions of features to your baseline. Then as a last step optimize out unnece= ssary things. This is something like a functionality oriented porting appr= oach. Get all the functionality you need by building up, then optimize out= . I would characterize Intel's traditional reference platforms as having e= verything and then adding and removing from a starting point that was very = feature rich. The challenge we seemed to face was that it was hard to remo= ve things with the feature rich starting point. As an example of functionality oriented porting, say that I set up my basic= server port by starting with the Purley open board package. I port it to = my motherboard, then I check out my baseline functionality. Then I add man= ageability features by including DSC/FDF from the ManageabilityFeaturePkg t= hat add FV to my MinPlatform port. And I repeat for other sets of features= until I get all of the features that I need. Then I optimize: for size, s= peed, to reduce complexity, and so on. It would be best if this optimizati= on were tool assisted to a great degree, e.g a more sophisticated FMMT that= lets one cut out extra components. My concern is that if we allow very specific feature packages, like the Use= rAuthenticationPkg, we are very much like today. Yes, you can select any d= rivers you need and add to your DSC/FDF. But that is very quickly overwhel= ming. There are hundreds of drivers and what they require is often complex= to determine. Thus we tend to copy something else and customize it. This= tends to lead to lots of technical debt and complexity. I am thinking that we should target something like 10-20 advanced feature p= ackages that produce one or two (if features have pre-memory components) FV= with a set of features and simpler dependencies. We are just in the early= stages of defining what this would look like, and our thinking is evolving= . We have identified Manageability and Debug as feature collections. I th= ink that there is one for adding USB, network, Bluetooth and such periphera= l support. I think setup browser and UI stuff will go somewhere. We can m= ine a few reference platforms for data. Let's discuss this in person and make a proposal for organization for featu= re packages and the rules for what goes where. We can add this proposal to= your RFC and I think that will help guide the future development of the Pl= atform\Intel contents. Regards, Isaac From: Yao, Jiewen Sent: Monday, June 3, 2019 9:03 AM To: Dong, Eric >; devel@edk= 2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] Since there is no other module, I think we can use this specific package na= me to tell people what it is. It is also good for feature isolation. Thank you Yao Jiewen From: Dong, Eric Sent: Monday, June 3, 2019 8:53 AM To: Yao, Jiewen >; devel@= edk2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] Hi Jiewen, So far, I don't have other modules which need to move to this package. I think UserAuthenticationPkg is too specific, but if others also agree wit= h this name, I'm ok too. Hi liming, Isaac & Mike, Any comments about the new package name? Thanks, Eric From: Yao, Jiewen Sent: Monday, June 3, 2019 8:35 AM To: Dong, Eric >; devel@edk= 2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D > Cc: Yao, Jiewen > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] OK. Do you have any other modules what could be potentially in this package= ? I think another option is to name it UserAuthenticationPkg, just like Signe= dCapsulePkg. Thank you Yao Jiewen From: Dong, Eric Sent: Monday, June 3, 2019 8:28 AM To: Yao, Jiewen >; devel@= edk2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] I think sample means this is an example about how to enable this feature. C= ode implemented with production quality. Platform can decide whether to use= it or not. Thanks, Eric From: Yao, Jiewen Sent: Friday, May 31, 2019 4:06 PM To: Dong, Eric >; devel@edk= 2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] Would you please clarify what "sample" here really means? Not for productio= n? Or something else? Thank you Yao Jiewen From: Dong, Eric Sent: Friday, May 31, 2019 4:02 PM To: Yao, Jiewen >; devel@= edk2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] Hi Jiewen, I think SecuritySamplePkg used to save 1) sample implementation for securit= y related features, 2) it's platform scope feature. SecurityPkg used to save 1) common security features, 2) It's not a sample = implementation. This is just my proposal, If you have better one, you can raise here. Thanks, Eric From: Yao, Jiewen Sent: Friday, May 31, 2019 3:49 PM To: Dong, Eric >; devel@edk= 2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D > Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel direct= ory] Would you please clarify the position of SecuritySamplePkg ? What is the difference between SecurityPkg and SecuritySamplePkg ? Thank you Yao Jiewen From: Dong, Eric Sent: Friday, May 31, 2019 3:46 PM To: devel@edk2.groups.io; Gao, Liming >; Kubacki, Michael A >; Oram, Isaac W >; Kinney, Michael D >; Yao, Jiewen > Subject: [RFC][edk2-platform][Add new packages in Platform\Intel directory] Isaac, Jiewen & Mike, I plan to add a new driver named UserAuthentication. This driver shows a sa= mple implementation about how to control user enter setup page. I plan to a= dd a new package in Platform\Intel folder to save this driver. New package = name is SecuritySamplePkg. Any comments for this RFC? Thanks, Eric _._,_._,_ --_000_3155A53C14BABF45A364D10949B7414C9711DB1BORSMSX116amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This looks good to me.  I would suggest that we= also capture an overview of the organization and the targeted contents of = the different packages in the Platform/Intel/Readme.md or maybe a wiki page= .

 

Thanks,
Isaac

 

From: Gao, Liming
Sent: Wednesday, June 12, 2019 6:27 AM
To: Oram, Isaac W <isaac.w.oram@intel.com>; Yao, Jiewen <ji= ewen.yao@intel.com>; Dong, Eric <eric.dong@intel.com>; devel@edk2.= groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
Cc: Gao, Liming <liming.gao@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

 

Isaac and Eric:

  Here is the proposal for new packages in Platf= orm\Intel directory.

 

BoardModulePkg: This package includes the libraries s= hared between the different board packages. Those libraries are linked by t= he drivers in the board packages.

DebugFeaturePkg: This package provides the debug feat= ures, such as debug library, debug method.

ManageabilityFeaturePkg: This package provides the sy= stem management driver, such as Ipmi, Smbios.

DeviceFeaturePkg: This package provides the different= device support, such as SIO controller, Network.

UserInterfaceFeaturePkg: This package provides UI rel= ated modules, such as Logo, Setup page.

 

Thanks

Liming

From: Oram, Isaac W
Sent: Tuesday, June 4, 2019 4:25 PM
To: Yao, Jiewen <jiewen.y= ao@intel.com>; Dong, Eric <eric.dong@intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kinney, Michael D <micha= el.d.kinney@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

Eric,

&nbs= p;

I have en= visioned less granular packages for advanced features.  One of the goa= ls for MinPlatform is to improve usability during porting.  The idea i= s that you would do basic board porting with minimal effort to get your system functional.  Then you would enable addition= al features by adding collections of features to your baseline.  Then = as a last step optimize out unnecessary things.  This is something lik= e a functionality oriented porting approach.  Get all the functionality you need by building up, then optimize out.  I = would characterize Intel’s traditional reference platforms as having = everything and then adding and removing from a starting point that was very= feature rich.  The challenge we seemed to face was that it was hard to remove things with the feature rich starting = point.

&nbs= p;

As an exa= mple of functionality oriented porting, say that I set up my basic server p= ort by starting with the Purley open board package.  I port it to my m= otherboard, then I check out my baseline functionality.  Then I add manageability features by including DSC/FD= F from the ManageabilityFeaturePkg that add FV to my MinPlatform port. = ; And I repeat for other sets of features until I get all of the features t= hat I need.  Then I optimize: for size, speed, to reduce complexity, and so on.  It would be best if this optimizati= on were tool assisted to a great degree, e.g a more sophisticated FMMT that= lets one cut out extra components.

&nbs= p;

My concer= n is that if we allow very specific feature packages, like the UserAuthenti= cationPkg, we are very much like today.  Yes, you can select any drive= rs you need and add to your DSC/FDF.  But that is very quickly overwhelming.  There are hundreds of drivers and= what they require is often complex to determine.  Thus we tend to cop= y something else and customize it.  This tends to lead to lots of tech= nical debt and complexity.

&nbs= p;

I am thin= king that we should target something like 10-20 advanced feature packages t= hat produce one or two (if features have pre-memory components) FV with a s= et of features and simpler dependencies.  We are just in the early stages of defining what this would look like, and= our thinking is evolving.  We have identified Manageability and Debug= as feature collections.  I think that there is one for adding USB, ne= twork, Bluetooth and such peripheral support.  I think setup browser and UI stuff will go somewhere.  We can mine a = few reference platforms for data.

&nbs= p;

Let’= ;s discuss this in person and make a proposal for organization for feature = packages and the rules for what goes where.  We can add this proposal = to your RFC and I think that will help guide the future development of the Platform\Intel contents.

&nbs= p;

Regards,<= o:p>

Isaac

&nbs= p;

&nbs= p;

From:<= /span> Yao, Jiewen
Sent: Monday, June 3, 2019 9:03 AM
To: Dong, Eric <eric.dong@= intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kubacki, Michael A <mic= hael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Kinney, Michael D <michae= l.d.kinney@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

Since there is no other module, I think we can use th= is specific package name to tell people what it is.

It is also good for feature isolation.

 

Thank you

Yao Jiewen

 

From:<= /span> Dong, Eric
Sent: Monday, June 3, 2019 8:53 AM
To: Yao, Jiewen <jiewen.y= ao@intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kubacki, Michael A <mic= hael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Kinney, Michael D <michae= l.d.kinney@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

Hi Jiewen,

 

So far, I don’t have other modules which need to move to this pa= ckage.

 

I think UserAuthenticationPkg is too = specific, but if others also agree with this name, I’m ok too.=

 

 

Hi liming, Isaac & Mike,

 

Any comments about the new package name?

 

Thanks,

Eric

From:<= /span> Yao, Jiewen
Sent: Monday, June 3, 2019 8:35 AM
To: Dong, Eric <eric.dong@= intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kubacki, Michael A <mic= hael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Kinney, Michael D <michae= l.d.kinney@intel.com>
Cc: Yao, Jiewen <jiewen.y= ao@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

OK. Do you have any other modules what could be poten= tially in this package?

 

I think another option is to name it UserAuthenticationPkg, just like SignedCapsulePkg.=

 

Thank you

Yao Jiewen

 

From:<= /span> Dong, Eric
Sent: Monday, June 3, 2019 8:28 AM
To: Yao, Jiewen <jiewen.y= ao@intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kubacki, Michael A <mic= hael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Kinney, Michael D <michae= l.d.kinney@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

I think sample means this is an example about how to enable this featu= re. Code implemented with production quality. Platform can decide whether t= o use it or not.

 

Thanks,

Eric

From:<= /span> Yao, Jiewen
Sent: Friday, May 31, 2019 4:06 PM
To: Dong, Eric <eric.dong@= intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kubacki, Michael A <mic= hael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Kinney, Michael D <michae= l.d.kinney@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

Would you please clarify what “sample” he= re really means? Not for production? Or something else?

 

Thank you

Yao Jiewen

 

 

From:<= /span> Dong, Eric
Sent: Friday, May 31, 2019 4:02 PM
To: Yao, Jiewen <jiewen.y= ao@intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kubacki, Michael A <mic= hael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Kinney, Michael D <michae= l.d.kinney@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

Hi Jiewen,

 

I think SecuritySamplePkg used to save 1) sample implementation for se= curity related features, 2) it’s platform scope feature.

SecurityPkg used to save 1) common security features, 2) It’s no= t a sample implementation.

 

This is just my proposal, If you have better one, you can raise here.<= o:p>

 

Thanks,

Eric

From:<= /span> Yao, Jiewen
Sent: Friday, May 31, 2019 3:49 PM
To: Dong, Eric <eric.dong@= intel.com>; devel@edk2.groups.io; Gao, Limi= ng <liming.gao@intel.com>= ; Kubacki, Michael A <mic= hael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.com>; Kinney, Michael D <michae= l.d.kinney@intel.com>
Subject: RE: [RFC][edk2-platform][Add new packages in Platform\Intel= directory]

&nbs= p;

Would you please clarify the position of SecuritySam= plePkg ?

 

What is the difference between SecurityPkg and SecuritySamplePkg ?

 

Thank you

Yao Jiewen

 

From:<= /span> Dong, Eric
Sent: Friday, May 31, 2019 3:46 PM
To: devel@edk2.groups.io= ; Gao, Liming <liming.gao@intel.= com>; Kubacki, Michael A <michael.a.kubacki@intel.com>; Oram, Isaac W <isaac.w.oram@intel.c= om>; Kinney, Michael D <michael.d.kinney@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>
Subject: [RFC][edk2-platform][Add new packages in Platform\Intel dir= ectory]

&nbs= p;

Isaac, Jiewen & Mike,

&nbs= p;

I plan to add a new driver named UserAuthentication. This driver shows= a sample implementation about how to control user enter setup page. I plan= to add a new package in Platform\Intel folder to save this driver. New package name is SecuritySamplePkg. Any com= ments for this RFC?<= /o:p>

 

Thanks,

Eric

_._,_._,_=

--_000_3155A53C14BABF45A364D10949B7414C9711DB1BORSMSX116amrcor_--