[Xen-devel] [xen-4.5-testing test] 65555: trouble: broken/fail/pass

flight 6 xen-4.5-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/6/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs.

[Xen-devel] [xen-4.3-testing test] 65554: regressions - trouble: blocked/broken/fail/pass

flight 65554 xen-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/65554/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-winxpsp3 3 host-install(3) broken REGR. vs. 64765 build-armhf

Re: [Xen-devel] [xen-unstable test] 65141: regressions - FAIL

On Tue, 2015-12-08 at 10:29 +, Ian Campbell wrote: > On Tue, 2015-12-08 at 08:06 +, Hu, Robert wrote: > > > > > [...] > > Please trim your quotes. > > > For your failure, as Kevin mentioned in other mail, we will find someone > > to look into. > > Would you find out the detailed log of

[Xen-devel] [qemu-mainline baseline-only test] 38466: trouble: broken/fail/pass

This run is configured for baseline tests only. flight 38466 qemu-mainline real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38466/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run:

[Xen-devel] [ovmf baseline-only test] 38467: all pass

This run is configured for baseline tests only. flight 38467 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38467/ Perfect :-) All tests in this flight passed version targeted for testing: ovmf 5ac96e3a28dd26eabee421919f67fa7c443a47f1 baseline version:

[Xen-devel] [PATCH v2] xen_pt: fix failure of attaching & detaching a PCI device to VM repeatedly

Add pci = [ '$VF_BDF1', '$VF_BDF2', '$VF_BDF3'] in hvm guest configuration file. After the guest boot up, detach the VFs in sequence by "xl pci-detach $DOMID $VF_BDF1" "xl pci-detach $DOMID $VF_BDF2" "xl pci-detach $DOMID $VF_BDF3" and reattach the VFs in sequence by "xl pci-attach $DOMID

Re: [Xen-devel] [PATCH 10/14] crashdump/ppc: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on ppc arch even > if the functionality is not available on it. The functionality is available by reading device tree nodes in procfs.. > >

Re: [Xen-devel] [PATCH 11/14] crashdump/ppc64: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on ppc64 arch even > if the functionality is not available on it. Ditto as ppc, you can read procfs file to get the values.. > > Signed-off-by: Daniel

Re: [Xen-devel] [PATCH 06/14] crashdump/cris: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on cris arch even > if the functionality is not available on it. > > Signed-off-by: Daniel Kiper > --- >

Re: [Xen-devel] xenstore domain

On 08/12/15 17:34, Andrew Cooper wrote: > On 08/12/15 16:02, Juergen Gross wrote: >> On 08/12/15 16:04, Andrew Cooper wrote: >>> On 08/12/15 14:44, Juergen Gross wrote: I'm just playing a little bit with xenstore in an own domain. I've come across some questions I'd like to have

Re: [Xen-devel] [PATCHv1] x86: rtc_cmos platform device requires legacy irqs

On 12/08/2015 04:02 PM, Thomas Gleixner wrote: On Fri, 4 Dec 2015, David Vrabel wrote: On 04/12/15 14:06, David Vrabel wrote: On 03/12/15 10:43, David Vrabel wrote: Adding the rtc platform device when there are no legacy irqs (no legacy PIC) causes a conflict with other devices that end up

Re: [Xen-devel] [PATCHv1] x86: rtc_cmos platform device requires legacy irqs

On Tue, 8 Dec 2015, Boris Ostrovsky wrote: > On 12/08/2015 04:02 PM, Thomas Gleixner wrote: > > > > --- a/arch/x86/kernel/rtc.c > > > > +++ b/arch/x86/kernel/rtc.c > > > > @@ -200,6 +200,9 @@ static __init int add_rtc_cmos(void) > > > > } > > > > #endif > > > > + if

[Xen-devel] [PATCH 06/14] crashdump/cris: Add print_crashkernel_region_size() function

Provide just print_crashkernel_region_size() stub. This way we can properly build kexec utility on cris arch even if the functionality is not available on it. Signed-off-by: Daniel Kiper --- kexec/arch/cris/kexec-cris.c |5 + 1 file changed, 5 insertions(+)

[Xen-devel] [PATCH 11/14] crashdump/ppc64: Add print_crashkernel_region_size() function

Provide just print_crashkernel_region_size() stub. This way we can properly build kexec utility on ppc64 arch even if the functionality is not available on it. Signed-off-by: Daniel Kiper --- kexec/arch/ppc64/crashdump-ppc64.c |5 + 1 file changed, 5

[Xen-devel] [PATCH 00/14] kexec: Add option to get crash kernel region size

Crash kernel region size is available via sysfs on Linux running on bare metal. However, this does not work when Linux runs as Xen dom0. In this case Xen crash kernel region size should be established using __HYPERVISOR_kexec_op hypercall (Linux kernel kexec functionality does not make a lot of

[Xen-devel] [PATCH 14/14] kexec: Add option to get crash kernel region size

Here print_crashkernel_region_size() function is available on all archs (even if the functionality is not implemented on some). So, we can safely use it in arch independent code and export the functionality to the user space. Signed-off-by: Daniel Kiper ---

[Xen-devel] [PATCH 02/14] kexec: Remove redundant space from help message

Signed-off-by: Daniel Kiper --- kexec/kexec.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kexec/kexec.c b/kexec/kexec.c index f0bd527..20dd93d 100644 --- a/kexec/kexec.c +++ b/kexec/kexec.c @@ -969,7 +969,7 @@ void usage(void) "

[Xen-devel] [PATCH 10/14] crashdump/ppc: Add print_crashkernel_region_size() function

Provide just print_crashkernel_region_size() stub. This way we can properly build kexec utility on ppc arch even if the functionality is not available on it. Signed-off-by: Daniel Kiper --- kexec/arch/ppc/crashdump-powerpc.c |4 1 file changed, 4 insertions(+)

[Xen-devel] [PATCH 01/14] purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe

Signed-off-by: Daniel Kiper --- purgatory/Makefile |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/purgatory/Makefile b/purgatory/Makefile index 2b5c061..caea7ea 100644 --- a/purgatory/Makefile +++ b/purgatory/Makefile @@ -33,7 +33,7 @@

[Xen-devel] [PATCH 07/14] crashdump/ia64: Add print_crashkernel_region_size() function

Follow similar x86 patch. Signed-off-by: Daniel Kiper --- kexec/arch/ia64/crashdump-ia64.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/kexec/arch/ia64/crashdump-ia64.c b/kexec/arch/ia64/crashdump-ia64.c index 726c9f4..07de42a 100644 ---

[Xen-devel] [PATCH 08/14] crashdump/m68k: Add print_crashkernel_region_size() function

Provide just print_crashkernel_region_size() stub. This way we can properly build kexec utility on m68k arch even if the functionality is not available on it. Signed-off-by: Daniel Kiper --- kexec/arch/m68k/kexec-m68k.c |5 + 1 file changed, 5 insertions(+)

[Xen-devel] [PATCH 12/14] crashdump/s390: Add print_crashkernel_region_size() function

Follow similar x86 patch. Signed-off-by: Daniel Kiper --- kexec/arch/s390/kexec-s390.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/kexec/arch/s390/kexec-s390.c b/kexec/arch/s390/kexec-s390.c index 074575e..212a64f 100644 ---

[Xen-devel] [PATCH 04/14] crashdump/x86: Add print_crashkernel_region_size() function

Crash kernel region size is available via sysfs on Linux running on bare metal. However, this does not work when Linux runs as Xen dom0. In this case Xen crash kernel region size should be established using __HYPERVISOR_kexec_op hypercall (Linux kernel kexec functionality does not make a lot of

[Xen-devel] [PATCH 09/14] crashdump/mips: Add print_crashkernel_region_size() function

Follow similar x86 patch. Signed-off-by: Daniel Kiper --- kexec/arch/mips/crashdump-mips.c |9 + 1 file changed, 9 insertions(+) diff --git a/kexec/arch/mips/crashdump-mips.c b/kexec/arch/mips/crashdump-mips.c index dc68cb4..450fa13 100644 ---

[Xen-devel] [PATCH 13/14] crashdump/sh: Add print_crashkernel_region_size() function

Follow similar x86 patch. Signed-off-by: Daniel Kiper --- kexec/arch/sh/crashdump-sh.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/kexec/arch/sh/crashdump-sh.c b/kexec/arch/sh/crashdump-sh.c index 9e6af6b..6556eb1 100644 ---

[Xen-devel] [PATCH 05/14] crashdump/arm: Add print_crashkernel_region_size() function

Follow similar x86 patch. Signed-off-by: Daniel Kiper --- kexec/arch/arm/crashdump-arm.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/kexec/arch/arm/crashdump-arm.c b/kexec/arch/arm/crashdump-arm.c index b523e5f..b3e93ad 100644 ---

[Xen-devel] [PATCH 03/14] crashdump: Remove stray get_crashkernel_region() declaration

Signed-off-by: Daniel Kiper --- kexec/crashdump.h |1 - 1 file changed, 1 deletion(-) diff --git a/kexec/crashdump.h b/kexec/crashdump.h index 95f1f0c..320767b 100644 --- a/kexec/crashdump.h +++ b/kexec/crashdump.h @@ -1,7 +1,6 @@ #ifndef CRASHDUMP_H #define

<    1   2