[PATCH 0/3] more Xen updates

[PATCH 0/3] more Xen updates

[Doug Goldstein]

Here are some updates for master and morty. The README is something that I hope
is ok to try and provide users some more info when they work with Xen.

Doug Goldstein (3):
  xen: update license checksum
  xen: remove unused patch
  xen: add a README to provide info for users

 recipes-extended/xen/README                        | 23 +++++++++
 ...l-compilation-warning-fix-for-arm-aarch64.patch | 58 ----------------------
 recipes-extended/xen/xen.inc                       |  2 +-
 3 files changed, 24 insertions(+), 59 deletions(-)
 create mode 100644 recipes-extended/xen/README
 delete mode 100644 recipes-extended/xen/files/libxl-compilation-warning-fix-for-arm-aarch64.patch

-- 
2.10.2

[PATCH 1/3] xen: update license checksum

[Doug Goldstein]

The checksum of the license changed with the 4.8.0 release.
---
 recipes-extended/xen/xen.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-extended/xen/xen.inc b/recipes-extended/xen/xen.inc
index af907b6..0084274 100644
--- a/recipes-extended/xen/xen.inc
+++ b/recipes-extended/xen/xen.inc
@@ -3,7 +3,7 @@ HOMEPAGE = "http://xen.org"
 LICENSE = "GPLv2"
 SECTION = "console/tools"
 
-LIC_FILES_CHKSUM = "file://COPYING;md5=a6260c12cd5de27e80d89ae18e48d20a"
+LIC_FILES_CHKSUM = "file://COPYING;md5=bbb4b1bdc2c3b6743da3c39d03249095"
 
 COMPATIBLE_HOST = '(x86_64.*).*-linux|aarch64.*-linux'
 
-- 
2.10.2

[PATCH 2/3] xen: remove unused patch

[Doug Goldstein]

---
 ...l-compilation-warning-fix-for-arm-aarch64.patch | 58 ----------------------
 1 file changed, 58 deletions(-)
 delete mode 100644 recipes-extended/xen/files/libxl-compilation-warning-fix-for-arm-aarch64.patch

diff --git a/recipes-extended/xen/files/libxl-compilation-warning-fix-for-arm-aarch64.patch b/recipes-extended/xen/files/libxl-compilation-warning-fix-for-arm-aarch64.patch
deleted file mode 100644
index baab928..0000000
--- a/recipes-extended/xen/files/libxl-compilation-warning-fix-for-arm-aarch64.patch
+++ /dev/null
@@ -1,58 +0,0 @@
-Upstream-Status: Submitted
-
-From 3716a7faf98e1e126d47fe1596593917c27ee1bd Mon Sep 17 00:00:00 2001
-From: Chris Patterson <pattersonc@ainfosec.com>
-Date: Tue, 26 Jul 2016 16:01:47 -0400
-Subject: [PATCH] libxl: compilation warning fix for arm & aarch64
-
-GCC 6 will warn on unused static const variables in c modules:
-https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00847.html
-
-When compiling with LIBXL_HAVE_NO_SUSPEND_RESUME set (arm & aarch64),
-the compiler emits the following errors:
-  xl_cmdimpl.c:101:19: error: 'migrate_report'
-      defined but not used [-Werror=unused-const-variable=]
-  xl_cmdimpl.c:99:19: error: 'migrate_permission_to_go'
-      defined but not used [-Werror=unused-const-variable=]
-  xl_cmdimpl.c:97:19: error: 'migrate_receiver_ready'
-      defined but not used [-Werror=unused-const-variable=]
-  xl_cmdimpl.c:95:19: error: 'migrate_receiver_banner'
-      defined but not used [-Werror=unused-const-variable=]
-
-These unused const variables are only used in functions which exist between
-the ifndef block:
-   #ifndef LIBXL_HAVE_NO_SUSPEND_RESUME
-   ...
-   #endif
-
-Wrap the same ifndef around these variables.
-
-Signed-off-by: Chris Patterson <pattersonc@ainfosec.com>
----
- tools/libxl/xl_cmdimpl.c | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
-index d1fcfa4..ada8178 100644
---- a/tools/libxl/xl_cmdimpl.c
-+++ b/tools/libxl/xl_cmdimpl.c
-@@ -92,6 +92,7 @@ static int fd_lock = -1;
- static const char savefileheader_magic[32]=
-     "Xen saved domain, xl format\n \0 \r";
- 
-+#ifndef LIBXL_HAVE_NO_SUSPEND_RESUME
- static const char migrate_receiver_banner[]=
-     "xl migration receiver ready, send binary domain data.\n";
- static const char migrate_receiver_ready[]=
-@@ -100,6 +101,8 @@ static const char migrate_permission_to_go[]=
-     "domain is yours, you are cleared to unpause";
- static const char migrate_report[]=
-     "my copy unpause results are as follows";
-+#endif
-+
-   /* followed by one byte:
-    *     0: everything went well, domain is running
-    *            next thing is we all exit
--- 
-2.7.4
-
-- 
2.10.2

[PATCH 3/3] xen: add a README to provide info for users

[Doug Goldstein]

Provided some basic documentation on how to use the xen recipe properly.
---
 recipes-extended/xen/README | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 recipes-extended/xen/README

diff --git a/recipes-extended/xen/README b/recipes-extended/xen/README
new file mode 100644
index 0000000..6ce2581
--- /dev/null
+++ b/recipes-extended/xen/README
@@ -0,0 +1,23 @@
+Xen
+---
+
+For any issues with the xen recipes please make sure you CC cardoe@gentoo.org
+
+configuring the hypervisor
+--------------------------
+
+Since 4.7.0 Xen supports using Kconfig to configure the hypervisor and the
+Yocto recipe supports this similiarly to how busybox works. The easiest way
+for you to take advantage of this is to create a .config for Xen and then
+copy it to your Yocto layer as 'defconfig' inside of
+'recipes-extended/xen/files/' and then create a bbappend adding
+'file://defconfig' to your SRC_URI.
+
+security patches
+----------------
+
+The base recipe does not include security fixes that the Xen community releases
+as XSAs (http://xenbits.xen.org/xsa/). The easiest way to include those is to
+drop patches in 'recipes-extened/xen/files' and create a bbappend adding those
+patches to SRC_URI and they will be applied. Alternatively you can override
+the SRC_URI to a git repo you provide that contains the patches.
-- 
2.10.2

[PATCH] xen: add a README to provide info for users

[Doug Goldstein]

Provided some basic documentation on how to use the xen recipe properly.
---
 recipes-extended/xen/README | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 recipes-extended/xen/README

diff --git a/recipes-extended/xen/README b/recipes-extended/xen/README
new file mode 100644
index 0000000..3686530
--- /dev/null
+++ b/recipes-extended/xen/README
@@ -0,0 +1,24 @@
+Xen
+---
+
+For any issues with the xen recipes please make sure you CC cardoe@gentoo.org
+
+configuring the hypervisor
+--------------------------
+
+Since 4.7.0 Xen supports using Kconfig to configure the hypervisor. Similarly
+to how the recipe for busybox works, you can provide a .config as a defconfig
+to override the default configuration of the hypervisor. The easiest way
+for you to take advantage of this is to create a .config for Xen and then
+copy it to your Yocto layer as 'defconfig' inside of
+'recipes-extended/xen/files/' and then create a bbappend adding
+'file://defconfig' to your SRC_URI.
+
+security patches
+----------------
+
+The base recipe does not include security fixes that the Xen community releases
+as XSAs (http://xenbits.xen.org/xsa/). The easiest way to include those is to
+drop patches in 'recipes-extened/xen/files' and create a bbappend adding those
+patches to SRC_URI and they will be applied. Alternatively, you can override
+the SRC_URI to a git repo you provide that contains the patches.
-- 
2.10.2

Re: [PATCH] xen: add a README to provide info for users

[Doug Goldstein]

[-- Attachment #1.1: Type: text/plain, Size: 1700 bytes --]

sorry for the confusion. This replaces patch 3 and provides better wording.


On 1/5/17 11:32 AM, Doug Goldstein wrote:
> Provided some basic documentation on how to use the xen recipe properly.
> ---
>  recipes-extended/xen/README | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
>  create mode 100644 recipes-extended/xen/README
> 
> diff --git a/recipes-extended/xen/README b/recipes-extended/xen/README
> new file mode 100644
> index 0000000..3686530
> --- /dev/null
> +++ b/recipes-extended/xen/README
> @@ -0,0 +1,24 @@
> +Xen
> +---
> +
> +For any issues with the xen recipes please make sure you CC cardoe@gentoo.org
> +
> +configuring the hypervisor
> +--------------------------
> +
> +Since 4.7.0 Xen supports using Kconfig to configure the hypervisor. Similarly
> +to how the recipe for busybox works, you can provide a .config as a defconfig
> +to override the default configuration of the hypervisor. The easiest way
> +for you to take advantage of this is to create a .config for Xen and then
> +copy it to your Yocto layer as 'defconfig' inside of
> +'recipes-extended/xen/files/' and then create a bbappend adding
> +'file://defconfig' to your SRC_URI.
> +
> +security patches
> +----------------
> +
> +The base recipe does not include security fixes that the Xen community releases
> +as XSAs (http://xenbits.xen.org/xsa/). The easiest way to include those is to
> +drop patches in 'recipes-extened/xen/files' and create a bbappend adding those
> +patches to SRC_URI and they will be applied. Alternatively, you can override
> +the SRC_URI to a git repo you provide that contains the patches.
> 


-- 
Doug Goldstein


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 978 bytes --]

Re: [PATCH 0/3] more Xen updates

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]

On Thu, Jan 5, 2017 at 12:05 PM, Doug Goldstein <cardoe@cardoe.com> wrote:

> Here are some updates for master and morty. The README is something that I
> hope
> is ok to try and provide users some more info when they work with Xen.
>

merged.

I think I got the right README patch. As much as I like gmail, I detest the
way it threads messages with the same subject.

Bruce


>
> Doug Goldstein (3):
>   xen: update license checksum
>   xen: remove unused patch
>   xen: add a README to provide info for users
>
>  recipes-extended/xen/README                        | 23 +++++++++
>  ...l-compilation-warning-fix-for-arm-aarch64.patch | 58
> ----------------------
>  recipes-extended/xen/xen.inc                       |  2 +-
>  3 files changed, 24 insertions(+), 59 deletions(-)
>  create mode 100644 recipes-extended/xen/README
>  delete mode 100644 recipes-extended/xen/files/
> libxl-compilation-warning-fix-for-arm-aarch64.patch
>
> --
> 2.10.2
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 2199 bytes --]