Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Sergey Dyasli
After printing some debug information I see that: SMP alternatives: switching to SMP code (XEN) [1.473056] == d1v1 master_cpu 0, lock 83018e315ec8 (XEN) [1.473120] sched_null.c:344: 1 <-- d1v1 (XEN) [1.473165] == d1v1 master_cpu 1, lock 8301899c2f48 (XEN) [1.473223] Asserti

[Xen-devel] [ovmf test] 143013: all pass - PUSHED

2019-10-22 Thread osstest service owner
flight 143013 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/143013/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf f413d9bee3f6cabd4b11ad0a1ab9ff865092fb16 baseline version: ovmf 61bb6eeb4d93c0a34c199

Re: [Xen-devel] [PATCH v2 03/20] piix4: Add a i8259 Interrupt Controller as specified in datasheet

2019-10-22 Thread Esteban Bosse
El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > From: Hervé Poussineau > > Add ISA irqs as piix4 gpio in, and CPU interrupt request as piix4 > gpio out. > Remove i8259 instanciated in malta board, to not have it twice. > > We can also remove the now unused piix4_init() f

Re: [Xen-devel] [PATCH v2 03/20] piix4: Add a i8259 Interrupt Controller as specified in datasheet

2019-10-22 Thread Esteban Bosse
El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > From: Hervé Poussineau > > Add ISA irqs as piix4 gpio in, and CPU interrupt request as piix4 > gpio out. > Remove i8259 instanciated in malta board, to not have it twice. > > We can also remove the now unused piix4_init() f

Re: [Xen-devel] [PATCH v2 04/20] Revert "irq: introduce qemu_irq_proxy()"

2019-10-22 Thread Esteban Bosse
El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > From: Philippe Mathieu-Daudé > > This function isn't used anymore. > > This reverts commit 22ec3283efba9ba0792790da786d6776d83f2a92. > > Reviewed-by: Thomas Huth > Signed-off-by: Philippe Mathieu-Daudé > --- > hw/core/i

Re: [Xen-devel] [PATCH v2 05/20] piix4: Rename PIIX4 object to piix4-isa

2019-10-22 Thread Esteban Bosse
El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > From: Hervé Poussineau > > Other piix4 parts are already named piix4-ide and piix4-usb-uhci. > > Reviewed-by: Philippe Mathieu-Daudé > Acked-by: Michael S. Tsirkin > Acked-by: Paolo Bonzini > Signed-off-by: Hervé Poussin

Re: [Xen-devel] [PATCH v2 06/20] piix4: Add a i8257 DMA Controller as specified in datasheet

2019-10-22 Thread Esteban Bosse
El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > From: Hervé Poussineau > > Remove i8257 instantiated in malta board, to not have it twice. > > Acked-by: Michael S. Tsirkin > Acked-by: Paolo Bonzini > Signed-off-by: Hervé Poussineau > Message-Id: <20171216090228.28505-

Re: [Xen-devel] [PATCH v2 03/20] piix4: Add a i8259 Interrupt Controller as specified in datasheet

2019-10-22 Thread Philippe Mathieu-Daudé
On 10/22/19 10:48 AM, Esteban Bosse wrote: El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: From: Hervé Poussineau Add ISA irqs as piix4 gpio in, and CPU interrupt request as piix4 gpio out. Remove i8259 instanciated in malta board, to not have it twice. We can also remo

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Jürgen Groß
On 21.10.19 11:51, Sergey Dyasli wrote: Hello, While testing pv-shim from a snapshot of staging 4.13 branch (with core- scheduling patches applied), some sort of scheduling issues were uncovered which usually leads to a guest lockup (sometimes with soft lockup messages from Linux kernel). This

Re: [Xen-devel] [PATCH v2 03/20] piix4: Add a i8259 Interrupt Controller as specified in datasheet

2019-10-22 Thread Philippe Mathieu-Daudé
On 10/22/19 10:44 AM, Esteban Bosse wrote: El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: From: Hervé Poussineau Add ISA irqs as piix4 gpio in, and CPU interrupt request as piix4 gpio out. Remove i8259 instanciated in malta board, to not have it twice. We can also remo

Re: [Xen-devel] [PATCH v2 13/20] hw/pci-host/piix: Extract piix3_create()

2019-10-22 Thread Esteban Bosse
El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > Extract the PIIX3 creation code from the i440fx_init() function. > > Reviewed-by: Aleksandar Markovic > Signed-off-by: Philippe Mathieu-Daudé > --- > hw/pci-host/piix.c | 51 -- > ---

Re: [Xen-devel] [PATCH v2 03/20] piix4: Add a i8259 Interrupt Controller as specified in datasheet

2019-10-22 Thread Peter Maydell
On Tue, 22 Oct 2019 at 09:52, Esteban Bosse wrote: > > El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > > +static void piix4_request_i8259_irq(void *opaque, int irq, int > > level) > > +{ > > +PIIX4State *s = opaque; > > +qemu_set_irq(s->cpu_intr, level); > > +} > I

Re: [Xen-devel] [PATCH v2 17/20] hw/pci-host/piix: Fix code style issues

2019-10-22 Thread Esteban Bosse
El vie, 18-10-2019 a las 15:47 +0200, Philippe Mathieu-Daudé escribió: > We will move this code, fix its style first. > > Reviewed-by: Aleksandar Markovic > Signed-off-by: Philippe Mathieu-Daudé > --- > hw/pci-host/piix.c | 7 --- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff

Re: [Xen-devel] [PATCH v2 03/20] piix4: Add a i8259 Interrupt Controller as specified in datasheet

2019-10-22 Thread Aleksandar Markovic
On Friday, October 18, 2019, Philippe Mathieu-Daudé wrote: > From: Hervé Poussineau > > Add ISA irqs as piix4 gpio in, and CPU interrupt request as piix4 gpio out. > Remove i8259 instanciated in malta board, to not have it twice. > > We can also remove the now unused piix4_init() function. > > A

Re: [Xen-devel] [PATCH v2 03/20] piix4: Add a i8259 Interrupt Controller as specified in datasheet

2019-10-22 Thread Philippe Mathieu-Daudé
On 10/22/19 11:53 AM, Aleksandar Markovic wrote: On Friday, October 18, 2019, Philippe Mathieu-Daudé > wrote: From: Hervé Poussineau mailto:hpous...@reactos.org>> Add ISA irqs as piix4 gpio in, and CPU interrupt request as piix4 gpio out. Remove i825

[Xen-devel] [linux-linus test] 143006: regressions - FAIL

2019-10-22 Thread osstest service owner
flight 143006 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/143006/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-examine 8 reboot fail REGR. vs. 133580 test-amd64-i386-lib

Re: [Xen-devel] [PATCH for-4.13 v3] xen/arm: domain_build: Don't expose IOMMU specific properties to hwdom

2019-10-22 Thread Oleksandr
Hi all Gentle reminder... -- Regards, Oleksandr Tyshchenko ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Roger Pau Monné
On Tue, Oct 22, 2019 at 11:27:41AM +0200, Jürgen Groß wrote: > On 21.10.19 11:51, Sergey Dyasli wrote: > > Hello, > > > > While testing pv-shim from a snapshot of staging 4.13 branch (with core- > > scheduling patches applied), some sort of scheduling issues were uncovered > > which usually leads

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Jürgen Groß
On 22.10.19 12:52, Roger Pau Monné wrote: On Tue, Oct 22, 2019 at 11:27:41AM +0200, Jürgen Groß wrote: On 21.10.19 11:51, Sergey Dyasli wrote: Hello, While testing pv-shim from a snapshot of staging 4.13 branch (with core- scheduling patches applied), some sort of scheduling issues were uncove

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Andrew Cooper
On 22/10/2019 12:01, Jürgen Groß wrote: > On 22.10.19 12:52, Roger Pau Monné wrote: >> On Tue, Oct 22, 2019 at 11:27:41AM +0200, Jürgen Groß wrote: >>> On 21.10.19 11:51, Sergey Dyasli wrote: Hello, While testing pv-shim from a snapshot of staging 4.13 branch (with core- sc

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Roger Pau Monné
On Tue, Oct 22, 2019 at 01:01:09PM +0200, Jürgen Groß wrote: > On 22.10.19 12:52, Roger Pau Monné wrote: > > On Tue, Oct 22, 2019 at 11:27:41AM +0200, Jürgen Groß wrote: > > > On 21.10.19 11:51, Sergey Dyasli wrote: > > > > Hello, > > > > > > > > While testing pv-shim from a snapshot of staging 4.

Re: [Xen-devel] [PATCH for-4.13 v3] xen/arm: domain_build: Don't expose IOMMU specific properties to hwdom

2019-10-22 Thread Julien Grall
Hi Oleksandr, On 22/10/2019 11:27, Oleksandr wrote: Gentle reminder... This is in my queue of patches to review. But I have been focusing on more urgent tasks the past week. I will try to review it by the end of the week. Cheers, -- Julien Grall __

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Jürgen Groß
On 22.10.19 13:25, Roger Pau Monné wrote: On Tue, Oct 22, 2019 at 01:01:09PM +0200, Jürgen Groß wrote: On 22.10.19 12:52, Roger Pau Monné wrote: On Tue, Oct 22, 2019 at 11:27:41AM +0200, Jürgen Groß wrote: On 21.10.19 11:51, Sergey Dyasli wrote: Hello, While testing pv-shim from a snapshot o

[Xen-devel] [PATCH] xen: mm: include for missing declarations

2019-10-22 Thread Ben Dooks (Codethink)
Include for xen_{create,destroy}_contigous_region call declarations. Fixes the following sparse warnings: arch/arm/xen/mm.c:119:5: warning: symbol 'xen_create_contiguous_region' was not declared. Should it be static? arch/arm/xen/mm.c:131:6: warning: symbol 'xen_destroy_contiguous_region' was n

[Xen-devel] [PATCH] xen: mm: make xen_mm_init static

2019-10-22 Thread Ben Dooks (Codethink)
The xen_mm_init is not exported or used outside of the file it is declared in, so make it static. This fixes the following sparse warning: arch/arm/xen/mm.c:136:12: warning: symbol 'xen_mm_init' was not declared. Should it be static? Signed-off-by: Ben Dooks (Codethink) --- Cc: Stefano Stabelli

[Xen-devel] laxton0 PDU port issue blocked/broken/fail/pass

2019-10-22 Thread Ian Jackson
osstest service owner writes ("[osstest test] 143010: regressions - trouble: blocked/broken/fail/pass"): > flight 143010 osstest real [real] > http://logs.test-lab.xenproject.org/osstest/logs/143010/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which co

[Xen-devel] [libvirt test] 143023: tolerable all pass - PUSHED

2019-10-22 Thread osstest service owner
flight 143023 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/143023/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 142840 test-armhf-armhf-libvirt-raw 13 saveresto

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Roger Pau Monné
On Tue, Oct 22, 2019 at 01:50:44PM +0200, Jürgen Groß wrote: > On 22.10.19 13:25, Roger Pau Monné wrote: > > On Tue, Oct 22, 2019 at 01:01:09PM +0200, Jürgen Groß wrote: > > > On 22.10.19 12:52, Roger Pau Monné wrote: > > > > On Tue, Oct 22, 2019 at 11:27:41AM +0200, Jürgen Groß wrote: > > > > > Si

Re: [Xen-devel] PV-shim 4.13 assertion failures during vcpu_wake()

2019-10-22 Thread Jürgen Groß
On 22.10.19 15:50, Roger Pau Monné wrote: On Tue, Oct 22, 2019 at 01:50:44PM +0200, Jürgen Groß wrote: On 22.10.19 13:25, Roger Pau Monné wrote: On Tue, Oct 22, 2019 at 01:01:09PM +0200, Jürgen Groß wrote: On 22.10.19 12:52, Roger Pau Monné wrote: On Tue, Oct 22, 2019 at 11:27:41AM +0200, Jür

[Xen-devel] [xen-unstable test] 143018: regressions - FAIL

2019-10-22 Thread osstest service owner
flight 143018 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/143018/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-pvopsbroken in 142997 build-arm64-pvops 4 h

Re: [Xen-devel] [PATCH] xen: mm: include for missing declarations

2019-10-22 Thread Stefano Stabellini
On Tue, 22 Oct 2019, Stefano Stabellini wrote: > On Tue, 22 Oct 2019, Ben Dooks (Codethink) wrote: > > Include for xen_{create,destroy}_contigous_region > > call declarations. Fixes the following sparse warnings: > > > > arch/arm/xen/mm.c:119:5: warning: symbol 'xen_create_contiguous_region' was

[Xen-devel] [PATCH RFC v1 00/12] mm: Don't mark hotplugged pages PG_reserved (including ZONE_DEVICE)

2019-10-22 Thread David Hildenbrand
This series is based on [2], which should pop up in linux/next soon: https://lkml.org/lkml/2019/10/21/1034 This is the result of a recent discussion with Michal ([1], [2]). Right now we set all pages PG_reserved when initializing hotplugged memmaps. This includes ZONE_DEVICE memory. In cas

[Xen-devel] [PATCH RFC v1 02/12] mm/usercopy.c: Prepare check_page_span() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. Let's make sure that the logic in the function won't change. Once we no longer set these pages to reserved, we can rework this function to perform separate checks for ZONE_DEVICE (split from PG_reserved checks). Cc:

[Xen-devel] [PATCH RFC v1 03/12] KVM: x86/mmu: Prepare kvm_is_mmio_pfn() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use case that you can map anything from /dev/mem into the guest. pfn_valid() is not a reliable check whether the memmap was initialized and can be touched. pfn_to_online_page() makes sure that we ha

[Xen-devel] [PATCH RFC v1 05/12] vfio/type1: Prepare is_invalid_reserved_pfn() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use case that you can map anything from /dev/mem into the guest. pfn_valid() is not a reliable check whether the memmap was initialized and can be touched. pfn_to_online_page() makes sure that we ha

[Xen-devel] [PATCH RFC v1 04/12] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use case that you can map anything from /dev/mem into the guest. pfn_valid() is not a reliable check whether the memmap was initialized and can be touched. pfn_to_online_page() makes sure that we ha

[Xen-devel] [PATCH RFC v1 06/12] staging/gasket: Prepare gasket_release_page() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. The pages are obtained via get_user_pages_fast(). I assume, these could be ZONE_DEVICE pages. Let's just exclude them as well explicitly. Cc: Rob Springer Cc: Todd Poynor Cc: Ben Chan Cc: Greg Kroah-Hartman Signe

[Xen-devel] [PATCH RFC v1 08/12] powerpc/book3s: Prepare kvmppc_book3s_instantiate_page() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use case that you can map anything from /dev/mem into the guest. pfn_valid() is not a reliable check whether the memmap was initialized and can be touched. pfn_to_online_page() makes sure that we ha

[Xen-devel] [PATCH RFC v1 12/12] mm/memory_hotplug: Don't mark pages PG_reserved when initializing the memmap

2019-10-22 Thread David Hildenbrand
Everything should be prepared to stop setting pages PG_reserved when initializing the memmap on memory hotplug. Most importantly, we stop marking ZONE_DEVICE pages PG_reserved. a) We made sure that any code that relied on PG_reserved to detect ZONE_DEVICE memory will no longer rely on PG_reserv

Re: [Xen-devel] [PATCH] xen: mm: include for missing declarations

2019-10-22 Thread Stefano Stabellini
On Tue, 22 Oct 2019, Ben Dooks (Codethink) wrote: > Include for xen_{create,destroy}_contigous_region > call declarations. Fixes the following sparse warnings: > > arch/arm/xen/mm.c:119:5: warning: symbol 'xen_create_contiguous_region' was > not declared. Should it be static? > arch/arm/xen/mm.c

Re: [Xen-devel] [PATCH] xen: mm: make xen_mm_init static

2019-10-22 Thread Stefano Stabellini
On Tue, 22 Oct 2019, Ben Dooks (Codethink) wrote: > The xen_mm_init is not exported or used outside of the file > it is declared in, so make it static. This fixes the following > sparse warning: > > arch/arm/xen/mm.c:136:12: warning: symbol 'xen_mm_init' was not declared. > Should it be static? >

[Xen-devel] [PATCH RFC v1 01/12] mm/memory_hotplug: Don't allow to online/offline memory blocks with holes

2019-10-22 Thread David Hildenbrand
Our onlining/offlining code is unnecessarily complicated. Only memory blocks added during boot can have holes. Hotplugged memory never has holes. That memory is already online. When we stop allowing to offline memory blocks with holes, we implicitly stop to online memory blocks with holes. This a

[Xen-devel] [PATCH RFC v1 11/12] x86/mm: Prepare __ioremap_check_ram() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. We could explicitly check for is_zone_device_page(page). But looking at the pfn_valid() check, it seems safer to just use pfn_to_online_page() here, that will skip all ZONE_DEVICE pages right away. Cc: Dave Hansen C

[Xen-devel] [PATCH RFC v1 07/12] staging: kpc2000: Prepare transfer_complete_cb() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. The pages are obtained via get_user_pages_fast(). I assume, these could be ZONE_DEVICE pages. Let's just exclude them as well explicitly. Cc: Greg Kroah-Hartman Cc: Vandana BN Cc: "Simon Sandström" Cc: Dan Carpent

[Xen-devel] [PATCH RFC v1 09/12] powerpc/64s: Prepare hash_page_do_lazy_icache() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. We could explicitly check for is_zone_device_page(page). But looking at the pfn_valid() check, it seems safer to just use pfn_to_online_page() here, that will skip all ZONE_DEVICE pages right away. Cc: Benjamin Herre

[Xen-devel] [PATCH RFC v1 10/12] powerpc/mm: Prepare maybe_pte_to_page() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. We could explicitly check for is_zone_device_page(page). But looking at the pfn_valid() check, it seems safer to just use pfn_to_online_page() here, that will skip all ZONE_DEVICE pages right away. Cc: Benjamin Herre

Re: [Xen-devel] [XEN PATCH for-4.13 v1] Reset iomem's gfn to LIBXL_INVALID_GFN on reboot

2019-10-22 Thread Julien Grall
Hi Oleksandr, Apologies for the late answer. On 16/10/2019 14:09, Oleksandr Grytsov wrote: On Mon, Oct 14, 2019 at 12:28 PM Julien Grall wrote: Thanks to point me out for this old thread. I completely forgot about it (I haven't worked with xen since long time). I've performed additional invest

[Xen-devel] [xen-unstable-smoke test] 143034: trouble: blocked/broken/pass

2019-10-22 Thread osstest service owner
flight 143034 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/143034/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm broken build-arm64-xs

Re: [Xen-devel] [PATCH] xen/netback: cleanup init and deinit code

2019-10-22 Thread Jakub Kicinski
On Mon, 21 Oct 2019 07:30:52 +0200, Juergen Gross wrote: > Do some cleanup of the netback init and deinit code: > > - add an omnipotent queue deinit function usable from > xenvif_disconnect_data() and the error path of xenvif_connect_data() > - only install the irq handlers after initializing al

[Xen-devel] [linux-4.4 test] 143025: regressions - trouble: broken/fail/pass

2019-10-22 Thread osstest service owner
flight 143025 linux-4.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/143025/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-xl-credit1 broken test-amd64-amd64-xl-pvshim 18 guest-localmig

Re: [Xen-devel] [PATCH RFC v1 07/12] staging: kpc2000: Prepare transfer_complete_cb() for PG_reserved changes

2019-10-22 Thread David Hildenbrand
On 22.10.19 19:55, Matt Sickler wrote: Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. The pages are obtained via get_user_pages_fast(). I assume, these could be ZONE_DEVICE pages. Let's just exclude them as well explicitly. I'm not sure what ZONE_DEVICE pages

Re: [Xen-devel] [PATCH RFC v1 00/12] mm: Don't mark hotplugged pages PG_reserved (including ZONE_DEVICE)

2019-10-22 Thread Dan Williams
Hi David, Thanks for tackling this! On Tue, Oct 22, 2019 at 10:13 AM David Hildenbrand wrote: > > This series is based on [2], which should pop up in linux/next soon: > https://lkml.org/lkml/2019/10/21/1034 > > This is the result of a recent discussion with Michal ([1], [2]). Right > now

[Xen-devel] [xen-unstable-smoke test] 143041: tolerable all pass - PUSHED

2019-10-22 Thread osstest service owner
flight 143041 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/143041/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass test-arm64-arm64-xl-xsm 1

[Xen-devel] [linux-linus bisection] complete test-amd64-i386-xl-qemuu-ws16-amd64

2019-10-22 Thread osstest service owner
branch xen-unstable xenbranch xen-unstable job test-amd64-i386-xl-qemuu-ws16-amd64 testid xen-boot Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git

[Xen-devel] [qemu-mainline test] 143030: trouble: broken/fail/pass

2019-10-22 Thread osstest service owner
flight 143030 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/143030/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-xl-credit1 broken test-arm64-arm64-xl

[Xen-devel] [ovmf test] 143039: all pass - PUSHED

2019-10-22 Thread osstest service owner
flight 143039 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/143039/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 46bb81200742fabfe5c5624c22e72f036af02869 baseline version: ovmf f413d9bee3f6cabd4b11a

Re: [Xen-devel] [PATCH RFC v1 07/12] staging: kpc2000: Prepare transfer_complete_cb() for PG_reserved changes

2019-10-22 Thread Matt Sickler
>Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change >that. > >The pages are obtained via get_user_pages_fast(). I assume, these could be >ZONE_DEVICE pages. Let's just exclude them as well explicitly. I'm not sure what ZONE_DEVICE pages are, but these pages are normal sys