On 20/06/18 00:24, osstest service owner wrote:
> flight 124372 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/124372/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-pvhv2-intel
On 06/19/2018 05:30 PM, Brian Woods wrote:
I'm currently seeing an issue where when booting from a recent Linux
kernel without nospec_store_bypass_disable. There's a NULL pointer
having to do with a lock. I put some printks in and it seems that in
arch/x86/kernel/process.c
that
The driver may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16.7 are:
[FUNC] mutex_lock_nested --> can sleep
drivers/xen/events/events_base.c, 839: mutex_lock_nested in
bind_evtchn_to_irq
drivers/xen/events/events_base.c, 1030: bind_evtchn_to_irq in
The driver may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16.7 are:
[FUNC] __get_free_pages(GFP_KERNEL)
drivers/xen/pvcalls-front.c, 351: __get_free_pages in create_active
drivers/xen/pvcalls-front.c, 800: create_active in pvcalls_front_accept
Hello,
Mixed-criticality and safety-critical systems under development need
support for timely boot of multiple domains at system launch -- “Initial
Domains” -- with static assignment of resources between them, each isolated
from the others and without runtime dependency on a “dom0”-type domain.
flight 124372 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124372/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvhv2-intel 7 xen-boot fail REGR. vs. 124090
I'm currently seeing an issue where when booting from a recent Linux
kernel without nospec_store_bypass_disable. There's a NULL pointer
having to do with a lock. I put some printks in and it seems that in
arch/x86/kernel/process.c
that speculative_store_bypass_ht_init isn't getting called which
This run is configured for baseline tests only.
flight 74886 xen-4.9-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74886/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 16
flight 124349 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124349/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl broken
test-armhf-armhf-xl-rtds
flight 124365 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124365/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm broken
test-armhf-armhf-xl-multivcpu
Otherwise e.g. xen/..xen-syms.0.o.d2 and xen/..xen-syms.1.o.d2 files
stay untouched because they are not listed in DEPS_RM variable.
Signed-off-by: Daniel Kiper
Acked-by: Ian Jackson
---
v2: Added Ian's ACK agreed on IRC.
---
xen/Makefile |2 +-
1 file changed, 1 insertion(+), 1
flight 124351 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124351/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-libvirt-pair 18 guests-nbd-mirror/debian fail in 124283 pass
in 124351
flight 124367 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124367/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 123814
build-amd64-libvirt
Otherwise times in XEN_BUILD_DATE and XEN_BUILD_TIME may differ.
Signed-off-by: Daniel Kiper
---
xen/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/Makefile b/xen/Makefile
index 60867e3..aa82641 100644
--- a/xen/Makefile
+++ b/xen/Makefile
@@ -9,7 +9,7 @@
In comparison to ELF the PE format is not supported by the Multiboot
protocol. So, if we wish to load xen.mb.efi using this protocol we
have to put header_addr, load_addr, load_end_addr, bss_end_addr and
entry_addr data into Multiboot header.
The Multiboot protocol spec can be found at
Hey,
As in subject... This way we get:
- one binary which can be loaded by the UEFI loader, Multiboot and
Multiboot2 protocols,
- UEFI secure boot support when Xen is loaded via Multiboot2 protocol,
- if we wish, in the future we can drop xen/xen.gz and build
xen.efi only,
- crash
We need the POSIX time to properly fill the TimeDateStamp field in the PE
header.
Additionally, realign the variables assignment in xen/Makefile to increase
readability.
Signed-off-by: Daniel Kiper
---
v2 - suggestions/fixes:
- derive XEN_COMPILE_POSIX_TIME from XEN_BUILD_DATE
Then rename xen.mb.efi to xen.efi and drop all related
differentiators in the code.
Signed-off-by: Daniel Kiper
---
xen/Makefile| 16 +-
xen/arch/arm/efi/efi-boot.h |4 -
xen/arch/x86/Makefile | 87 +
xen/arch/x86/boot/head.S|2 +-
In comparison to ELF the PE format is not supported by the Multiboot2
protocol. So, if we wish to load xen.mb.efi using this protocol we have
to add MULTIBOOT2_HEADER_TAG_ADDRESS and MULTIBOOT2_HEADER_TAG_ENTRY_ADDRESS
tags into Multiboot2 header.
Additionally, put
Signed-off-by: Daniel Kiper
---
v2 - suggestions/fixes:
- add const to *dom0_kernel efi_multiboot2() argument,
(suggested by Jan Beulich),
- improve comments
(suggested by Konrad Rzeszutek Wilk).
---
xen/arch/x86/boot/head.S| 23 +--
..which verifies PE signatures with SHIM_LOCK protocol. We want
to re-use this code in subsequent patch in efi_multiboot2().
Signed-off-by: Daniel Kiper
---
xen/common/efi/boot.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/xen/common/efi/boot.c
On Tue, Jun 19, 2018 at 2:14 AM Alexandru Stefan ISAILA
wrote:
>
> On Lu, 2018-06-18 at 09:39 -0600, Tamas K Lengyel wrote:
> > On Mon, Jun 18, 2018 at 9:19 AM Alexandru Isaila
> > wrote:
> > >
> > >
> > > +static p2m_access_t p2m_get_access(struct p2m_domain *p2m,
> > > unsigned long gfn)
> > >
Otherwise e.g. xen/..xen-syms.0.o.d2 and xen/..xen-syms.1.o.d2 files
stay untouched because they are not listed in DEPS_RM variable.
Signed-off-by: Daniel Kiper
---
xen/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/Makefile b/xen/Makefile
index
Michael Young writes ("Re: [Xen-devel] Status of comet-4.10 branch"):
> +1 to an update on the status of extra branches for XSA-254.
I'm drafting this update now. I think that the status is:
4.10.0-shim-comet:
Merged into and superseded by staging-4.10.
"Testing status" (see the advisory)
On 01/06/18 13:41, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Only gnttab_{alloc|free}_pages are exported as EXPORT_SYMBOL
> while all the rest are exported as EXPORT_SYMBOL_GPL, thus
> effectively making it not possible for non-GPL driver modules
> to use grant table
On 08/06/18 10:40, Roger Pau Monne wrote:
> Use a global variable to store the start flags for both PV and PVH.
> This allows the xen_initial_domain macro to work properly on PVH.
>
> Note that ARM is also switched to use the new variable.
>
> Signed-off-by: Boris Ostrovsky
> Signed-off-by:
On 15/06/18 01:34, Zhouyang Jia wrote:
> When xenbus_printf fails, the lack of error-handling code may
> cause unexpected results.
>
> This patch adds error-handling code after calling xenbus_printf.
>
> Signed-off-by: Zhouyang Jia
Pushed to xen/tip.git for-linus-4.18
Juergen
On 15/06/18 19:05, Zhouyang Jia wrote:
> When xenbus_printf fails, the lack of error-handling code may
> cause unexpected results.
>
> This patch adds error-handling code after calling xenbus_printf.
>
> Signed-off-by: Zhouyang Jia
Pushed to xen/tip.git for-linus-4.18
Juergen
On 16/06/18 02:14, Zhouyang Jia wrote:
> When xenbus_printf fails, the lack of error-handling code may
> cause unexpected results.
>
> This patch adds error-handling code after calling xenbus_printf.
>
> Signed-off-by: Zhouyang Jia
Pushed to xen/tip.git for-linus-4.18
Juergen
On 15/06/18 19:05, Zhouyang Jia wrote:
> When xenbus_printf fails, the lack of error-handling code may
> cause unexpected results.
>
> This patch adds error-handling code after calling xenbus_printf.
>
> Signed-off-by: Zhouyang Jia
Reviewed-by: Juergen Gross
Juergen
On 16/06/18 02:14, Zhouyang Jia wrote:
> When xenbus_printf fails, the lack of error-handling code may
> cause unexpected results.
>
> This patch adds error-handling code after calling xenbus_printf.
>
> Signed-off-by: Zhouyang Jia
Reviewed-by: Juergen Gross
Juergen
flight 124361 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124361/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 11d0cd23dd1bc15a6e6a1598250ea2e0c4c36e9a
baseline version:
ovmf
flight 74885 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74885/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-i386-daily-netboot-pygrub 11 guest-start fail REGR. vs. 74858
flight 124345 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124345/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-amd64-i386-libvirt 13
On Lu, 2018-06-18 at 09:39 -0600, Tamas K Lengyel wrote:
> On Mon, Jun 18, 2018 at 9:19 AM Alexandru Isaila
> wrote:
> >
> >
> > +static p2m_access_t p2m_get_access(struct p2m_domain *p2m,
> > unsigned long gfn)
> > +{
> > +void *ptr;
> > +
> > +ptr =
flight 124328 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124328/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ws16-amd64 16 guest-localmigrate/x10 fail like 123801
test-amd64-i386-libvirt-pair 23
flight 124292 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124292/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 broken
Tests which are
37 matches
Mail list logo
