<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-virtualization.git/recipes-extended/xen, branch master-nxt</title>
<subtitle>Mirror of git.yoctoproject.org/meta-virtualization</subtitle>
<id>https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master-nxt</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master-nxt'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/'/>
<updated>2021-11-02T13:57:03+00:00</updated>
<entry>
<title>global: add explicit branch to all SRC_URIs</title>
<updated>2021-11-02T13:57:03+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-10-29T13:51:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=ac399ad09105dce73bccde9574216377613a98de'/>
<id>urn:sha1:ac399ad09105dce73bccde9574216377613a98de</id>
<content type='text'>
As introduced in the oe-core post:

  https://lists.openembedded.org/g/openembedded-core/message/157623

SRC_URIs without an explicit branch will generate warnings, and
eventually be an error.

We run the provided conversion script to make sure that meta-virt
is ready for the change.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xen,xen-tools: update xen to new releases</title>
<updated>2021-11-02T13:57:03+00:00</updated>
<author>
<name>Edward Pickup</name>
<email>edward.pickup@arm.com</email>
</author>
<published>2021-10-26T13:32:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=03689b86cc1b5eb935f5271697336ce5cb6b4e69'/>
<id>urn:sha1:03689b86cc1b5eb935f5271697336ce5cb6b4e69</id>
<content type='text'>
Update the SHA in recipes for xen and xen-tools to use the latest releases;
update xen 4.14 to xen 4.14.3 release, update xen 4.15 to 4.15.1 release, and
xen 4.16 to the current master version.

Add a comment to each recipe indicating which version of Xen is used in recipe.

Do not apply patches that have been merged/solved in Xen and remove patch files
not needed anymore.

Create a test package to pack new tests introduced in 4.16.

Add a depencency to util-linux-prlimit, as the xen 4.16 x86 requires prlimit,
without this boot of dom0 fails.

Signed-off-by: Edward Pickup &lt;Edward.Pickup@arm.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xen: add missing pkgconfig inherit</title>
<updated>2021-10-12T14:17:36+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross@burtonini.com</email>
</author>
<published>2021-10-12T11:56:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=aaeb4f49c04d1f5204d72abc521304e9c125a4f2'/>
<id>urn:sha1:aaeb4f49c04d1f5204d72abc521304e9c125a4f2</id>
<content type='text'>
New oe-core pulls in less default dependencies[1], so add an explicit
inherit of pkgconfig as it is needed to configure Xen.

[1] https://lists.openembedded.org/g/openembedded-core/message/156185

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xen, xen-tools: apply workaround for gnu linker error to fix x86 build</title>
<updated>2021-08-27T14:50:45+00:00</updated>
<author>
<name>Christopher Clark</name>
<email>christopher.w.clark@gmail.com</email>
</author>
<published>2021-08-24T05:10:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=c8e57e4f22b299c1eb65ade4f2a3f43102c3c735'/>
<id>urn:sha1:c8e57e4f22b299c1eb65ade4f2a3f43102c3c735</id>
<content type='text'>
Upstream patch applied to each Xen and Xen tools recipe to fix the build
of the hypervisor and shim with GNU linker 2.37.

Signed-off-by: Christopher Clark &lt;christopher.w.clark@gmail.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>global: overrides syntax conversion</title>
<updated>2021-08-02T21:17:53+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-07-28T18:22:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=d876cfc5bfafa516dee55d04b50b319a22165640'/>
<id>urn:sha1:d876cfc5bfafa516dee55d04b50b319a22165640</id>
<content type='text'>
OEcore/bitbake are moving to use the clearer ":" as an overrides
separator.

This is pass one of updating the meta-virt recipes to use that
syntax.

This has only been minimally build/runtime tested, more changes
will be required for missed overrides, or incorrect conversions

Note: A recent bitbake is required:

    commit 75fad23fc06c008a03414a1fc288a8614c6af9ca
    Author: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
    Date:   Sun Jul 18 12:59:15 2021 +0100

        bitbake: data_smart/parse: Allow ':' characters in variable/function names

        It is becomming increasingly clear we need to find a way to show what
        is/is not an override in our syntax. We need to do this in a way which
        is clear to users, readable and in a way we can transition to.

        The most effective way I've found to this is to use the ":" charater
        to directly replace "_" where an override is being specified. This
        includes "append", "prepend" and "remove" which are effectively special
        override directives.

        This patch simply adds the character to the parser so bitbake accepts
        the value but maps it back to "_" internally so there is no behaviour
        change.

        This change is simple enough it could potentially be backported to older
        version of bitbake meaning layers using the new syntax/markup could
        work with older releases. Even if other no other changes are accepted
        at this time and we don't backport, it does set us on a path where at
        some point in future we could
        require a more explict syntax.

        I've tested this patch by converting oe-core/meta-yocto to the new
        syntax for overrides (9000+ changes) and then seeing that builds
        continue to work with this patch.

        (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284)

        Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xen-tools: remove Arm 32-bit compiler flags override</title>
<updated>2021-07-14T19:33:10+00:00</updated>
<author>
<name>Christopher Clark</name>
<email>christopher.w.clark@gmail.com</email>
</author>
<published>2021-07-08T04:32:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=62137a394fdaa46abbbd539cd6e83d2607520bf0'/>
<id>urn:sha1:62137a394fdaa46abbbd539cd6e83d2607520bf0</id>
<content type='text'>
The SECURITY_FLAGS are already passed into the tools build in
HOST_CC_ARCH so this separate case override is not needed.

Signed-off-by: Christopher Clark &lt;christopher.w.clark@gmail.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xtf: fix build with gcc11 SRCREV and specifying linker</title>
<updated>2021-07-14T19:33:10+00:00</updated>
<author>
<name>Christopher Clark</name>
<email>christopher.w.clark@gmail.com</email>
</author>
<published>2021-07-08T04:32:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=c1cdd76a477cbe95ee89eaf297464d63aa14bdb2'/>
<id>urn:sha1:c1cdd76a477cbe95ee89eaf297464d63aa14bdb2</id>
<content type='text'>
Newer XTF revision works around GCC 11.1 issue 99578 and
supplying the correct linker to use fixes the build.

Signed-off-by: Christopher Clark &lt;christopher.w.clark@gmail.com&gt;
Reviewed-by: Bertrand Marquis &lt;bertrand.marquis@arm.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xen, xen-tools: fix build and passing of CFLAGS via Xen vars</title>
<updated>2021-07-14T19:33:10+00:00</updated>
<author>
<name>Christopher Clark</name>
<email>christopher.w.clark@gmail.com</email>
</author>
<published>2021-07-08T04:32:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=3e128c1bcd8f46a37923271b5b722b378eb72d06'/>
<id>urn:sha1:3e128c1bcd8f46a37923271b5b722b378eb72d06</id>
<content type='text'>
Ensure that the Xen build system variables EXTRA_CFLAGS_XEN_CORE and
EXTRA_CFLAGS_XEN_TOOLS are passed into the compile steps.

Update the hypervisor compilation to avoid passing in most compile flags
from the build environment via EXTRA_CFLAGS_XEN_CORE -- prefer the
compiler defaults and the flags set by the Xen build system, so only the
debug prefix flags are provided.

Observeration derived from the prior commit e99974aa, so:
Reported-by: Diego Sueiro &lt;diego.sueiro@arm.com&gt;
Signed-off-by: Christopher Clark &lt;christopher.w.clark@gmail.com&gt;
Reviewed-by: Bertrand Marquis &lt;bertrand.marquis@arm.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xen, xen-tools: apply upstream fixes for gcc11 compilation</title>
<updated>2021-07-14T19:33:10+00:00</updated>
<author>
<name>Christopher Clark</name>
<email>christopher.w.clark@gmail.com</email>
</author>
<published>2021-07-08T04:32:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=4d61693058271667a5f30a92d8f40c96ff1c16ba'/>
<id>urn:sha1:4d61693058271667a5f30a92d8f40c96ff1c16ba</id>
<content type='text'>
Apply patches for the tools and hypervisor to Xen 4.15 and the git
recipe and uprev Xen 4.14 to latest stable revision.
Retire the previous -Wno-vla-parameter workaround.

Signed-off-by: Christopher Clark &lt;christopher.w.clark@gmail.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>xen-tools: Pass -Wno-vla-parameter to workaround when compiling with gcc-11</title>
<updated>2021-05-06T20:40:28+00:00</updated>
<author>
<name>Diego Sueiro</name>
<email>diego.sueiro@arm.com</email>
</author>
<published>2021-05-06T15:37:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=e99974aa57ec9aa4f51817346ddc744bd9f61eca'/>
<id>urn:sha1:e99974aa57ec9aa4f51817346ddc744bd9f61eca</id>
<content type='text'>
When compiling xen-tools (4.14 and 4.15) with gcc-11 the following kind of
errors are produced:

linux.c:164:50: error: argument 7 of type 'const xen_pfn_t[]' {aka 'const long unsigned int[]'} declared as an ordinary array [-Werror=vla-parameter]
  164 |                                  const xen_pfn_t arr[/*num*/], int err[/*num*/])
      |                                  ~~~~~~~~~~~~~~~~^~~~~~~~~~~~

Workaround it by passing -Wno-vla-parameter to the compiler.

Signed-off-by: Diego Sueiro &lt;diego.sueiro@arm.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
</feed>
