date:20180403

Re: [meta-intel] [meta-dpdk][PATCH v2] dpdk.inc: fix missing numa.h by disabling NUMA options by default

2018-04-03 Thread Belal, Awais

>> Use PACKAGECONFIG to optionally enable the numa option.

Looks good to go now.

BR,
Awais


From: California Sullivan 
Sent: Wednesday, April 4, 2018 2:18 AM
To: meta-intel@yoctoproject.org
Cc: Belal, Awais; California Sullivan
Subject: [meta-dpdk][PATCH v2] dpdk.inc: fix missing numa.h by disabling NUMA 
options by default

Otherwise we get this:

| dpdk-18.02/lib/librte_eal/linuxapp/eal/eal_memory.c:27:10: fatal error: 
numa.h: No such file or directory
|  #include 
|   ^~~~
| compilation terminated.

Use PACKAGECONFIG to optionally enable the numa option.

Signed-off-by: California Sullivan 
---
v2:
  * use correct dependency for numa
  * CONFIG_VHOST_NUMA_ENABLED -> CONFIG_HAVE_NUMA
  * PACKAGECONFIG[libnuma] -> PACKAGECONFIG[numa]

 recipes-extended/dpdk/dpdk.inc | 4 
 1 file changed, 4 insertions(+)

diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index ce4e8bc..0818841 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -29,10 +29,12 @@ COMPATIBLE_HOST_libc-musl_class-target = "null"
 PACKAGECONFIG[dpdk_qat] = ",,virtual/qat"
 PACKAGECONFIG[vhost] = ",,fuse"
 PACKAGECONFIG[libvirt] = ",,libvirt"
+PACKAGECONFIG[numa] = ",,numactl"

 export CONFIG_EXAMPLE_DPDK_QAT = "${@bb.utils.contains('PACKAGECONFIG', 
'dpdk_qat', 'y', 'n', d)}"
 export CONFIG_EXAMPLE_VM_POWER_MANAGER = 
"${@bb.utils.contains('PACKAGECONFIG', 'libvirt', 'y', 'n', d)}"
 export CONFIG_VHOST_ENABLED = "${@bb.utils.contains('PACKAGECONFIG', 'vhost', 
'y', 'n', d)}"
+export CONFIG_HAVE_NUMA = "${@bb.utils.contains('PACKAGECONFIG', 'numa', 'y', 
'n', d)}"

 RDEPENDS_${PN} += "python-subprocess virtual/libibverbs"
 DEPENDS = "virtual/kernel virtual/libibverbs"
@@ -80,6 +82,8 @@ do_configure () {
sed -e 
"s#CONFIG_RTE_KNI_VHOST=n#CONFIG_RTE_KNI_VHOST=${CONFIG_VHOST_ENABLED}#" -i 
${S}/config/common_linuxapp
sed -e 
"s#CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=n#CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=${CONFIG_VHOST_ENABLED}#"
 -i ${S}/config/common_linuxapp
sed -e 
"s#CONFIG_RTE_LIBRTE_VHOST=n#CONFIG_RTE_LIBRTE_VHOST=${CONFIG_VHOST_ENABLED}#" 
-i ${S}/config/common_linuxapp
+   sed -e 
"s#CONFIG_RTE_LIBRTE_VHOST_NUMA=.*#CONFIG_RTE_LIBRTE_VHOST_NUMA=${CONFIG_HAVE_NUMA}#"
 -i ${S}/config/common_linuxapp
+   sed -e 
"s#CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=.*#CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=${CONFIG_HAVE_NUMA}#"
 -i ${S}/config/common_linuxapp

make O=$RTE_TARGET T=$RTE_TARGET config
 }
--
2.14.3

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [meta-dpdk][PATCH] dpdk.inc: fix missing numa.h by disabling NUMA options by default

2018-04-03 Thread Cal Sullivan

Thanks for the feedback. v2 has been sent. Assuming no other issues are 
found I'll merge tomorrow. Apologies for the delays.


Thanks,
Cal

On 04/01/2018 10:37 PM, Belal, Awais wrote:

+PACKAGECONFIG[libnuma] = ",,libnuma"

This dependency should be on 'numactl' which is provided under meta-oe and the 
PACKAGECONFIG should use just numa rather than libnuma IMO.

BR,
Awais


From: California Sullivan 
Sent: Saturday, March 31, 2018 2:29 AM
To: meta-intel@yoctoproject.org
Cc: kexin@windriver.com; Belal, Awais; California Sullivan
Subject: [meta-dpdk][PATCH] dpdk.inc: fix missing numa.h by disabling NUMA 
options by default

Otherwise we get this:

| dpdk-18.02/lib/librte_eal/linuxapp/eal/eal_memory.c:27:10: fatal error: 
numa.h: No such file or directory
|  #include 
|   ^~~~
| compilation terminated.

Signed-off-by: California Sullivan 
---
Based on top of Awais's patch "dpdk: upgrade to 18.02"

  recipes-extended/dpdk/dpdk.inc | 4 
  1 file changed, 4 insertions(+)

diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index ce4e8bc..9affda4 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -29,10 +29,12 @@ COMPATIBLE_HOST_libc-musl_class-target = "null"
  PACKAGECONFIG[dpdk_qat] = ",,virtual/qat"
  PACKAGECONFIG[vhost] = ",,fuse"
  PACKAGECONFIG[libvirt] = ",,libvirt"
+PACKAGECONFIG[libnuma] = ",,libnuma"

  export CONFIG_EXAMPLE_DPDK_QAT = "${@bb.utils.contains('PACKAGECONFIG', 
'dpdk_qat', 'y', 'n', d)}"
  export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@bb.utils.contains('PACKAGECONFIG', 
'libvirt', 'y', 'n', d)}"
  export CONFIG_VHOST_ENABLED = "${@bb.utils.contains('PACKAGECONFIG', 'vhost', 'y', 
'n', d)}"
+export CONFIG_VHOST_NUMA_ENABLED = "${@bb.utils.contains('PACKAGECONFIG', 
'libnuma', 'y', 'n', d)}"

  RDEPENDS_${PN} += "python-subprocess virtual/libibverbs"
  DEPENDS = "virtual/kernel virtual/libibverbs"
@@ -80,6 +82,8 @@ do_configure () {
 sed -e 
"s#CONFIG_RTE_KNI_VHOST=n#CONFIG_RTE_KNI_VHOST=${CONFIG_VHOST_ENABLED}#" -i 
${S}/config/common_linuxapp
 sed -e 
"s#CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=n#CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=${CONFIG_VHOST_ENABLED}#"
 -i ${S}/config/common_linuxapp
 sed -e 
"s#CONFIG_RTE_LIBRTE_VHOST=n#CONFIG_RTE_LIBRTE_VHOST=${CONFIG_VHOST_ENABLED}#" 
-i ${S}/config/common_linuxapp
+   sed -e 
"s#CONFIG_RTE_LIBRTE_VHOST_NUMA=.*#CONFIG_RTE_LIBRTE_VHOST_NUMA=${CONFIG_VHOST_NUMA_ENABLED}#"
 -i ${S}/config/common_linuxapp
+   sed -e 
"s#CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=.*#CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=${CONFIG_VHOST_NUMA_ENABLED}#"
 -i ${S}/config/common_linuxapp

 make O=$RTE_TARGET T=$RTE_TARGET config
  }
--
2.14.3



--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-dpdk][PATCH v2] dpdk.inc: fix missing numa.h by disabling NUMA options by default

2018-04-03 Thread California Sullivan

Otherwise we get this:

| dpdk-18.02/lib/librte_eal/linuxapp/eal/eal_memory.c:27:10: fatal error: 
numa.h: No such file or directory
|  #include 
|   ^~~~
| compilation terminated.

Use PACKAGECONFIG to optionally enable the numa option.

Signed-off-by: California Sullivan 
---
v2:
  * use correct dependency for numa
  * CONFIG_VHOST_NUMA_ENABLED -> CONFIG_HAVE_NUMA
  * PACKAGECONFIG[libnuma] -> PACKAGECONFIG[numa]

 recipes-extended/dpdk/dpdk.inc | 4 
 1 file changed, 4 insertions(+)

diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index ce4e8bc..0818841 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -29,10 +29,12 @@ COMPATIBLE_HOST_libc-musl_class-target = "null"
 PACKAGECONFIG[dpdk_qat] = ",,virtual/qat"
 PACKAGECONFIG[vhost] = ",,fuse"
 PACKAGECONFIG[libvirt] = ",,libvirt"
+PACKAGECONFIG[numa] = ",,numactl"
 
 export CONFIG_EXAMPLE_DPDK_QAT = "${@bb.utils.contains('PACKAGECONFIG', 
'dpdk_qat', 'y', 'n', d)}"
 export CONFIG_EXAMPLE_VM_POWER_MANAGER = 
"${@bb.utils.contains('PACKAGECONFIG', 'libvirt', 'y', 'n', d)}"
 export CONFIG_VHOST_ENABLED = "${@bb.utils.contains('PACKAGECONFIG', 'vhost', 
'y', 'n', d)}"
+export CONFIG_HAVE_NUMA = "${@bb.utils.contains('PACKAGECONFIG', 'numa', 'y', 
'n', d)}"
 
 RDEPENDS_${PN} += "python-subprocess virtual/libibverbs"
 DEPENDS = "virtual/kernel virtual/libibverbs"
@@ -80,6 +82,8 @@ do_configure () {
sed -e 
"s#CONFIG_RTE_KNI_VHOST=n#CONFIG_RTE_KNI_VHOST=${CONFIG_VHOST_ENABLED}#" -i 
${S}/config/common_linuxapp
sed -e 
"s#CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=n#CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=${CONFIG_VHOST_ENABLED}#"
 -i ${S}/config/common_linuxapp
sed -e 
"s#CONFIG_RTE_LIBRTE_VHOST=n#CONFIG_RTE_LIBRTE_VHOST=${CONFIG_VHOST_ENABLED}#" 
-i ${S}/config/common_linuxapp
+   sed -e 
"s#CONFIG_RTE_LIBRTE_VHOST_NUMA=.*#CONFIG_RTE_LIBRTE_VHOST_NUMA=${CONFIG_HAVE_NUMA}#"
 -i ${S}/config/common_linuxapp
+   sed -e 
"s#CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=.*#CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=${CONFIG_HAVE_NUMA}#"
 -i ${S}/config/common_linuxapp
 
make O=$RTE_TARGET T=$RTE_TARGET config
 }
-- 
2.14.3

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] swupdate yocto

2018-04-03 Thread Stephano Cetola

On 4/2/18 11:49 PM, Mohammad, Jamal M wrote:
> I modified EFI_PROVIDER to "grub-efi" for intel-core-i7 machine and generated 
> a root filesystem ( ext4 )
> 
> Now I need to create an additional partition to keep this initrd image and 
> then modify the grub configuration to jump into this.
> 
> Do you have any idea on this where I have to modify the partition script in 
> yocto..

If you are using a recent version of Yocto, have a look at wic:

https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#creating-partitioned-images-using-wic

That is how we produce multiple partitions since our last release (2.4).

Before that you would have to do this manually. Freescale has a great
example of how to do this in their image_types child class:

https://github.com/Freescale/meta-fsl-arm/blob/master/classes/image_types_fsl.bbclass

Again, I would only recommend this if you do not have access to wic and
wks (wic kick start) files.

--S

> 
> Regards,
> Jamal
> 
> -Original Message-
> From: Stephano Cetola [mailto:stephano.cet...@linux.intel.com] 
> Sent: Monday, April 02, 2018 7:19 PM
> To: Mohammad, Jamal M 
> Cc: meta-intel@yoctoproject.org
> Subject: Re: [meta-intel] swupdate yocto
> 
> For swupdate support, please see their google group:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_forum_-23-21topic_swupdate_MGq0uMQAUvs=DwID-g=gJN2jf8AyP5Q6Np0yWY19w=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0LHnCs=mmFyyRToaSShSSW6iBMDSgFBGdZwS6N_3E0Gh_Rg4oY=1ozow8dnGfNk8acsmAlQ0i3pGQM6YI-ULbt1c9SnoIs=
> 
> It sounds like you need to understand swupdate better so that you can utilize 
> their GRUB or EFI Boot Guard support.
> 
> Cheers,
> Stephano
> 
> On 4/2/18 2:56 AM, Mohammad, Jamal M wrote:
>> Hi,
>>
>> I cloned the master branch of poky, meta-intel and meta-swupdate and 
>> then I added both layers to bblayers.conf file
>>
>> When I run "bitbake swupdate-image", I get the following error:
>>
>>
>> ERROR: Nothing PROVIDES 'u-boot-fw-utils' (but 
>> /home/jamal/Yocto/poky/meta-swupdate/recipes-support/swupdate/https://
>> urldefense.proofpoint.com/v2/url?u=http-3A__swupdate-5F2018.03.bb=Dw
>> ID-g=gJN2jf8AyP5Q6Np0yWY19w=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0
>> LHnCs=mmFyyRToaSShSSW6iBMDSgFBGdZwS6N_3E0Gh_Rg4oY=i4W4pGZF6XiTAmaS
>> _-nkyCmsELJf5Irdu5h9vGY_MrM=
>> DEPENDS on or otherwise requires it)
>>
>> u-boot-fw-utils was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must 
>> be set in the intel-corei7-64 machine configuration.
>>
>> NOTE: Runtime target 'swupdate-www' is unbuildable, removing...
>>
>> Missing or unbuildable dependency chain was: ['swupdate-www', 
>> 'u-boot-fw-utils']
>>
>> ERROR: Required build target 'swupdate-image' has no buildable providers.
>>
>> Missing or unbuildable dependency chain was: ['swupdate-image', 
>> 'swupdate-www', 'u-boot-fw-utils']
>>
>> As, it is Intel board, the bootloader should not be uboot, so why it 
>> is throwing that error. I am just a beginner in Yocto.. Forgive me if 
>> I made a small mistake. Did anyone have steps of how to get started 
>> for swupdate on Intel Yocto.
>>
>> Thanks and Regards,
>> Mohammad Jamal,
>> NCR Corporation
> 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] bootloader used for core-image-full-cmdline

2018-04-03 Thread Stephano Cetola

On 4/3/18 2:54 AM, Mohammad, Jamal M wrote:
> Can we use u-boot with Intel boards?

This depends on which specific device you are referencing and whether
that device manufacturer supports u-boot.

I have never seen any x86 based device use u-boot in a production
environment.

--S

> 
> -Original Message-
> From: Anuj Mittal [mailto:anuj.mit...@intel.com] 
> Sent: Tuesday, April 03, 2018 3:23 PM
> To: Mohammad, Jamal M ; 
> meta-intel@yoctoproject.org
> Subject: Re: [meta-intel] bootloader used for core-image-full-cmdline
> 
> On 04/03/2018 11:11 AM, Mohammad, Jamal M wrote:
>> Hi,
>>
>>  
>>
>> What is the bootloader used when we flash core-image-minimal or 
>> core-image-full-cmdline image.
>>
> 
> It depends on the value of EFI_PROVIDER. It can be grub-efi or systemd-boot.
> 
>>  
>>
>> I don't see any grub image there in tmp/deploy/images folder
>>
>>  
>>
>> Is bootx64.efi a bootloader?
>>
> 
> Yes, that is what the firmware looks for.
> 
> Thanks,
> Anuj
> 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] bootloader used for core-image-full-cmdline

2018-04-03 Thread Mohammad, Jamal M

Can we use u-boot with Intel boards?

-Original Message-
From: Anuj Mittal [mailto:anuj.mit...@intel.com] 
Sent: Tuesday, April 03, 2018 3:23 PM
To: Mohammad, Jamal M ; 
meta-intel@yoctoproject.org
Subject: Re: [meta-intel] bootloader used for core-image-full-cmdline

On 04/03/2018 11:11 AM, Mohammad, Jamal M wrote:
> Hi,
> 
>  
> 
> What is the bootloader used when we flash core-image-minimal or 
> core-image-full-cmdline image.
> 

It depends on the value of EFI_PROVIDER. It can be grub-efi or systemd-boot.

>  
> 
> I don't see any grub image there in tmp/deploy/images folder
> 
>  
> 
> Is bootx64.efi a bootloader?
> 

Yes, that is what the firmware looks for.

Thanks,
Anuj
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] bootloader used for core-image-full-cmdline

2018-04-03 Thread Anuj Mittal

On 04/03/2018 11:11 AM, Mohammad, Jamal M wrote:
> Hi,
> 
>  
> 
> What is the bootloader used when we flash core-image-minimal or
> core-image-full-cmdline image.
> 

It depends on the value of EFI_PROVIDER. It can be grub-efi or systemd-boot.

>  
> 
> I don’t see any grub image there in tmp/deploy/images folder
> 
>  
> 
> Is bootx64.efi a bootloader?
> 

Yes, that is what the firmware looks for.

Thanks,
Anuj
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] swupdate yocto

2018-04-03 Thread Mohammad, Jamal M

I modified EFI_PROVIDER to "grub-efi" for intel-core-i7 machine and generated a 
root filesystem ( ext4 )

Now I need to create an additional partition to keep this initrd image and then 
modify the grub configuration to jump into this.

Do you have any idea on this where I have to modify the partition script in 
yocto..

Regards,
Jamal

-Original Message-
From: Stephano Cetola [mailto:stephano.cet...@linux.intel.com] 
Sent: Monday, April 02, 2018 7:19 PM
To: Mohammad, Jamal M 
Cc: meta-intel@yoctoproject.org
Subject: Re: [meta-intel] swupdate yocto

For swupdate support, please see their google group:

https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_forum_-23-21topic_swupdate_MGq0uMQAUvs=DwID-g=gJN2jf8AyP5Q6Np0yWY19w=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0LHnCs=mmFyyRToaSShSSW6iBMDSgFBGdZwS6N_3E0Gh_Rg4oY=1ozow8dnGfNk8acsmAlQ0i3pGQM6YI-ULbt1c9SnoIs=

It sounds like you need to understand swupdate better so that you can utilize 
their GRUB or EFI Boot Guard support.

Cheers,
Stephano

On 4/2/18 2:56 AM, Mohammad, Jamal M wrote:
> Hi,
> 
> I cloned the master branch of poky, meta-intel and meta-swupdate and 
> then I added both layers to bblayers.conf file
> 
> When I run "bitbake swupdate-image", I get the following error:
> 
> 
> ERROR: Nothing PROVIDES 'u-boot-fw-utils' (but 
> /home/jamal/Yocto/poky/meta-swupdate/recipes-support/swupdate/https://
> urldefense.proofpoint.com/v2/url?u=http-3A__swupdate-5F2018.03.bb=Dw
> ID-g=gJN2jf8AyP5Q6Np0yWY19w=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0
> LHnCs=mmFyyRToaSShSSW6iBMDSgFBGdZwS6N_3E0Gh_Rg4oY=i4W4pGZF6XiTAmaS
> _-nkyCmsELJf5Irdu5h9vGY_MrM=
> DEPENDS on or otherwise requires it)
> 
> u-boot-fw-utils was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must 
> be set in the intel-corei7-64 machine configuration.
> 
> NOTE: Runtime target 'swupdate-www' is unbuildable, removing...
> 
> Missing or unbuildable dependency chain was: ['swupdate-www', 
> 'u-boot-fw-utils']
> 
> ERROR: Required build target 'swupdate-image' has no buildable providers.
> 
> Missing or unbuildable dependency chain was: ['swupdate-image', 
> 'swupdate-www', 'u-boot-fw-utils']
>
> As, it is Intel board, the bootloader should not be uboot, so why it 
> is throwing that error. I am just a beginner in Yocto.. Forgive me if 
> I made a small mistake. Did anyone have steps of how to get started 
> for swupdate on Intel Yocto.
> 
> Thanks and Regards,
> Mohammad Jamal,
> NCR Corporation

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [meta-dpdk][PATCH v2] dpdk.inc: fix missing numa.h by disabling NUMA options by default

Re: [meta-intel] [meta-dpdk][PATCH] dpdk.inc: fix missing numa.h by disabling NUMA options by default

[meta-intel] [meta-dpdk][PATCH v2] dpdk.inc: fix missing numa.h by disabling NUMA options by default

Re: [meta-intel] swupdate yocto

Re: [meta-intel] bootloader used for core-image-full-cmdline

Re: [meta-intel] bootloader used for core-image-full-cmdline

Re: [meta-intel] bootloader used for core-image-full-cmdline

Re: [meta-intel] swupdate yocto

8 matches

Site Navigation

Mail list logo

Footer information