[ovmf test] 183733: all pass - PUSHED

2023-11-11 Thread osstest service owner
flight 183733 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/183733/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 33deaa3b845f0d588ffd068003558be46f90aaac baseline version: ovmf 589f2e49e5f9ff998bd4f

[linux-linus test] 183731: tolerable FAIL - PUSHED

2023-11-11 Thread osstest service owner
flight 183731 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/183731/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 183728 test-amd64-amd64-xl-qemuu-win7-amd64

Re: [PATCH v2 06/15] xen/asm-generic: ifdef inclusion of

2023-11-11 Thread Oleksii
This patch should be reworked as it fails Arm builds: https://gitlab.com/xen-project/people/olkur/xen/-/pipelines/1068867920 It looks like it is not possible just to #ifdef CONFIG_MEM_ACCESS. An empty asm-generic mem_access.h will be better solution. Could you please share your opinion? ~ Oleks

Re: [PATCH v2 03/15] xen: ifdef inclusion of in

2023-11-11 Thread Oleksii
I missed to check the patch properly. The patch fails for Arm randconfigs: https://gitlab.com/xen-project/people/olkur/xen/-/pipelines/1068865674 I need to do an additional investigation. Does it make sense to re-send this patch separately out of this patch series? ~ Oleksii On Fri, 2023-11-10

Re: [PATCH v1 1/7] xen-block: Do not write frontend nodes

2023-11-11 Thread David Woodhouse
On Fri, 2023-11-10 at 20:42 +, Volodymyr Babchuk wrote: > From: Oleksandr Tyshchenko > > The PV backend running in other than Dom0 domain (non toolstack domain) > is not allowed to write frontend nodes. The more, the backend does not > need to do that at all, this is purely toolstack/xl devd

Re: [PATCH v1 3/7] xen: xenstore: add possibility to preserve owner

2023-11-11 Thread David Woodhouse
On Fri, 2023-11-10 at 20:42 +, Volodymyr Babchuk wrote: > Add option to preserve owner when creating an entry in Xen Store. This > may be needed in cases when Qemu is working as device model in a > domain that is Domain-0, e.g. in driver domain. > > "owner" parameter for qemu_xen_xs_create() f

Re: [PATCH v1 5/7] xen-bus: Set offline if backend's state is XenbusStateClosed

2023-11-11 Thread David Woodhouse
(When sending a series, if you Cc someone on one message please could you Cc them on the whole thread for context? Thanks.) > Both state (XenbusStateClosed) and online (0) are expected by > toolstack/xl devd to completely destroy the device. But "offline" > is never being set by the backend resul

[xen-unstable test] 183732: regressions - trouble: blocked/broken/fail/pass

2023-11-11 Thread osstest service owner
flight 183732 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/183732/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-libvirt broken build-armhf-libvirt 4 host-inst

Re: [PATCH for-4.18 3/3] docs/sphinx: Fix indexing

2023-11-11 Thread Andrew Cooper
On 10/11/2023 11:49 pm, Stefano Stabellini wrote: > On Fri, 10 Nov 2023, Andrew Cooper wrote: >> On 10/11/2023 12:07 am, Stefano Stabellini wrote: >>> On Wed, 8 Nov 2023, Andrew Cooper wrote: diff --git a/docs/index.rst b/docs/index.rst index f3f779f89ce5..22fdde80590c 100644 --- a/d

Re: [PATCH v1 1/7] xen-block: Do not write frontend nodes

2023-11-11 Thread Andrew Cooper
On 11/11/2023 10:55 am, David Woodhouse wrote: > On Fri, 2023-11-10 at 20:42 +, Volodymyr Babchuk wrote: >> From: Oleksandr Tyshchenko >> >> The PV backend running in other than Dom0 domain (non toolstack domain) >> is not allowed to write frontend nodes. The more, the backend does not >> need

[libvirt test] 183734: tolerable FAIL - PUSHED

2023-11-11 Thread osstest service owner
flight 183734 libvirt real [real] flight 183735 libvirt real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/183734/ http://logs.test-lab.xenproject.org/osstest/logs/183735/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-arm64-arm64-li

[PATCH] arm/mm: add option to prefer IOMMU ops for DMA on Xen

2023-11-11 Thread Chuck Zmudzinski
Enabling the new option, ARM_DMA_USE_IOMMU_XEN, fixes this error when attaching the Exynos mixer in Linux dom0 on Xen on the Chromebook Snow (and probably on other devices that use the Exynos mixer): [drm] Exynos DRM: using 1440.fimd device for DMA mapping operations exynos-drm exynos-drm: bou

Re: [PATCH v1 1/7] xen-block: Do not write frontend nodes

2023-11-11 Thread David Woodhouse
On 11 November 2023 08:43:40 GMT-05:00, Andrew Cooper wrote: >Furthermore, the control domain doesn't always have the domid of 0. > >If qemu wants/needs to make changes like this, the control domain has to >arrange for qemu's domain to have appropriate permissions on the nodes. Right. And that's

Re: [PATCH v1 1/7] xen-block: Do not write frontend nodes

2023-11-11 Thread Andrew Cooper
On 11/11/2023 8:18 pm, David Woodhouse wrote: > On 11 November 2023 08:43:40 GMT-05:00, Andrew Cooper > wrote: >> Furthermore, the control domain doesn't always have the domid of 0. >> >> If qemu wants/needs to make changes like this, the control domain has to >> arrange for qemu's domain to have

Re: [PATCH v1 1/7] xen-block: Do not write frontend nodes

2023-11-11 Thread David Woodhouse
On 11 November 2023 16:51:22 GMT-05:00, Andrew Cooper wrote: >On 11/11/2023 8:18 pm, David Woodhouse wrote: >> On 11 November 2023 08:43:40 GMT-05:00, Andrew Cooper >> wrote: >>> Furthermore, the control domain doesn't always have the domid of 0. >>> >>> If qemu wants/needs to make changes like