flight 158460 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158460/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
Hi Ian
On 14.01.21 19:20, Ian Jackson wrote:
Oleksandr Tyshchenko writes ("[PATCH V4 24/24] [RFC] libxl: Add support for
virtio-disk configuration"):
This patch adds basic support for configuring and assisting virtio-disk
backend (emualator) which is intended to run out of Qemu and could be
flight 158454 qemu-mainline real [real]
flight 158461 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158454/
http://logs.test-lab.xenproject.org/osstest/logs/158461/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
On 15.01.21 18:41, Jan Beulich wrote:
Hi Jan
On 12.01.2021 22:52, Oleksandr Tyshchenko wrote:
@@ -1080,6 +1104,27 @@ int hvm_unmap_io_range_from_ioreq_server(struct domain
*d, ioservid_t id,
return rc;
}
+/* Called with ioreq_server lock held */
+int arch_ioreq_server_map_mem_ty
On Tue, Jan 12, 2021 at 07:12:37PM +0100, Manuel Bouyer wrote:
> From: Manuel Bouyer
>
> Pass bridge name to qemu as command line option
> When starting qemu, set an environnement variable XEN_DOMAIN_ID,
> to be used by qemu helper scripts
>
> Signed-off-by: Manuel Bouyer
> ---
> tools/libs/li
flight 158459 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158459/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf c88736f8605eab3b0877d9301f8e845291c6fdd9
baseline version:
ovmf 014b9850f2a33ae402b87
There are only two keyhandlers which make use of the cpu_user_regs
struct passed to them. In order to be able to call any keyhandler in
non-interrupt contexts, too, modify those two handlers to cope with a
NULL regs pointer by using run_in_exception_handler() in that case.
Suggested-by: Julien Gra
When the host crashes it would sometimes be nice to have additional
debug data available which could be produced via debug keys, but
halting the server for manual intervention might be impossible due to
the need to reboot/kexec rather sooner than later.
Add support for automatic debug key actions
When the host crashes it would sometimes be nice to have additional
debug data available which could be produced via debug keys, but
halting the server for manual intervention might be impossible due to
the need to reboot/kexec rather sooner than later.
Add support for automatic debug key actions
Add support to run a function in an exception handler for Arm. Do it
as on x86 via a bug_frame, but pass the function pointer via a
register (this needs to be done that way, because inline asm support
for 32-bit Arm lacks the needed functionality to reference an
arbitrary function via the bugframe)
On Sat, Jan 16, 2021 at 11:16:06AM +0100, Roger Pau Monné wrote:
> On Tue, Jan 12, 2021 at 07:12:37PM +0100, Manuel Bouyer wrote:
> > From: Manuel Bouyer
> >
> > Pass bridge name to qemu as command line option
> > When starting qemu, set an environnement variable XEN_DOMAIN_ID,
> > to be used by
Hi Stefano,
On 15/01/2021 23:17, Stefano Stabellini wrote:
On Fri, 15 Jan 2021, Volodymyr Babchuk wrote:
9us was in idle state. Interestingly enough, I got latency if 3us while
Dom0 was doing some CPU-intensive tasks. So, under load latency is lower
than in idle state. I didn't investigated thi
On 15/01/2021 23:41, Stefano Stabellini wrote:
> This is very interestingi too. Did you get any spikes with the
> period
> set to 100us? It would be fantastic if there were none.
>
>> 3. Huge latency spike during domain creation. I conducted some
>> additional tests, in
flight 158457 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158457/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ws16-amd64 19 guest-stopfail like 158437
test-amd64-amd64-xl-qemuu-win7-amd64
On 12/01/2021 23:48, Volodymyr Babchuk wrote:
> Hello community,
>
> Recently I was experimenting with context switching latencies in
> Xen. I want to share my findings and discuss some issues I have found.
>
> My target was to ensure that no more 30us passes between interrupt
> generation and hand
flight 158458 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158458/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd broken
test-amd64-i386-qemuu-rhel6hvm-intel 7 xe
Hi Juergen,
On 16/01/2021 10:33, Juergen Gross wrote:
Add support to run a function in an exception handler for Arm. Do it
as on x86 via a bug_frame, but pass the function pointer via a
register (this needs to be done that way, because inline asm support
for 32-bit Arm lacks the needed functiona
On 16.01.21 18:19, Julien Grall wrote:
Hi Juergen,
On 16/01/2021 10:33, Juergen Gross wrote:
Add support to run a function in an exception handler for Arm. Do it
as on x86 via a bug_frame, but pass the function pointer via a
register (this needs to be done that way, because inline asm support
f
flight 158462 qemu-mainline real [real]
flight 158464 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158462/
http://logs.test-lab.xenproject.org/osstest/logs/158464/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
flight 158463 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158463/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd broken in 158458
test-amd64-i386-qemuu-rhel6hvm-
On Fri, 15 Jan 2021, Jan Beulich wrote:
As you will have seen, I've posted a series apparently doing this a
little differently, in particular without said LONG_MAX -> INT_MAX
transformation. While it works fine this way for me, it would be
nice if you could double check it also does for you.
Y
flight 158465 qemu-mainline real [real]
flight 158468 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158465/
http://logs.test-lab.xenproject.org/osstest/logs/158468/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 15 Jan 2021 20:08:58 + you wrote:
> Resending the stragglers again.
> This set is part of a larger effort attempting to clean-up W=1
> kernel builds, which are currently overwhelmingly riddled with
> niggly lit
flight 158466 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158466/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-qem
flight 158469 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158469/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
25 matches
Mail list logo
