On 30.01.2023 10:21, Josef Johansson wrote:
> On 11/21/22 11:21, Roger Pau Monne wrote:
>> --- a/arch/x86/xen/enlighten.c
>> +++ b/arch/x86/xen/enlighten.c
>> @@ -346,3 +346,30 @@ void xen_arch_unregister_cpu(int num)
>> }
>> EXPORT_SYMBOL(xen_arch_unregister_cpu);
>> #endif
>> +
>> +#ifdef C
flight 176341 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176341/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-freebsd12-amd64 21 guest-start/freebsd.repeat fail REGR. vs.
173462
build-arm64-
flight 176336 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176336/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
One-element arrays are deprecated, and we are replacing them with flexible
array members instead. So, replace one-element array with flexible-array
member in struct xen_page_directory.
This helps with the ongoing efforts to tighten the FORTIFY_SOURCE
routines on memcpy() and help us make progress
flight 176339 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176339/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
flight 176333 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176333/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf 4 host-insta
flight 176325 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176325/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
On Thu, Feb 02, 2023 at 02:56:34PM -0500, Mike Snitzer wrote:
> On Thu, Feb 02 2023 at 1:41P -0500,
> Demi Marie Obenour wrote:
>
> > On Thu, Feb 02, 2023 at 11:50:37AM -0500, Mike Snitzer wrote:
> > > On Wed, Jan 25 2023 at 10:33P -0500,
> > > Demi Marie Obenour wrote:
> > >
> > > > This work
flight 176326 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176326/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
flight 176321 xen-4.17-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176321/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-win7-amd64 broken
test-amd6
On Thu, Feb 02 2023 at 1:41P -0500,
Demi Marie Obenour wrote:
> On Thu, Feb 02, 2023 at 11:50:37AM -0500, Mike Snitzer wrote:
> > On Wed, Jan 25 2023 at 10:33P -0500,
> > Demi Marie Obenour wrote:
> >
> > > This work aims to allow userspace to create and destroy block devices
> > > in a race-f
flight 176337 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176337/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
On Thu, Feb 02, 2023 at 11:50:37AM -0500, Mike Snitzer wrote:
> On Wed, Jan 25 2023 at 10:33P -0500,
> Demi Marie Obenour wrote:
>
> > This work aims to allow userspace to create and destroy block devices
> > in a race-free and leak-free way,
>
> "race-free and leak-free way" implies there both
On 02/02/2023 6:34 pm, Andrew Cooper wrote:
On 02/02/2023 5:18 pm, Andrew Cooper wrote:
On 02/02/2023 5:13 pm, Bernhard Kaindl wrote:
Fixes for Py3:
* class Delayed(): file not defined; also an error for pylint -E
* Inconsistent use of tabs and spaces for indentation (in one block)
Signed-off-
On 02/02/2023 5:18 pm, Andrew Cooper wrote:
> On 02/02/2023 5:13 pm, Bernhard Kaindl wrote:
>> Fixes for Py3:
>> * class Delayed(): file not defined; also an error for pylint -E
>> * Inconsistent use of tabs and spaces for indentation (in one block)
>>
>> Signed-off-by: Bernhard Kaindl
> Acked-by:
On 02/02/2023 5:13 pm, Bernhard Kaindl wrote:
> Fixes for Py3:
> * class Delayed(): file not defined; also an error for pylint -E
> * Inconsistent use of tabs and spaces for indentation (in one block)
>
> Signed-off-by: Bernhard Kaindl
Acked-by: Andrew Cooper
I'll add this to my pending queue w
Fixes for Py3:
* class Delayed(): file not defined; also an error for pylint -E
* Inconsistent use of tabs and spaces for indentation (in one block)
Signed-off-by: Bernhard Kaindl
---
tools/xenmon/xenmon.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/xenmon/xe
On Wed, Jan 25 2023 at 10:33P -0500,
Demi Marie Obenour wrote:
> This work aims to allow userspace to create and destroy block devices
> in a race-free and leak-free way,
"race-free and leak-free way" implies there both races and leaks in
existing code. You're making claims that are likely very
On Thu, 2 Feb 2023, Paul Durrant wrote:
> On 01/02/2023 18:22, Vikram Garhwal wrote:
> > Hi Paul,
> >
> > Thanks for reviewing this and other patches in series.
> >
> > Please see my reply below.
> >
> > On 2/1/23 12:30 AM, Paul Durrant wrote:
> > > On 31/01/2023 22:51, Vikram Garhwal wrote:
> >
flight 176335 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176335/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
On 12/01/2023 4:52 pm, Jan Beulich wrote:
> (re-sending with REST on Cc, as requested at the community call)
>
> At present we use a mix of Makefile and Kconfig driven capability checks for
> tool chain components involved in the building of the hypervisor. What
> approach
> is used where is in s
flight 176332 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176332/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf 4 host-ins
On 01/02/2023 18:22, Vikram Garhwal wrote:
Hi Paul,
Thanks for reviewing this and other patches in series.
Please see my reply below.
On 2/1/23 12:30 AM, Paul Durrant wrote:
On 31/01/2023 22:51, Vikram Garhwal wrote:
Add a new machine xenpvh which creates a IOREQ server to
register/connect w
On 02/02/2023 11:08 am, Luca Fancellu wrote:
> Recent changes added in struct xen_sysctl_physinfo a new flag for
> arch_capabilities to understand when the platform is SVE capable,
> another field having the maximum SVE vector length in bits was
> added as well, so update the tools to handle these
flight 176334 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176334/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
flight 176328 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176328/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf ae6e470252d9312dce20d0b21e7f622c4ca9ad0a
baseline version:
ovmf d375273c899bfa279c273
On Thu, Feb 02, 2023 at 11:08:14AM +, Luca Fancellu wrote:
> Recent changes added in struct xen_sysctl_physinfo a new flag for
> arch_capabilities to understand when the platform is SVE capable,
> another field having the maximum SVE vector length in bits was
> added as well, so update the tool
On 02.02.2023 12:08, Luca Fancellu wrote:
> When the arm platform supports SVE, advertise the feature by a new
> flag for the arch_capabilities in struct xen_sysctl_physinfo and add
> a new field "arm_sve_vl_bits" where on arm there can be stored the
> maximum SVE vector length in bits.
>
> Update
flight 176331 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176331/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
On 01.02.2023 23:11, Julien Grall wrote:
> On 01/02/2023 17:40, Oleksii wrote:
>> I wrote the following macros and they have been compiled without any
>> errors:
>> .
>> #define _ASM_BUGFRAME_TEXT(second_frame) \
>> ".Lbug%=: ebreak\n"
Hi Julien,
On 02/02/2023 12:23, Julien Grall wrote:
>
>
> On 02/02/2023 11:12, Michal Orzel wrote:
>> Hi Julien,
>
> Hi Michal,
>
>>
>> On 02/02/2023 12:01, Julien Grall wrote:
>>>
>>>
>>> Hi Michal,
>>>
>>> On 02/02/2023 08:49, Michal Orzel wrote:
@@ -265,11 +284,14 @@ static __init int
Hi, Julien
> -Original Message-
> From: Julien Grall
> Sent: Thursday, February 2, 2023 6:58 PM
> To: Penny Zheng ; xen-devel@lists.xenproject.org;
> Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> ayan.kumar.hal...@xilinx.com
> Cc: Volodymyr Babchuk
> Subject: Re: [PATCH v2 11/40
On 02/02/2023 11:12, Michal Orzel wrote:
Hi Julien,
Hi Michal,
On 02/02/2023 12:01, Julien Grall wrote:
Hi Michal,
On 02/02/2023 08:49, Michal Orzel wrote:
@@ -265,11 +284,14 @@ static __init int kernel_decompress(struct bootmodule
*mod)
#define IH_ARCH_ARM 2 /*
Hi Julien,
On 02/02/2023 12:01, Julien Grall wrote:
>
>
> Hi Michal,
>
> On 02/02/2023 08:49, Michal Orzel wrote:
>> @@ -265,11 +284,14 @@ static __init int kernel_decompress(struct bootmodule
>> *mod)
>> #define IH_ARCH_ARM 2 /* ARM */
>> #define IH_ARCH_ARM64
Hi Penny,
On 02/02/2023 08:05, Penny Zheng wrote:
-Original Message-
From: Julien Grall
Sent: Thursday, February 2, 2023 3:27 AM
To: Penny Zheng ; xen-devel@lists.xenproject.org
Cc: Wei Chen ; Stefano Stabellini
; Bertrand Marquis ;
Volodymyr Babchuk
Subject: Re: [PATCH v2 13/40] xen/m
Add sve parameter in XL configuration to allow guests to use
SVE feature.
Signed-off-by: Luca Fancellu
---
Changes from RFC:
- changed libxl_types.idl sve field to uint16
- now toolstack uses info from physinfo to check against the
sve XL value
- Changed documentation
---
docs/man/xl.cfg.5
Add a device tree property in the dom0less domU configuration
to enable the guest to use SVE.
Update documentation.
Signed-off-by: Luca Fancellu
---
Changes from RFC:
- Changed documentation
---
docs/misc/arm/device-tree/booting.txt | 9 +
xen/arch/arm/domain_build.c | 7
Recent changes added in struct xen_sysctl_physinfo a new flag for
arch_capabilities to understand when the platform is SVE capable,
another field having the maximum SVE vector length in bits was
added as well, so update the tools to handle these new fields.
Signed-off-by: Luca Fancellu
---
Change
Save/restore context switch for SVE, allocate memory to contain
the Z0-31 registers whose length is maximum 2048 bits each and
FFR who can be maximum 256 bits, the allocated memory depends on
how many bits is the vector length for the domain and how many bits
are supported by the platform.
Save P0
Add a command line parameter to allow Dom0 the use of SVE resources,
the command line parameter dom0_sve controls the feature on this
domain and sets the maximum SVE vector length for Dom0.
Signed-off-by: Luca Fancellu
---
Changes from RFC:
- Changed docs to explain that the domain won't be crea
When the arm platform supports SVE, advertise the feature by a new
flag for the arch_capabilities in struct xen_sysctl_physinfo and add
a new field "arm_sve_vl_bits" where on arm there can be stored the
maximum SVE vector length in bits.
Update the padding.
Bump XEN_SYSCTL_INTERFACE_VERSION for t
Enable Xen to handle the SVE extension, add code in cpufeature module
to handle ZCR SVE register, disable trapping SVE feature on system
boot only when SVE resources are accessed.
While there, correct coding style for the comment on coprocessor
trapping.
Now cptr_el2 is part of the domain context
This serie is introducing the possibility for Dom0 and DomU guests to use
sve/sve2 instructions.
SVE feature introduces new instruction and registers to improve performances on
floating point operations.
The SVE feature is advertised using the ID_AA64PFR0_EL1 register, SVE field, and
when availab
When a guest is allowed to use SVE, expose the SVE features through
the identification registers.
Signed-off-by: Luca Fancellu
---
Changes from RFC:
- No changes
---
xen/arch/arm/arm64/vsysreg.c | 39 ++--
1 file changed, 37 insertions(+), 2 deletions(-)
diff --
SVE has a new exception class with code 0x19, introduce the new code
and handle the exception.
Signed-off-by: Luca Fancellu
---
Changes from RFC:
- No changes
---
xen/arch/arm/include/asm/processor.h | 1 +
xen/arch/arm/traps.c | 12
2 files changed, 13 insertions(
Add sve_vl_bits field to arch_domain and xen_arch_domainconfig
structure, to allow the domain to have an information about the
SVE feature and the number of SVE register bits that are allowed
for this domain.
The field is used also to allow or forbid a domain to use SVE,
because a value equal to z
Hi Michal,
On 02/02/2023 08:49, Michal Orzel wrote:
@@ -265,11 +284,14 @@ static __init int kernel_decompress(struct bootmodule
*mod)
#define IH_ARCH_ARM 2 /* ARM */
#define IH_ARCH_ARM64 22 /* ARM64*/
+/* uImage Compression Types */
+#d
On 02/02/2023 10:53, Penny Zheng wrote:
Hi Julien,
Hi,
-Original Message-
From: Julien Grall
Sent: Thursday, February 2, 2023 2:57 AM
To: Penny Zheng ; xen-devel@lists.xenproject.org;
Wei Chen ; Stefano Stabellini
; Bertrand Marquis ;
ayan.kumar.hal...@xilinx.com
Cc: Volodymyr Bab
Hi Julien,
> -Original Message-
> From: Julien Grall
> Sent: Thursday, February 2, 2023 2:57 AM
> To: Penny Zheng ; xen-devel@lists.xenproject.org;
> Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> ayan.kumar.hal...@xilinx.com
> Cc: Volodymyr Babchuk
> Subject: Re: [PATCH v2 11/40
flight 176314 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176314/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
test-amd64-amd64-xl-pvshim
On Thu, Feb 2, 2023 at 2:05 AM Henry Wang wrote:
> Hi George,
>
>
>
> > From: George Dunlap
>
> > Subject: Re: [PATCH] Changelog: Add details about new features for SPR
>
> >
>
> > One approach would be to have someone / something (either the release
> manager, or an automated script)
>
>
>
> An
> Thanks, Kevin.
>
> I'd like to get the rest of the Xen platform support in to qemu 8.0 if
> possible. Which is currently scheduled for March.
>
> Is there likely to be a SeaBIOS release before then which Gerd would
> pull into qemu anyway, or should I submit a submodule update to a
> snapshot o
flight 176330 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176330/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
At the moment, Xen does not support booting gzip compressed uImages.
This is because we are trying to decompress the kernel before probing
the u-boot header. This leads to a failure as the header always appears
at the top of the image (and therefore obscuring the gzip header).
Move the call to ker
This series adds support for booting gzip compressed images with u-boot header.
Currently Xen does not support such images because we are trying to decompress
the kernel before probing uImage header.
The problem can be solved using 2 different approaches:
1) Split uImage probing into 2 stages. The
In a follow-up patch, we will be calling kernel_decompress function from
within kernel_uimage_probe to support booting compressed images with
u-boot header. Therefore, move the kernel_uimage_probe definition after
kernel_decompress so that the latter is visible to the former.
No functional change
Hi Julien,
On 01/02/2023 19:54, Julien Grall wrote:
>
>
> On 01/02/2023 12:56, Michal Orzel wrote:
>> Hi Julien,
>
> Hi Michal,
>
>> On 01/02/2023 12:20, Julien Grall wrote:
>>>
>>>
>>> On 01/02/2023 11:01, Michal Orzel wrote:
I would prefer not to do this in this series as the goals are
> -Original Message-
> From: Julien Grall
> Sent: Thursday, February 2, 2023 3:27 AM
> To: Penny Zheng ; xen-devel@lists.xenproject.org
> Cc: Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk
> Subject: Re: [PATCH v2 13/40] xen/mpu: introduce unified function
> setu
On Wed, 2023-02-01 at 21:13 -0500, Kevin O'Connor wrote:
> On Fri, Jan 20, 2023 at 11:33:19AM +, David Woodhouse wrote:
> > From: David Woodhouse
> >
> > When running under Xen, hvmloader places a table at 0x1000 with the e820
> > information and BIOS tables. If this isn't present, SeaBIOS wi
59 matches
Mail list logo
