Re: [meta-intel] [PATCH 1/1] README: Documentation of hardware features
On Thu, 2014-10-02 at 14:14 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Starting a new documentation section to describe the layer specific hardware features. At this point the intel-ucode machine feature is described here. In the future more such features will be described in this section. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- README | 75 ++ 1 file changed, 75 insertions(+) diff --git a/README b/README index c829fdb..f633f36 100644 --- a/README +++ b/README @@ -83,3 +83,78 @@ The meta-intel maintainers will do their best to review and/or pull in a patch or patchset within 24 hours of the time it was posted. For larger and/or more involved patches and patchsets, the review process may take longer. + + +Machine Features in the meta-intel layer + + +Many machine features are available in the oecore/poky layer for BSP use. +The meta-intel layer makes some additional machine features available for BSPs +using the meta-intel layer. + +Requirements + + +The additional machine features are only available when the meta-intel layer +is included in the build config, and the meta-intel.inc file is included in +the machine configuration of the interested BSP. + +To make these features available for your machine, you will need to: + +1. have a configuration line as seen below in the bblayers.conf + BBLAYERS += local path/meta-intel.git +2. have the following line in the machine configuration + require conf/machine/include/meta-intel.inc + +Once the above requirements are met, then the machine features provided by +the meta-intel layer will be available for the BSP use. + +Available Machine Features +-- + +As of now the meta-intel layer provides the following list of machine features. +In the future, more machine features may be available in this list. + +* intel-ucode + +These machine features can be included by listing them in the MACHINE_FEATURES +variable in the machine configuration file. + +Details of the Machine Features +--- + +* intel-ucode: This feature provides microcode updating support for Intel + processors. With the intel-ucode feature, images get complete support for + updating the microcode on Intel processors. This feature enables microcode + updating at early boot time by placing the microcode data files in the + initrd image. It also puts the user land microcode updating tool iucode_tool + and the microcode data file in the target images. + + Q. Why to enable this microcode feature? + A. Intel releases microcode updates to correct processor behavior as + documented in the respective processor specification updates. While + the regular approach to getting this microcode update is via a BIOS + upgrade, this can be an administrative hassle and not always possible + in the field. The intel-ucode feature enables the microcode update + capability from the Linux OS. It provides an easy path for upgrading + processor microcode without need of changing BIOS. Once the feature + is enabled, it is also possible to update the existing images with + newer microcode update in the future. + + Q. How to bundle only specific microcodes in the target image? + A. The Intel microcode data file released by Intel contains microcode + updates for multiple processors. If the BSP image will be running only + on a certain kind of processors, then the number of microcodes bundled in + the target image can be filtered by specifying the UCODE_FILTER_SIGNATURES + variable. A sequence of iucode-tool parameters are listed in the + UCODE_FILTER_SIGNATURES variable to filter the microcodes from the + microcode data file. For more information on these parameters refer to + the iucode-tool manual page, which can be seen over here: + http://manned.org/iucode-tool + I took a quick look at the iucode-tool manpage, but didn't see anything describing the signatures themselves or where to find them. It would be helpful to the user of this feature to have some idea of where to look to find them. Could you perhaps add a bit about that? Thanks, Tom + Q. When to not enable this microcode feature? + A. The microcode datafile and the associated tools take small (few KB) + space on the target image. The BSPs which are highly sensitive to the + target image size, which are not experiencing any microcode related issues, + may consider not enabling this feature to save the target image foot print. + -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 1/1] README: Documentation of hardware features
On 10/3/14, 7:26 AM, Zanussi, Tom tom.zanu...@intel.com wrote: On Thu, 2014-10-02 at 14:14 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Starting a new documentation section to describe the layer specific hardware features. At this point the intel-ucode machine feature is described here. In the future more such features will be described in this section. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- README | 75 ++ 1 file changed, 75 insertions(+) diff --git a/README b/README index c829fdb..f633f36 100644 --- a/README +++ b/README @@ -83,3 +83,78 @@ The meta-intel maintainers will do their best to review and/or pull in a patch or patchset within 24 hours of the time it was posted. For larger and/or more involved patches and patchsets, the review process may take longer. + + +Machine Features in the meta-intel layer + + +Many machine features are available in the oecore/poky layer for BSP use. +The meta-intel layer makes some additional machine features available for BSPs +using the meta-intel layer. + +Requirements + + +The additional machine features are only available when the meta-intel layer +is included in the build config, and the meta-intel.inc file is included in +the machine configuration of the interested BSP. + +To make these features available for your machine, you will need to: + +1. have a configuration line as seen below in the bblayers.conf +BBLAYERS += local path/meta-intel.git +2. have the following line in the machine configuration +require conf/machine/include/meta-intel.inc + +Once the above requirements are met, then the machine features provided by +the meta-intel layer will be available for the BSP use. + +Available Machine Features +-- + +As of now the meta-intel layer provides the following list of machine features. +In the future, more machine features may be available in this list. + +* intel-ucode + +These machine features can be included by listing them in the MACHINE_FEATURES +variable in the machine configuration file. + +Details of the Machine Features +--- + +* intel-ucode: This feature provides microcode updating support for Intel + processors. With the intel-ucode feature, images get complete support for + updating the microcode on Intel processors. This feature enables microcode + updating at early boot time by placing the microcode data files in the + initrd image. It also puts the user land microcode updating tool iucode_tool + and the microcode data file in the target images. + + Q. Why to enable this microcode feature? + A. Intel releases microcode updates to correct processor behavior as + documented in the respective processor specification updates. While + the regular approach to getting this microcode update is via a BIOS + upgrade, this can be an administrative hassle and not always possible + in the field. The intel-ucode feature enables the microcode update + capability from the Linux OS. It provides an easy path for upgrading + processor microcode without need of changing BIOS. Once the feature + is enabled, it is also possible to update the existing images with + newer microcode update in the future. + + Q. How to bundle only specific microcodes in the target image? + A. The Intel microcode data file released by Intel contains microcode + updates for multiple processors. If the BSP image will be running only + on a certain kind of processors, then the number of microcodes bundled in + the target image can be filtered by specifying the UCODE_FILTER_SIGNATURES + variable. A sequence of iucode-tool parameters are listed in the + UCODE_FILTER_SIGNATURES variable to filter the microcodes from the + microcode data file. For more information on these parameters refer to + the iucode-tool manual page, which can be seen over here: + http://manned.org/iucode-tool + I took a quick look at the iucode-tool manpage, but didn't see anything describing the signatures themselves or where to find them. It would be helpful to the user of this feature to have some idea of where to look to find them. Could you perhaps add a bit about that? Sure, this would help. Nitin Thanks, Tom + Q. When to not enable this microcode feature? + A. The microcode datafile and the associated tools take small (few KB) + space on the target image. The BSPs which are highly sensitive to the + target image size, which are not experiencing any microcode related issues, + may consider not enabling this feature to save the target image foot print. + -- ___ meta-intel mailing list meta-intel@yoctoproject.org
Re: [meta-intel] [PATCH 1/1] README: Documentation of hardware features
Hi Nitin, On Friday 03 October 2014 16:33:28 Kamble, Nitin A wrote: On 10/3/14, 4:15 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Thursday 02 October 2014 14:14:41 nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Starting a new documentation section to describe the layer specific hardware features. At this point the intel-ucode machine feature is described here. In the future more such features will be described in this section. This looks fine to me, thanks for revising it. Speaking of the feature itself, I do wonder if going forward whether only a MACHINE_FEATURES item is the best way to control this though - particularly if the decision to include it or not is about image size or policy, users may want to be able to control it at the distro or image level, and MACHINE_FEATURES is not meant to be changed outside of the machine configuration. Perhaps we can revisit this in 1.8? (I regret that I didn't take the opportunity to get involved with this earlier, my apologies.) Paul, Thanks for the response. To me it feels best to leave it to machine configuration space. Handling from image or distro configuration space does not seem right. If the machine need/can use updated microcode then that reason is valid for all kinds of distro or image configurations. It is very processor specific decision, and it is best handled in the machine configuration. You yourself stated: The BSPs which are highly sensitive to the target image size, which are not experiencing any microcode related issues, may consider not enabling this feature to save the target image foot print. However, it's not really the BSP that is sensitive to the target image size, for a lot of cases it's going to be dependent on how the device is to be used (what storage is going to be used for the image, how large I want my image to be, etc.) We may supply a BSP for a device where microcode updates are available and can be applied, but that doesn't mean that all usages of that device need or want to include the microcode update functionality. Hence to my mind it ought to be able to be controlled independently of the BSP. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 1/1] README: Documentation of hardware features
On 10/3/14, 9:57 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: Hi Nitin, On Friday 03 October 2014 16:33:28 Kamble, Nitin A wrote: On 10/3/14, 4:15 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Thursday 02 October 2014 14:14:41 nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Starting a new documentation section to describe the layer specific hardware features. At this point the intel-ucode machine feature is described here. In the future more such features will be described in this section. This looks fine to me, thanks for revising it. Speaking of the feature itself, I do wonder if going forward whether only a MACHINE_FEATURES item is the best way to control this though - particularly if the decision to include it or not is about image size or policy, users may want to be able to control it at the distro or image level, and MACHINE_FEATURES is not meant to be changed outside of the machine configuration. Perhaps we can revisit this in 1.8? (I regret that I didn't take the opportunity to get involved with this earlier, my apologies.) Paul, Thanks for the response. To me it feels best to leave it to machine configuration space. Handling from image or distro configuration space does not seem right. If the machine need/can use updated microcode then that reason is valid for all kinds of distro or image configurations. It is very processor specific decision, and it is best handled in the machine configuration. You yourself stated: The BSPs which are highly sensitive to the target image size, which are not experiencing any microcode related issues, may consider not enabling this feature to save the target image foot print. However, it's not really the BSP that is sensitive to the target image size, for a lot of cases it's going to be dependent on how the device is to be used (what storage is going to be used for the image, how large I want my image to be, etc.) We may supply a BSP for a device where microcode updates are available and can be applied, but that doesn't mean that all usages of that device need or want to include the microcode update functionality. Hence to my mind it ought to be able to be controlled independently of the BSP. I think this can be explained better with an example. For example take a wearable BSP, it would not be building a big image. So the BSP is tied to a restricted size of the image. Sato or SDK kind of images may not make any sense for the BSP. In this case the feature can go in the machine configuration. Ideally it would be nice to have this as a default disabled feature in the poky-tiny distro, but that is not ideal for the non-wearable kind of BSPs. I am not trying to reach any conclusion here, but making sure we have all the information and understanding to make the right decision. I hope all this clarifications would help you in making the distro/image feature decision for microcode. Cheers, Nitin Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
