[xen-unstable test] 186920: tolerable FAIL - PUSHED

2024-07-19 Thread osstest service owner
flight 186920 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/186920/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 186891 test-amd64-amd64-xl-qemuu-ws16-amd64

[PATCH] CI: workaround broken selinux+docker interaction in yocto

2024-07-19 Thread Marek Marczykowski-Górecki
`cp --preserve=xattr` doesn't work in docker when SELinux is enabled. It tries to set the "security.selinux" xattr, but SELinux (or overlay fs?) denies it. Workaround it by skipping selinux.selinux xattr copying. Signed-off-by: Marek Marczykowski-Górecki --- Tested here: https://gitlab.com/xen-pr

Re: [PATCH 1/6] tools/libxs: Fix length check in xs_talkv()

2024-07-19 Thread Jason Andryuk
On 2024-07-18 12:48, Andrew Cooper wrote: If the sum of iov element lengths overflows, the XENSTORE_PAYLOAD_MAX can pass, after which we'll write 4G of data with a good-looking length field, and the remainder of the payload will be interpreted as subsequent commands. Check each iov element lengt

[xen-4.19-testing test] 186899: tolerable FAIL - PUSHED

2024-07-19 Thread osstest service owner
flight 186899 xen-4.19-testing real [real] flight 186921 xen-4.19-testing real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/186899/ http://logs.test-lab.xenproject.org/osstest/logs/186921/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): t

[xen-unstable-smoke test] 186913: tolerable all pass - PUSHED

2024-07-19 Thread osstest service owner
flight 186913 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/186913/ 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

[xen-unstable test] 186891: tolerable FAIL

2024-07-19 Thread osstest service owner
flight 186891 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/186891/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 186844 test-amd64-amd64-xl-qemut-win7-amd64

Re: [PATCH v2 2/2] Add scripts/oss-fuzz/build.sh

2024-07-19 Thread Tamas K Lengyel
On Thu, Jul 18, 2024 at 1:36 PM Alejandro Vallejo wrote: > > On Tue Jun 25, 2024 at 11:47 PM BST, Tamas K Lengyel wrote: > > The build integration script for oss-fuzz targets. Future fuzzing targets > > can > > be added to this script and those targets will be automatically picked up by > > oss-f

[PATCH v2] Mini-OS: add some macros for asm statements

2024-07-19 Thread Juergen Gross
Instead of having #ifdefs sprinkled around in x86 code, add some macros defining constants for asm statements to address differences between 32- and 64-bit mode. Modify existing code to use those macros. While at it convert the assembler parts of run_idle_thread() to a more sane variant. Signed-

Re: [RFC PATCH 17/17] CODING_STYLE: Add a section on header guards naming conventions

2024-07-19 Thread Stefano Stabellini
On Fri, 19 Jul 2024, Jan Beulich wrote: > On 19.07.2024 00:01, Stefano Stabellini wrote: > > On Thu, 18 Jul 2024, Jan Beulich wrote: > >> On 18.07.2024 01:02, Stefano Stabellini wrote: > >>> On Wed, 17 Jul 2024, Jan Beulich wrote: > On 17.07.2024 02:20, Stefano Stabellini wrote: > > On Tue

[RFC XEN PATCH v2] x86/cpuid: Expose max_vcpus field in HVM hypervisor leaf

2024-07-19 Thread Matthew Barnes
Currently, OVMF is hard-coded to set up a maximum of 64 vCPUs on startup. There are efforts to support a maximum of 128 vCPUs, which would involve bumping the OVMF constant from 64 to 128. However, it would be more future-proof for OVMF to access the maximum number of vCPUs for a domain and set i

[xen-unstable-smoke test] 186906: regressions - FAIL

2024-07-19 Thread osstest service owner
flight 186906 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/186906/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-amd64 7 xen-install fail REGR. vs. 186826 test-amd64-a

[PATCH] xen: PE/COFF image header

2024-07-19 Thread Milan Djokic
From: Nikola Jelic Added PE/COFF generic image header which shall be used for EFI application format for x86/risc-v. x86 and risc-v source shall be adjusted to use this header in following commits. pe.h header is taken over from linux kernel with minor changes in terms of formatting and structure

Re: [PATCH] SUPPORT.md: update Xen version

2024-07-19 Thread Julien Grall
Hi, On 19/07/2024 12:51, Juergen Gross wrote: Update the Xen version to 4.20 Signed-off-by: Juergen Gross I am pretty sure I forgot to update this file also last release :(. Acked-by: Julien Grall --- SUPPORT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SUPPO

[PATCH] SUPPORT.md: update Xen version

2024-07-19 Thread Juergen Gross
Update the Xen version to 4.20 Signed-off-by: Juergen Gross --- SUPPORT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SUPPORT.md b/SUPPORT.md index 77d2a7a7db..bd4316523d 100644 --- a/SUPPORT.md +++ b/SUPPORT.md @@ -9,7 +9,7 @@ for the definitions of the support status l

[PATCH] drivers: char: omap-uart: add "clock-hz" option

2024-07-19 Thread Amneesh Singh
Quite a few TI K3 devices do not have clock-frequency specified in their respective UART nodes. However hard-coding the frequency is not a solution as the function clock input can differ between SoCs. So, similar to com1/com2, let the user pass the frequency as a dtuart option via the bootargs. If

Re: [Vote] Xen Project Code of Conduct Team Member

2024-07-19 Thread Kelly Choi
Hi all, I have received all votes from leadership teams of three mature projects and achieved a quorum on this proposal. Votes have been received both in public and private. The outcome of votes: Hypervisor: +3 Windows PV: +2 XAPI: +2 Roger will be added as the new code of conduct team member.

[qemu-upstream-4.19-testing baseline test] 186879: tolerable FAIL

2024-07-19 Thread osstest service owner
"Old" tested version had not actually been tested; therefore in this flight we test it, rather than a new candidate. The baseline, if any, is the most recent actually tested revision. flight 186879 qemu-upstream-4.19-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/186879/ Fa

Re: [XEN PATCH v4 02/14] x86/altp2m: add static inline stub for altp2m_vcpu_idx()

2024-07-19 Thread Sergiy Kibrik
09.07.24 10:09, Jan Beulich: On 09.07.2024 07:48, Sergiy Kibrik wrote: The stub just returns 0 due to implementation of p2m_get_mem_access() for x86 & ARM expects it to be 0 when altp2m not active or not implemented. The separate stub is favoured over dynamic check for alt2pm availability insi

[xen-unstable-smoke test] 186901: regressions - FAIL

2024-07-19 Thread osstest service owner
flight 186901 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/186901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-amd64 7 xen-install fail REGR. vs. 186826 test-amd64-a

Re: [PATCH for-4.20 4/4] x86/fpu: Split fpu_setup_fpu() in two

2024-07-19 Thread Jan Beulich
On 18.07.2024 19:25, Alejandro Vallejo wrote: > On Thu Jul 18, 2024 at 1:19 PM BST, Jan Beulich wrote: >> On 09.07.2024 17:52, Alejandro Vallejo wrote: >>> --- a/xen/arch/x86/i387.c >>> +++ b/xen/arch/x86/i387.c >>> @@ -310,41 +310,25 @@ int vcpu_init_fpu(struct vcpu *v) >>> return xstate_allo

Re: [PATCH for-4.20 3/4] x86/fpu: Combine fpu_ctxt and xsave_area in arch_vcpu

2024-07-19 Thread Jan Beulich
On 18.07.2024 18:54, Alejandro Vallejo wrote: > On Thu Jul 18, 2024 at 12:49 PM BST, Jan Beulich wrote: >> On 09.07.2024 17:52, Alejandro Vallejo wrote: >>> --- a/xen/arch/x86/include/asm/domain.h >>> +++ b/xen/arch/x86/include/asm/domain.h >>> @@ -591,12 +591,7 @@ struct pv_vcpu >>> >>> struct

Re: [RFC PATCH 17/17] CODING_STYLE: Add a section on header guards naming conventions

2024-07-19 Thread Jan Beulich
On 19.07.2024 00:01, Stefano Stabellini wrote: > On Thu, 18 Jul 2024, Jan Beulich wrote: >> On 18.07.2024 01:02, Stefano Stabellini wrote: >>> On Wed, 17 Jul 2024, Jan Beulich wrote: On 17.07.2024 02:20, Stefano Stabellini wrote: > On Tue, 16 Jul 2024, Jan Beulich wrote: >> On 16.07.20

Re: [PATCH] x86/HVM: get_pat_flags() is needed only by shadow code

2024-07-19 Thread Roger Pau Monné
On Thu, Jul 18, 2024 at 06:06:54PM +0100, Andrew Cooper wrote: > On 18/07/2024 11:10 am, Jan Beulich wrote: > > Therefore with SHADOW_PAGING=n this is better compiled out, to avoid > > leaving around unreachable/dead code. > > > > Signed-off-by: Jan Beulich > > > > --- a/xen/arch/x86/hvm/mtrr.c >