flight 168691 linux-linus real [real]
flight 168700 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/168691/
http://logs.test-lab.xenproject.org/osstest/logs/168700/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-
flight 168698 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168698/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168697 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168697/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168695 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168695/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168694 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168694/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168693 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168693/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
From: Stefano Stabellini
Add qemu-system-arm to the existing test-artifacts qemu container (which
doesn't get build for every iteration but only updated once in a while.)
With qemu-system-arm available, we'll be able to run ARM32 tests.
This patch also bumps the QEMU version to v6.0.0 for both
Add a minimal ARM32 smoke test based on qemu-system-arm, as provided by
the test-artifacts qemu container. The minimal test simply boots Xen
(built from previous build stages) and Dom0. The test is fetching the
Dom0 kernel and initrd from Debian Jessie: they work just fine and this
way we don't hav
Hi all,
This small series adds a simple Xen + Dom0 boot arm32 test to gitlab-ci
using QEMU, similar to the existing tests for arm64 and x86.
Cheers,
Stefano
Stefano Stabellini (2):
gitlab-ci: add qemu-system-arm to the existing tests-artifacts container
gitlab-ci: add an ARM32 qemu
On Fri, 18 Mar 2022, Stefano Stabellini wrote:
> On Fri, 18 Mar 2022, Anthony PERARD wrote:
> > On Wed, Mar 16, 2022 at 06:46:53PM -0700, Stefano Stabellini wrote:
> > > +curl -fsSLO
> > > http://http.us.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/vmlinuz
> > > +curl
On Fri, 18 Mar 2022, Anthony PERARD wrote:
> On Wed, Mar 16, 2022 at 06:46:53PM -0700, Stefano Stabellini wrote:
> > +curl -fsSLO
> > http://http.us.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/vmlinuz
> > +curl -fsSLO
> > http://http.us.debian.org/debian/dists/jessi
On Fri, 18 Mar 2022, Anthony PERARD wrote:
> On Wed, Mar 16, 2022 at 06:46:52PM -0700, Stefano Stabellini wrote:
> > +qemu-system-aarch64-6.0.0-arm32-export:
> > + stage: build
> > + image:
> > registry.gitlab.com/xen-project/xen/tests-artifacts/qemu-system-aarch64:6.0.0-arm64v8
> > + script:
>
On Fri, 18 Mar 2022, Anthony PERARD wrote:
> On Wed, Mar 16, 2022 at 06:38:53PM -0700, Stefano Stabellini wrote:
> > Also considering the recent arm32 xen breakage, which could have been
> > caught by gitlab-ci before commit,
>
> I'm not sure that's true. I think the commits you are speaking about
flight 168692 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168692/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
From: Juergen Gross
> Sent: 18 March 2022 16:56
>
> On 18.03.22 16:22, David Laight wrote:
> > From: Juergen Gross
> >> Sent: 18 March 2022 15:10
> >>
> >> The dcdbas driver is used to call SMI handlers for both, dcdbas and
> >> dell-smbios-smm. Both drivers allocate a buffer for communicating
> >
On Fri, 18 Mar 2022, Penny Zheng wrote:
> > On Fri, 11 Mar 2022, Penny Zheng wrote:
> > > From: Penny Zheng
> > >
> > > This commit introduces process_shm to cope with static shared memory
> > > in domain construction.
> > >
> > > This commit only considers allocating static shared memory to
> > >
On Fri, 18 Mar 2022, Jan Beulich wrote:
> Further (there's no particularly good place to mention this) I'm
> afraid I don't view "shared" as a good name: It's not the domain
> which is shared, but it's the domain to hold shared memory.
To be honest I thought the same thing when reading this patch
On 18/03/2022 10:44, Hongda Deng wrote:
Hi Julien,
Hi Hongda,
-Original Message-
From: Xen-devel On Behalf Of Julien
Grall
Sent: 2022年2月21日 18:22
To: xen-devel@lists.xenproject.org
Cc: jul...@xen.org; Julien Grall ; Stefano Stabellini
; Bertrand Marquis ;
Volodymyr Babchuk
Subject:
On Fri, 18 Mar 2022, Penny Zheng wrote:
> > On Fri, 11 Mar 2022, Penny Zheng wrote:
> > > From: Penny Zheng
> > >
> > > In case to own statically shared pages when owner domain is not
> > > explicitly defined, this commits propose a special domain
> > > DOMID_SHARED, and we assign it 0x7FF5, as on
flight 168690 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168690/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On Fri, 18 Mar 2022, Jan Beulich wrote:
> On 11.03.2022 07:11, Penny Zheng wrote:
> > In case to own statically shared pages when owner domain is not
> > explicitly defined, this commits propose a special domain DOMID_SHARED,
> > and we assign it 0x7FF5, as one of the system domains.
> >
> > Stati
flight 168681 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168681/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-rtds 22 guest-start/debian.repeat fail in 168674 pass in
168681
test-amd64-amd64-xl-multivc
On Fri, 18 Mar 2022, Luca Fancellu wrote:
> > On 18 Mar 2022, at 10:37, Julia Lawall wrote:
> >
> > Various spelling mistakes in comments.
> > Detected with the help of Coccinelle.
> >
> > Signed-off-by: Julia Lawall
>
> Reviewed-by: Luca Fancellu
Acked-by: Stefano Stabellini
I assume this
flight 168689 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168689/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168688 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168688/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168687 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168687/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On 18/03/2022 07:36, Hongda Deng wrote:
Hi Julien,
Hi Hongda,
-Original Message-
From: Xen-devel On Behalf Of Julien
Grall
Sent: 2022年2月21日 18:22
To: xen-devel@lists.xenproject.org
Cc: jul...@xen.org; Julien Grall ; Stefano Stabellini
; Bertrand Marquis ;
Volodymyr Babchuk ; Julien G
flight 168686 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168686/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168685 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168685/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
Hi Juergen,
On 17/03/2022 11:19, Juergen Gross wrote:
On 17.03.22 12:07, Julien Grall wrote:
On 16/03/2022 16:10, Juergen Gross wrote:
Add documentation for two new Xenstore wire commands SET_FEATURE and
GET_FEATURE used to set or query the Xenstore features visible in the
ring page of a given
Hi Ayan,
On 17/03/2022 14:00, Ayan Kumar Halder wrote:
diff --git a/xen/arch/arm/include/asm/mmio.h b/xen/arch/arm/include/asm/mmio.h
index ca259a79c2..79e64d9af8 100644
--- a/xen/arch/arm/include/asm/mmio.h
+++ b/xen/arch/arm/include/asm/mmio.h
@@ -35,6 +35,7 @@ enum instr_decode_state
*
Hi Ayan,
On 17/03/2022 14:00, Ayan Kumar Halder wrote:
If the abort was caused due to access to stage1 translation table, Xen
will try to set the p2m entry (assuming that the Stage 1 translation
table is in a non MMIO region).
If there is no such entry found, then Xen will try to map the address
Hi Ayan,
On 17/03/2022 14:00, Ayan Kumar Halder wrote:
When an instruction is trapped in Xen due to translation fault, Xen
checks if the ISS is invalid (for data abort) or it is an instruction
abort. If so, Xen tries to resolve the translation fault using p2m page
tables. In case of data abort,
flight 168677 xen-unstable real [real]
flight 168684 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/168677/
http://logs.test-lab.xenproject.org/osstest/logs/168684/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd6
flight 168683 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168683/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 168682 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168682/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On 18.03.22 16:22, David Laight wrote:
From: Juergen Gross
Sent: 18 March 2022 15:10
The dcdbas driver is used to call SMI handlers for both, dcdbas and
dell-smbios-smm. Both drivers allocate a buffer for communicating
with the SMI handler. The physical buffer address is then passed to
the call
Hi,
On 18/03/2022 15:25, Luca Fancellu wrote:
Introduce domain-cpupool property of a xen,domain device tree node,
that specifies the cpupool device tree handle of a xen,cpupool node
that identifies a cpupool created at boot time where the guest will
be assigned on creation.
Add member to the xe
Hi Luca,
I only skimmed through the series. I have one question below:
On 18/03/2022 15:25, Luca Fancellu wrote:
+void __init btcpupools_allocate_pools(void)
+{
+unsigned int i;
+bool add_extra_cpupool = false;
+
+/*
+ * If there are no cpupools, the value of next_pool_id is zer
On Wed, Mar 16, 2022 at 06:46:53PM -0700, Stefano Stabellini wrote:
> +curl -fsSLO
> http://http.us.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/vmlinuz
> +curl -fsSLO
> http://http.us.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/initrd.
flight 168680 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168680/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
This serie introduces a feature for Xen to create cpu pools at boot time, the
feature is enabled using a configurable that is disabled by default.
The boot time cpupool feature relies on the device tree to describe the cpu
pools.
Another feature is introduced by the serie, the possibility to assign
Add a static function to retrieve the scheduler pointer using the
scheduler name.
Add a public function to retrieve the scheduler id by the scheduler
name that makes use of the new static function.
Take the occasion to replace open coded scheduler search with the
new static function in scheduler_
Create new public function to create cpupools, can take as parameter
the scheduler id or a negative value that means the default Xen
scheduler will be used.
Signed-off-by: Luca Fancellu
---
Changes in v3:
- Fixed comment (Andrew)
Changes in v2:
- cpupool_create_pool doesn't check anymore for pool
Currently cpupool0 can use only the default scheduler, and
cpupool_create has an hardcoded behavior when creating the pool 0
that doesn't allocate new memory for the scheduler, but uses the
default scheduler structure in memory.
With this commit it is possible to allocate a different scheduler for
Introduce a way to create different cpupools at boot time, this is
particularly useful on ARM big.LITTLE system where there might be the
need to have different cpupools for each type of core, but also
systems using NUMA can have different cpu pools for each node.
The feature on arm relies on a spe
Introduce domain-cpupool property of a xen,domain device tree node,
that specifies the cpupool device tree handle of a xen,cpupool node
that identifies a cpupool created at boot time where the guest will
be assigned on creation.
Add member to the xen_domctl_createdomain public interface so the
XEN
With the introduction of boot time cpupools, Xen can create many
different cpupools at boot time other than cpupool with id 0.
Since these newly created cpupools can't have an
entry in Xenstore, create the entry using xen-init-dom0
helper with the usual convention: Pool-.
Given the change, remove
From: Juergen Gross
> Sent: 18 March 2022 15:10
>
> The dcdbas driver is used to call SMI handlers for both, dcdbas and
> dell-smbios-smm. Both drivers allocate a buffer for communicating
> with the SMI handler. The physical buffer address is then passed to
> the called SMI handler via %ebx.
>
>
On Wed, Mar 16, 2022 at 06:46:52PM -0700, Stefano Stabellini wrote:
> +qemu-system-aarch64-6.0.0-arm32-export:
> + stage: build
> + image:
> registry.gitlab.com/xen-project/xen/tests-artifacts/qemu-system-aarch64:6.0.0-arm64v8
> + script:
> +- mkdir binaries && cp /qemu-system-arm binaries/
The dcdbas driver is used to call SMI handlers for both, dcdbas and
dell-smbios-smm. Both drivers allocate a buffer for communicating
with the SMI handler. The physical buffer address is then passed to
the called SMI handler via %ebx.
Unfortunately this doesn't work when running in Xen dom0, as th
On Wed, Mar 16, 2022 at 06:38:53PM -0700, Stefano Stabellini wrote:
> Also considering the recent arm32 xen breakage, which could have been
> caught by gitlab-ci before commit,
I'm not sure that's true. I think the commits you are speaking about
also break the build on x86, which was caught by the
On 09/03/2022 11:34, Juergen Gross wrote:
> XEN_SHSTK should be on per default now that it is supported officially.
> Only let the prompt depend on EXPERT.
>
> Signed-off-by: Juergen Gross
> ---
> xen/arch/x86/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/xe
flight 168674 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168674/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 6 xen-build fail in 168667 REGR. vs. 168620
Tests which are fai
flight 168679 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168679/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
> On 18 Mar 2022, at 10:37, Julia Lawall wrote:
>
> Various spelling mistakes in comments.
> Detected with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
Reviewed-by: Luca Fancellu
Cheers,
Luca
>
> ---
> arch/arm/xen/mm.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-
Hi Julien,
> -Original Message-
> From: Xen-devel On Behalf Of Julien
> Grall
> Sent: 2022年2月21日 18:22
> To: xen-devel@lists.xenproject.org
> Cc: jul...@xen.org; Julien Grall ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk
> Subject: [PATCH v3 09/19] xen/arm32: mm: Check
Various spelling mistakes in comments.
Detected with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
arch/arm/xen/mm.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/xen/mm.c b/arch/arm/xen/mm.c
index a7e54a087b80..607c1a557ccc 100644
--- a/arch/arm/xen/
flight 168678 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168678/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On 17.03.2022 20:02, Jason Andryuk wrote:
> On Thu, Mar 17, 2022 at 2:14 PM Andrew Cooper
> wrote:
>>
>> On 17/03/2022 17:52, Jason Andryuk wrote:
>>> I shut down a domU (HVM dom9 w/ Linux stubdom dom10) with a single PCI
>>> device assigned. Xen logged the following Flask denial for a second
>>
On 11.03.2022 07:11, Penny Zheng wrote:
> In case to own statically shared pages when owner domain is not
> explicitly defined, this commits propose a special domain DOMID_SHARED,
> and we assign it 0x7FF5, as one of the system domains.
>
> Statically shared memory reuses the same way of initializ
On Fri, Mar 18, 2022 at 08:46:00AM +, s...@kernel.org wrote:
> Hi Roger and Juergen,
>
>
> May I ask your opinions to this patch, please?
Sorry, I was expecting Maximilian to Ack it, but I see he is added as
SoB.
>
>
> Thanks,
> SJ
>
> On Tue, 1 Mar 2022 14:46:28 + SeongJae Park wro
Hi Julien,
> On 17 Mar 2022, at 20:32, Julien Grall wrote:
>
>
>
> On 17/03/2022 15:23, Bertrand Marquis wrote:
>> Hi Julien,
>
> Hi Bertrand,
>
>>> On 9 Mar 2022, at 11:20, Julien Grall wrote:
>>>
>>> From: Julien Grall
>>>
>>> In a follow-up patch, the base address for the common mappi
Hi Roger and Juergen,
May I ask your opinions to this patch, please?
Thanks,
SJ
On Tue, 1 Mar 2022 14:46:28 + SeongJae Park wrote:
> SeongJae is currently listed as a contact point for some blk{back,front}
> features, but he will not work for XEN for a while. This commit
> therefore upd
Variable i is being assigned a value that is never read, it is being
re-assigned later in a for-loop. The assignment is redundant and can
be removed.
Cleans up clang scan build warning:
drivers/block/xen-blkback/blkback.c:934:14: warning: Although the value
stored to 'i' is used in the enclosing e
Hi Stefano
> -Original Message-
> From: Stefano Stabellini
> Sent: Friday, March 18, 2022 10:00 AM
> To: Penny Zheng
> Cc: xen-devel@lists.xenproject.org; nd ; Stefano Stabellini
> ; Julien Grall ; Bertrand Marquis
> ; Volodymyr Babchuk
>
> Subject: Re: [PATCH v1 03/13] xen/arm: allocat
flight 168671 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168671/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
flight 168665 xen-unstable real [real]
flight 168676 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/168665/
http://logs.test-lab.xenproject.org/osstest/logs/168676/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-arm6
On 14.03.2022 04:41, Chuck Zmudzinski wrote:
> When gfx_passthru is enabled for the Intel IGD, hvmloader maps the IGD
> opregion to the guest but libxl does not grant the guest permission to
> access the mapped memory region. This results in a crash of the i915.ko
> kernel module in a Linux HVM gue
flight 168675 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168675/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
Hi Julien,
> -Original Message-
> From: Xen-devel On Behalf Of Julien
> Grall
> Sent: 2022年2月21日 18:22
> To: xen-devel@lists.xenproject.org
> Cc: jul...@xen.org; Julien Grall ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk ; Julien Grall
>
> Subject: [PATCH v3 08/19] xen/
71 matches
Mail list logo
