On 24.05.2021 16:34, Connor Davis wrote:
> Defaulting to yes only for X86 and ARM reduces the requirements
> for a minimal build when porting new architectures.
>
> Signed-off-by: Connor Davis
> Reviewed-by: Alistair Francis
Acked-by: Jan Beulich
On 25.05.2021 09:02, Jan Beulich wrote:
> On 24.05.2021 16:34, Connor Davis wrote:
>> Defaulting to yes only for X86 and ARM reduces the requirements
>> for a minimal build when porting new architectures.
>>
>> Signed-off-by: Connor Davis
>> Reviewed-by: Alistair Francis
>
> Acked-by: Jan Beulic
On 12.05.21 08:58, Juergen Gross wrote:
Ping?
Now each patch has an Ack by Wei. Could the series be either applied or
get more comments, please?
Juergen
On 12.04.21 17:22, Juergen Gross wrote:
There are some corners left which don't support the not so very new
linear p2m list of pv guests
On 24.05.2021 16:34, Connor Davis wrote:
> The variables iommu_enabled and iommu_dont_flush_iotlb are defined in
> drivers/passthrough/iommu.c and are referenced in common code, which
> causes the link to fail when !CONFIG_HAS_PASSTHROUGH.
>
> Guard references to these variables in common code so
On 24.05.2021 16:34, Connor Davis wrote:
> Add arch-specific makefiles and configs needed to build for
> riscv. Also add a minimal head.S that is a simple infinite loop.
> head.o can be built with
>
> $ make XEN_TARGET_ARCH=riscv SUBSYSTEMS=xen -C xen tiny64_defconfig
> $ make XEN_TARGET_ARCH=risc
On 24.05.2021 06:29, Roberto Bagnara wrote:
> I stumbled upon parsing errors due to invalid uses of
> _Static_assert expanded from HASH_CALLBACKS_CHECK where
> the tested expression is not constant, as mandated by
> the C standard.
>
> Judging from the following comment, there is partial awareness
On 24/05/2021 15:34, Connor Davis wrote:
> Add a container for cross-compiling xen to riscv64.
> This just includes the cross-compiler and necessary packages for
> building xen itself (packages for tools, stubdoms, etc., can be
> added later).
>
> Signed-off-by: Connor Davis
I've deployed this ve
flight 162147 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162147/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-armhf-libvirt
flight 162145 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162145/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 162137
test-armhf-armhf-libvirt 16 save
flight 162149 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162149/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
On 30.04.2021 16:39, Jan Beulich wrote:
> Originally I meant to finally get v2 of "firmware/shim: honor symlinks
> during Xen tree setup" sorted. However, the suggestion to use find's
> -L option, while a suitable equivalent of the -xtype primary, has the
> same drawback: It doesn't distinguish bet
On 26.04.2021 11:54, Jan Beulich wrote:
> The original commit wasn't quite sufficient: Emptying DEPS is helpful
> only when nothing will get added to it subsequently. xen/Rules.mk will,
> after including the local Makefile, amend DEPS by dependencies for
> objects living in sub-directories though.
The commit referenced below still wasn't careful enough - with COMPAT we
will have a compat_handle_okay() visible already, which we first need to
get rid of.
Fixes: bd1e7b47bac0 ("x86/shim: fix build when !PV32")
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/pv/shim.c
+++ b/xen/arch/x86/pv/shim.
flight 162151 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162151/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
On Fri, Apr 30, 2021 at 04:43:59PM +0200, Jan Beulich wrote:
> Some intermediate files weren't considered at all at the time. Also
> after its introduction, various changes to the build environment have
> rendered the exclusion sets stale. For example, we now have some .*.cmd
> files in the build t
On Fri, Apr 30, 2021 at 04:44:21PM +0200, Jan Beulich wrote:
> As of commit d155e4aef35c ("xen: Allow EXPERT mode to be selected from
> the menuconfig directly") EXPERT is a regular config option.
Might be worth mentioning that the default pvshim config already have
EXPERT selected.
> Signed-off-
On Fri, Apr 30, 2021 at 04:45:03PM +0200, Jan Beulich wrote:
> We shouldn't default to include any unsupported code in the shim. Mark
> the setting as off, replacing the ARGO specification. This points out
> anomalies with the scheduler configuration: Unsupported schedulers
> better don't default t
On Tue, May 25, 2021 at 03:20:56PM +0200, Jan Beulich wrote:
> The commit referenced below still wasn't careful enough - with COMPAT we
> will have a compat_handle_okay() visible already, which we first need to
> get rid of.
>
> Fixes: bd1e7b47bac0 ("x86/shim: fix build when !PV32")
> Signed-off-b
flight 162146 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162146/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-freebsd11-amd64 16 guest-saverestore fail REGR. vs.
152631
test-amd64-i3
On 25.05.2021 16:14, Roger Pau Monné wrote:
> On Fri, Apr 30, 2021 at 04:44:21PM +0200, Jan Beulich wrote:
>> As of commit d155e4aef35c ("xen: Allow EXPERT mode to be selected from
>> the menuconfig directly") EXPERT is a regular config option.
>
> Might be worth mentioning that the default pvshim
On 25.05.2021 16:39, Roger Pau Monné wrote:
> On Fri, Apr 30, 2021 at 04:45:03PM +0200, Jan Beulich wrote:
>> We shouldn't default to include any unsupported code in the shim. Mark
>> the setting as off, replacing the ARGO specification. This points out
>> anomalies with the scheduler configuration
On Tue, May 25, 2021 at 05:21:43PM +0200, Jan Beulich wrote:
> On 25.05.2021 16:39, Roger Pau Monné wrote:
> > On Fri, Apr 30, 2021 at 04:45:03PM +0200, Jan Beulich wrote:
> >> @@ -31,7 +31,7 @@ config SCHED_ARINC653
> >>
> >> config SCHED_NULL
> >>bool "Null scheduler support (UNSUPPORTED)"
On 25.05.2021 17:51, Roger Pau Monné wrote:
> On Tue, May 25, 2021 at 05:21:43PM +0200, Jan Beulich wrote:
>> On 25.05.2021 16:39, Roger Pau Monné wrote:
>>> On Fri, Apr 30, 2021 at 04:45:03PM +0200, Jan Beulich wrote:
@@ -31,7 +31,7 @@ config SCHED_ARINC653
config SCHED_NULL
On Fri, May 21, 2021 at 04:09:13PM +0200, Noralf Trønnes wrote:
>
>
> Den 21.05.2021 11.09, skrev Daniel Vetter:
> > Goes through all the drivers and deletes the default hook since it's
> > the default now.
> >
> > Signed-off-by: Daniel Vetter
>
> Acked-by: Noralf Trønnes
Can you perhaps als
On 5/25/21 1:48 AM, Jan Beulich wrote:
> On 24.05.2021 16:34, Connor Davis wrote:
>> Add arch-specific makefiles and configs needed to build for
>> riscv. Also add a minimal head.S that is a simple infinite loop.
>> head.o can be built with
>>
>> $ make XEN_TARGET_ARCH=riscv SUBSYSTEMS=xen -C xen t
flight 162148 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162148/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow 7 xen-install fail REGR. vs.
152332
test-amd64-i3
On 5/21/21 1:26 AM, Anchal Agarwal wrote:
>>> What I meant there wrt VCPU info was that VCPU info is not unregistered
>>> during hibernation,
>>> so Xen still remembers the old physical addresses for the VCPU information,
>>> created by the
>>> booting kernel. But since the hibernation kernel m
flight 162150 xen-unstable real [real]
flight 162154 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/162150/
http://logs.test-lab.xenproject.org/osstest/logs/162154/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be r
flight 162152 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162152/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-freebsd11-amd64 16 guest-saverestore fail REGR. vs.
152631
test-amd64-i3
flight 162153 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162153/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow 7 xen-install fail REGR. vs.
152332
test-amd64-i3
On Tue, May 25, 2021 at 06:23:35PM -0400, Boris Ostrovsky wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
>
>
>
> On 5/21/21 1:26 AM, Anchal Agarwal wrote:
> >>>
flight 162159 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162159/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-armhf-libvirt
32 matches
Mail list logo
