flight 88488 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88488/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
flight 88370 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88370/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 60684
test-amd64
flight 88467 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88467/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
flight 88347 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88347/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs.
86491
test-amd64-am
flight 88458 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88458/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
flight 88359 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88359/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt-xsm 12 migrate-support-checkfail never pass
test-amd64-i386-libvirt 12 migrate-sup
flight 88449 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88449/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
flight 88440 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88440/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
[cc Jan Kara]
On Sat, Apr 2, 2016 at 1:47 PM, Borislav Petkov wrote:
> On Sat, Apr 02, 2016 at 01:13:37PM -0700, Andy Lutomirski wrote:
>> Given that I this isn't really a regression with my patches (it
>> probably never worked much better on 32-bit and the regs never would
>> have shown at all o
flight 88323 linux-3.16 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88323/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs.
85048
Tests which are
On Sat, Apr 02, 2016 at 01:16:07PM -0700, Andy Lutomirski wrote:
> I have no idea why it was explicitly unsupported, but I'm guessing it
> was just to avoid duplicating the code. Early "ext" uaccess failures
> are certainly not going to work, but I don't think this is a problem
> -- there's no use
On Sat, Apr 02, 2016 at 01:13:37PM -0700, Andy Lutomirski wrote:
> Given that I this isn't really a regression with my patches (it
> probably never worked much better on 32-bit and the regs never would
> have shown at all on 64-bit),
You're right. That thing calls printk *and* early_printk, WTF:
flight 88334 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88334/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-amd64-xl-qemuu-ov
On Sat, 02 Apr 2016 20:05:21 +0200,
Andy Lutomirski wrote:
>
> On Apr 2, 2016 12:07 PM, "Takashi Iwai" wrote:
> >
> > On Sat, 02 Apr 2016 14:57:44 +0200,
> > Andy Lutomirski wrote:
> > >
> > > On Fri, Apr 1, 2016 at 10:33 PM, Takashi Iwai wrote:
> > > > On Sat, 02 Apr 2016 00:28:31 +0200,
> > >
On Sat, Apr 2, 2016 at 11:52 AM, Borislav Petkov wrote:
> On Sat, Apr 02, 2016 at 07:01:35AM -0700, Andy Lutomirski wrote:
>> Now that early_fixup_exception has pt_regs, we can just call
>> fixup_exception from it. This will make fancy exception handlers
>> work early.
>>
>> Signed-off-by: Andy L
On Sat, Apr 2, 2016 at 11:39 AM, Borislav Petkov wrote:
> On Sat, Apr 02, 2016 at 07:01:34AM -0700, Andy Lutomirski wrote:
>> This removes a bunch of assembly and adds some C code instead. It
>> changes the actual printouts on both 32-bit and 64-bit kernels, but
>> they still seem okay.
>>
>> Sig
flight 88431 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88431/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
flight 88309 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88309/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
like 86551
test-amd64-i38
On Sat, Apr 02, 2016 at 07:01:35AM -0700, Andy Lutomirski wrote:
> Now that early_fixup_exception has pt_regs, we can just call
> fixup_exception from it. This will make fancy exception handlers
> work early.
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/mm/extable.c | 19 ++--
On Sat, Apr 02, 2016 at 07:01:34AM -0700, Andy Lutomirski wrote:
> This removes a bunch of assembly and adds some C code instead. It
> changes the actual printouts on both 32-bit and 64-bit kernels, but
> they still seem okay.
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/include/asm/uacc
On Apr 2, 2016 12:07 PM, "Takashi Iwai" wrote:
>
> On Sat, 02 Apr 2016 14:57:44 +0200,
> Andy Lutomirski wrote:
> >
> > On Fri, Apr 1, 2016 at 10:33 PM, Takashi Iwai wrote:
> > > On Sat, 02 Apr 2016 00:28:31 +0200,
> > > Luis R. Rodriguez wrote:
> > >> If the former, could a we somehow detect an
flight 88426 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88426/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
On Sat, 02 Apr 2016 14:57:44 +0200,
Andy Lutomirski wrote:
>
> On Fri, Apr 1, 2016 at 10:33 PM, Takashi Iwai wrote:
> > On Sat, 02 Apr 2016 00:28:31 +0200,
> > Luis R. Rodriguez wrote:
> >> If the former, could a we somehow detect an emulated device other than
> >> through
> >> this type of chec
flight 88296 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88296/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 10 guest-start fail REGR. vs. 86454
test-amd64-i386-fre
On Sat, Apr 2, 2016 at 10:13 AM, Andy Lutomirski wrote:
>
> I also tried a bad wrmsrl at a couple early points. Very very early
> it just works with not warning. A little later and it prints the
> warning.
Ok, that sounds like the correct behavior - I'm sure the very very
early ones "warned" to
On Sat, Apr 2, 2016 at 7:24 AM, Linus Torvalds
wrote:
> This patch series looks much nicer than the last one. I assume you
> tested that the early-trap handling actually worked too? I only looked
> at the patches..
>
> Ack to it all,
I injected some BUGs in various places on 32-bit an 64-bit and
flight 88411 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88411/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
This patch series looks much nicer than the last one. I assume you
tested that the early-trap handling actually worked too? I only looked
at the patches..
Ack to it all,
Linus
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.x
This demotes an OOPS and likely panic due to a failed non-"safe" MSR
access to a WARN_ONCE and, for RDMSR, a return value of zero.
To be clear, this type of failure should *not* happen. This patch
exists to minimize the chance of nasty undebuggable failures
happening when a CONFIG_PARAVIRT=y bug
There are two parts here:
* FIRST PART: EARLY EXCEPTIONS *
The first few patches move some early panic code into C, add pt_regs
to early exception handling, and make fancy exception handlers work early.
* SECOND PART: MSRs *
Setting CONFIG_PARAVIRT=y has an unintended side effec
This adds paravirt hooks for unsafe MSR access. On native, they
call native_{read,write}_msr. On Xen, they use
xen_{read,write}_msr_safe.
Nothing uses them yet for ease of bisection. The next patch will
use them in rdmsrl, wrmsrl, etc.
I intentionally didn't make them warn on #GP on Xen. I th
This will cause unchecked native_rdmsr_safe failures to return
deterministic results.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/msr.h | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/msr.h b/arch/x86/include/asm/msr.h
index 13da359881d7..
These hooks match the _safe variants, so name them accordingly.
This will make room for unsafe PV hooks.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/paravirt.h | 33 +
arch/x86/include/asm/paravirt_types.h | 8
arch/x86/kernel/paravirt.
Now that early_fixup_exception has pt_regs, we can just call
fixup_exception from it. This will make fancy exception handlers
work early.
Signed-off-by: Andy Lutomirski
---
arch/x86/mm/extable.c | 19 ++-
1 file changed, 2 insertions(+), 17 deletions(-)
diff --git a/arch/x86/mm
C is nicer than asm.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/head_32.S | 7 ---
arch/x86/kernel/head_64.S | 6 --
arch/x86/mm/extable.c | 5 +
3 files changed, 5 insertions(+), 13 deletions(-)
diff --git a/arch/x86/kernel/head_32.S b/arch/x86/kernel/head_32.S
index be
early_fixup_exception is limited by the fact that it doesn't have a
real struct pt_regs. Change both the 32-bit and 64-bit asm and the
C code to pass and accept a real pt_regs.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/uaccess.h | 2 +-
arch/x86/kernel/head_32.S | 74 +++
Enabling CONFIG_PARAVIRT had an unintended side effect: rdmsr turned
into rdmsr_safe and wrmsr turned into wrmsr_safe, even on bare
metal. Undo that by using the new unsafe paravirt MSR hooks.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/paravirt.h | 9 +++--
1 file changed, 3 in
This removes a bunch of assembly and adds some C code instead. It
changes the actual printouts on both 32-bit and 64-bit kernels, but
they still seem okay.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/uaccess.h | 2 +-
arch/x86/kernel/head_32.S | 49 +---
flight 88284 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88284/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
test-amd64-amd64-xl-c
On Fri, Apr 1, 2016 at 10:33 PM, Takashi Iwai wrote:
> On Sat, 02 Apr 2016 00:28:31 +0200,
> Luis R. Rodriguez wrote:
>> If the former, could a we somehow detect an emulated device other than
>> through
>> this type of check ? Or could we *add* a capability of some sort to detect it
>> on the dri
flight 88394 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88394/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
Well if you install ocaml-nox oxenstored is made default, so I tested both
situations this morning with and without ocaml. That location is not
causing the problem, as it happened without ocaml too. The install path for
ocaml is worth checking, as it should not default to /usr/local, after
grepping
On Sat, Apr 02, 2016 at 11:59:47AM +0100, Wei Liu wrote:
> On Sat, Apr 02, 2016 at 02:45:41AM +0200, Sjoer van der Ploeg wrote:
> > Just finished a fresh testbed, xendomains still refused to get enabled when
> > using --prefix=/usr and modules did load.
> >
> > Took a look at /usr/local (which was
On Sat, Apr 02, 2016 at 02:45:41AM +0200, Sjoer van der Ploeg wrote:
> Just finished a fresh testbed, xendomains still refused to get enabled when
> using --prefix=/usr and modules did load.
>
> Took a look at /usr/local (which was non-existent before make install),
> ocaml dumped its files there
flight 88381 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88381/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
flight 88251 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88251/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken in 87395 REGR. vs. 66399
build-amd64-rumpuserxen
flight 88367 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88367/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
build-armhf
47 matches
Mail list logo
