flight 107900 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107900/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail in 107840
pass in 107900
test-amd64-amd64-x
flight 107882 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107882/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 6 xen-boot fail REGR. vs. 107819
test-amd64-i386-xl-q
flight 107911 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107911/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 107636
build-arm64-xsm
This run is configured for baseline tests only.
flight 71241 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71241/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 65ed9d7ff55ad5c149e713d73b8d52ee8cbce601
baseline v
flight 107912 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107912/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs.
106986
test-amd64-amd64-
flight 107913 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107913/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 65ed9d7ff55ad5c149e713d73b8d52ee8cbce601
baseline version:
ovmf fcdb928a82c4ed3d776d0
branch xen-unstable
xenbranch xen-unstable
job build-armhf-libvirt
testid libvirt-build
Tree: libvirt git://libvirt.org/libvirt.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: libvirt git
On Thu, 13 Apr 2017, Herongguang (Stephen) wrote:
> On 2017/4/13 7:51, Stefano Stabellini wrote:
> > On Wed, 12 Apr 2017, Herongguang (Stephen) wrote:
> > > On 2017/4/12 6:32, Stefano Stabellini wrote:
> > > > On Tue, 11 Apr 2017, hrg wrote:
> > > > > On Tue, Apr 11, 2017 at 3:50 AM, Stefano Stabel
This run is configured for baseline tests only.
flight 71240 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71240/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 15 guest-lo
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> Xenconsole supports only PV console currently. This patch adds support
> for vuart, which allows emulated pl011 uart to be accessed as a console.
>
> This patch modifies different data structures and APIs used
> in xenconsole to support two console ty
flight 107879 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107879/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 107358
Tests which are faili
On 04/28/2017 09:42 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> We want to track why a guest was shutdown; in particular, being able
>> to tell the difference between a guest request (such as ACPI request)
>> and host request (such as SIGINT) will prove useful to libvirt.
>> Since all
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> 1. Update documentation for vuart = "pl011" option added.
> 2. Update documentation about SPI irq reserved for vpl011.
>
> Signed-off-by: Bhupinder Thakur
> ---
> docs/man/xl.cfg.pod.5.in | 8
> docs/misc/console.txt| 14 +-
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> Add a new console type VUART to connect to guest vuart.
>
> Signed-off-by: Bhupinder Thakur
> ---
> tools/console/client/main.c | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/tools/console/client/main.c b/tools/cons
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> Add two new parameters to the xen store to be used by xenconsoled:
> - newly allocated PFN to be used as IN/OUT ring buffer
> - get a new event channel allocated by Xen using a domctl call
>
> These paramters are added to xenstore only if vuar
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> Allocate a new pfn and pass on to Xen using a domctl call.
>
> Signed-off-by: Bhupinder Thakur
Reviewed-by: Stefano Stabellini
>
> Changes since v1:
> - Replaced the hvm call with the domctl call to set the pfn.
>
> tools/libxc/include/xc_dom.
flight 107869 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107869/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 3 host-install(3) broken REGR. vs. 59254
test-armhf-armhf-xl
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> An option is provided in libxl to enable/disable pl011 vuart while
> creating a guest domain.
>
> Libxl now suppots a generic vuart console and pl011 is a specific type.
> In future support can be added for multiple vuart of different types.
>
> User
branch xen-unstable
xenbranch xen-unstable
job build-arm64-xsm
testid xen-build
Tree: qemuu git://git.qemu.org/qemu.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: qemuu git://git.qemu.org/qemu.git
Bug introduced: 52e94ea5de3ed9d7d
On 04/25/2017 02:50 PM, Andrew Cooper wrote:
On 24/04/17 18:54, Mohit Gambhir wrote:
Mohit Gambhir (2):
xtf/vpmu: Add Intel PMU MSR addresses
xtf/vpmu: MSR read/write tests for VPMU
arch/x86/include/arch/msr-index.h | 11 +
tests/vpmu/Makefile | 9 +
tests/vpmu/main
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> 1. Add two new domctl API to:
> - Allocate a new event channel for sending/receiving events to/from Xen.
> - Map the PFN allocted by the toolstack to be used as IN/OUT ring buffers.
>
> Xen will communicate with xenconsole over the ring buffer
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> Vpl011 emulation is enabled for a guest domain in Xen only when it is
> enabled through an option in libxl provided by the user through
> guest configuration.
>
> The pl011 enable/disable knob in libxl is introduced in the following
> patch:
>
> xen/
On Fri, 28 Apr 2017, Bhupinder Thakur wrote:
> Add emulation code to emulate read/write access to pl011 registers
> and pl011 interrupts:
>
> - Emulate DR read/write by reading and writing from/to the IN
> and OUT ring buffers and raising an event to the backend when
> there is dat
This patch adds Intel PMU MSR addresses as macros for VPMU testing
Signed-off-by: Mohit Gambhir
---
arch/x86/include/arch/msr-index.h | 12
1 file changed, 12 insertions(+)
diff --git a/arch/x86/include/arch/msr-index.h
b/arch/x86/include/arch/msr-index.h
index 72373c6..911d7f9 10
This patch tests VPMU functionality in the hypervisor on Intel machines.
The tests write to all valid bits in the MSRs that get exposed to the guests
when VPMU is enabled. The tests also write invalid values to the bits
that should be masked and expect the wrmsr call to fault.
The tests are curren
v2:
Incorporated review comments received on patch v1.
+ Changed test type from utility to functional
+ Test is now defined only for hvm64 and hvm32 instead of ALL_ENVIRONMENTS
+ Several code styling and formatting changes
+ Expanded test description for doxygen
+ Added max_leaf check before cp
* Eric Blake (ebl...@redhat.com) wrote:
> On 04/28/2017 11:09 AM, Dr. David Alan Gilbert wrote:
>
> >>> At a higher level, using your tags, I'm not sure where a reset triggered
> >>> by a fault detected by the hypervisor lives - e.g. an x86 triple fault
> >>> where the guest screws up so badly tha
On 04/28/2017 11:09 AM, Dr. David Alan Gilbert wrote:
>>> At a higher level, using your tags, I'm not sure where a reset triggered
>>> by a fault detected by the hypervisor lives - e.g. an x86 triple fault
>>> where the guest screws up so badly that it just gets reset. Is
>>> that a guest-reset o
On 24/04/17 21:04, Boris Ostrovsky wrote:
> Recent discussion (http://marc.info/?l=xen-devel&m=149192184523741)
> established that commit 72a9b186292d ("xen: Remove event channel
> notification through Xen PCI platform device") (and thus commit
> da72ff5bfcb0 ("partially revert "xen: Remove event c
On 26/04/17 15:42, Boris Ostrovsky wrote:
> Recent code rework that split handling ov PV, HVM and PVH guests into
> separate files missed calling xen_smp_intr_init_pv() on CPU0.
>
> Add this call.
>
> Signed-off-by: Boris Ostrovsky
> Reported-by: Sander Eikelenboom
Pushed to xen/tip for-linus-
On 25/04/17 06:02, Juergen Gross wrote:
> On 24/04/17 20:21, Boris Ostrovsky wrote:
>> On 04/24/2017 01:58 PM, Julien Grall wrote:
>>> The helper xen_reboot will be called by the EFI code in a later patch.
>>>
>>> Note that the ARM version does not yet exist and will be added in a
>>> later patch t
flight 107904 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107904/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt 12 mig
Hello,
the tarball has not been uploaded to the URL in the mail.
Its 4pm BST when I send this, so maybe there is still time before everyone
leaves for the weekend.
Is it possible to post an xz tarball with a Debian delta naming scheme?
Something like:
xen_4.9~rc3.orig.tar.xz
thanks,
PryMar56
__
* Eric Blake (ebl...@redhat.com) wrote:
> On 04/28/2017 10:27 AM, Dr. David Alan Gilbert wrote:
>
> +# Enumeration of various causes for shutdown.
> +#
> +# @host-qmp: Reaction to a QMP command, such as 'quit'
> +# @host-signal: Reaction to a signal, such as SIGINT
> +# @h
Add a new console type VUART to connect to guest vuart.
Signed-off-by: Bhupinder Thakur
---
tools/console/client/main.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/console/client/main.c b/tools/console/client/main.c
index 99f..ec5c6e1 100644
--- a/tools/c
PL011 emulation for guests in Xen
===
Linaro has published VM System specification for ARM Processors, which
provides a set of guidelines for both guest OS and hypervisor implementations,
such that building OS images according to these guidelines guarantees
that tho
1. Update documentation for vuart = "pl011" option added.
2. Update documentation about SPI irq reserved for vpl011.
Signed-off-by: Bhupinder Thakur
---
docs/man/xl.cfg.pod.5.in | 8
docs/misc/console.txt| 14 +-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --
The SBSA uart node format is as specified in
Documentation/devicetree/bindings/serial/arm_sbsa_uart.txt and given below:
ARM SBSA defined generic UART
--
This UART uses a subset of the PL011 registers and consequently lives
in the PL011 driver. It's baudrate and other c
Xenconsole supports only PV console currently. This patch adds support
for vuart, which allows emulated pl011 uart to be accessed as a console.
This patch modifies different data structures and APIs used
in xenconsole to support two console types: PV and VUART.
Change summary:
1. Split the domai
Add two new parameters to the xen store to be used by xenconsoled:
- newly allocated PFN to be used as IN/OUT ring buffer
- get a new event channel allocated by Xen using a domctl call
These paramters are added to xenstore only if vuart console is enabled
by the user.
Signed-off-by: Bhupi
An option is provided in libxl to enable/disable pl011 vuart while
creating a guest domain.
Libxl now suppots a generic vuart console and pl011 is a specific type.
In future support can be added for multiple vuart of different types.
User can enable pl011 vuart by adding the following line in the
Vpl011 emulation is enabled for a guest domain in Xen only when it is
enabled through an option in libxl provided by the user through
guest configuration.
The pl011 enable/disable knob in libxl is introduced in the following
patch:
xen/arm: vpl011: Add support for vuart in libxl
Signed-off-by: B
Add emulation code to emulate read/write access to pl011 registers
and pl011 interrupts:
- Emulate DR read/write by reading and writing from/to the IN
and OUT ring buffers and raising an event to the backend when
there is data in the OUT ring buffer and injecting an interrupt
Allocate a new pfn and pass on to Xen using a domctl call.
Signed-off-by: Bhupinder Thakur
---
Changes since v1:
- Replaced the hvm call with the domctl call to set the pfn.
tools/libxc/include/xc_dom.h | 2 ++
tools/libxc/xc_dom_arm.c | 7 ++-
tools/libxc/xc_dom_boot.c| 2 ++
3 fi
1. Add two new domctl API to:
- Allocate a new event channel for sending/receiving events to/from Xen.
- Map the PFN allocted by the toolstack to be used as IN/OUT ring buffers.
Xen will communicate with xenconsole over the ring buffer and the event
channel to transmit and receive pl011 da
On 04/28/2017 10:27 AM, Dr. David Alan Gilbert wrote:
+# Enumeration of various causes for shutdown.
+#
+# @host-qmp: Reaction to a QMP command, such as 'quit'
+# @host-signal: Reaction to a signal, such as SIGINT
+# @host-ui: Reaction to a UI event, such as closing the wi
flight 107891 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107891/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-buildfail REGR. vs. 106986
build-amd64
flight 107884 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107884/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 107636
build-arm64-xsm
* Eric Blake (ebl...@redhat.com) wrote:
> On 04/28/2017 03:08 AM, Dr. David Alan Gilbert wrote:
> > * Eric Blake (ebl...@redhat.com) wrote:
> >> We want to track why a guest was shutdown; in particular, being able
> >> to tell the difference between a guest request (such as ACPI request)
> >> and h
Eric Blake writes:
> Libvirt would like to be able to distinguish between a SHUTDOWN
> event triggered solely by guest request and one triggered by a
> SIGTERM or other action on the host. While qemu_kill_report() is
> already able to tell whether a shutdown was triggered by a host
> signal (but
On 04/28/2017 03:08 AM, Dr. David Alan Gilbert wrote:
> * Eric Blake (ebl...@redhat.com) wrote:
>> We want to track why a guest was shutdown; in particular, being able
>> to tell the difference between a guest request (such as ACPI request)
>> and host request (such as SIGINT) will prove useful to
"Dr. David Alan Gilbert" writes:
> * Eric Blake (ebl...@redhat.com) wrote:
>> We want to track why a guest was shutdown; in particular, being able
>> to tell the difference between a guest request (such as ACPI request)
>> and host request (such as SIGINT) will prove useful to libvirt.
>> Since a
Eric Blake writes:
> We want to track why a guest was shutdown; in particular, being able
> to tell the difference between a guest request (such as ACPI request)
> and host request (such as SIGINT) will prove useful to libvirt.
> Since all requests eventually end up changing shutdown_requested in
Xen 4.9.0 RC3 is now available.
You can check it out from xen.git:
git://xenbits.xen.org/xen.git#4.9.0-rc3
For your convenience there is also a tarball and singautre at:
https://downloads.xenproject.org/release/xen/4.9.0-rc3/xen-4.9.0-rc3.tar.gz
https://downloads.xenproject.org/release/
flight 107840 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107840/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail in 107791 pass
in 107840
test-armhf-armhf-xl
Jan Beulich writes ("[PATCH] x86emul: correct stub invocation constraints
again"):
> While the hypervisor side of commit cd91ab08ea ("x86emul: correct stub
> invocation constraints") was fine, the tools side triggered a bogus
> error with old gcc (4.3 and 4.4 at least). Use a slightly less
> appro
libvirt.git#02fb15f introduces this new submodule.
Submodules are awkward, and we need them to be explicitly listed.
So add keycodemapdb to the submodulemap in ts-libvirt-build.
Reported-by: Wei Liu
Signed-off-by: Ian Jackson
---
ts-libvirt-build | 3 ++-
1 file changed, 2 insertions(+), 1 del
branch xen-unstable
xenbranch xen-unstable
job build-amd64-libvirt
testid libvirt-build
Tree: libvirt git://libvirt.org/libvirt.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reprod
On Fri, Apr 28, 2017 at 06:24:04AM -0600, Jan Beulich wrote:
> >>> On 28.04.17 at 12:54, wrote:
> > Since this is the last unacked patch I'm only sending the updated
> > version here.
>
> Sure,
> Reviewed-by: Jan Beulich
> with one minor remaining thing I did overlook in v3:
>
> > --- /dev/null
>>> On 28.04.17 at 13:01, wrote:
> From 0f61898acaeb2b34ee8156ebd40bb82fef28ff5f Mon Sep 17 00:00:00 2001
> From: Simon Crowe
> Date: Fri, 28 Apr 2017 10:46:43 +
> Subject: [PATCH] kexec: Provide user friendly option for memory limit
>
> grub2 requires that the '<' character be escaped which
>>> On 28.04.17 at 12:54, wrote:
> Since this is the last unacked patch I'm only sending the updated
> version here.
Sure,
Reviewed-by: Jan Beulich
with one minor remaining thing I did overlook in v3:
> --- /dev/null
> +++ b/xen/arch/x86/pv/domain.c
> @@ -0,0 +1,235 @@
> +/*
flight 107880 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107880/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-buildfail REGR. vs. 106986
build-amd64
>From 0f61898acaeb2b34ee8156ebd40bb82fef28ff5f Mon Sep 17 00:00:00 2001
From: Simon Crowe
Date: Fri, 28 Apr 2017 10:46:43 +
Subject: [PATCH] kexec: Provide user friendly option for memory limit
grub2 requires that the '<' character be escaped which is
inconvienet for users, provide a more nat
On Fri, Apr 28, 2017 at 02:47:30AM -0600, Jan Beulich wrote:
> >>> On 26.04.17 at 17:54, wrote:
> > --- a/xen/include/asm-x86/domain.h
> > +++ b/xen/include/asm-x86/domain.h
> > @@ -655,6 +655,9 @@ static inline void pv_inject_page_fault(int errcode,
> > unsigned long cr2)
> > pv_inject_even
>>> On 27.04.17 at 11:51, wrote:
> At 03:23 -0600 on 27 Apr (1493263380), Jan Beulich wrote:
>> ... it wouldn't better be the other way around: We use the patch
>> in its current (or even v1) form, and try to do something about
>> performance only if we really find a case where it matters. To be
>
Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 107791: regressions -
FAIL"):
> I don't suppose there is any memory sharing being set up for any
> tests in osstest,
Indeed, there isn't.
Ian.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
On Fri, Apr 28, 2017 at 1:29 PM, Jan Beulich wrote:
On 28.04.17 at 12:16, wrote:
>> On Fri, Apr 28, 2017 at 9:23 AM, Jan Beulich wrote:
>>> >>> On 27.04.17 at 18:56, wrote:
>>> > 2. xen/drivers/passthrough/vtd/x86/vtd.c:143:
>>> > ...
>>> > tmp = 1 << (PAGE_SHIFT - PAGE_SHIFT_4K);
>>> > fo
Jan
Ok i will make the change and resubmit
Thanks again
Regards
On Fri, Apr 28, 2017 at 11:37 AM +0100, "Jan Beulich"
mailto:jbeul...@suse.com>> wrote:
>>> On 27.04.17 at 14:22, wrote:
> @@ -162,6 +166,10 @@ static void __init parse_crashkernel(const char *str)
> kexec_crash_
>>> On 27.04.17 at 14:22, wrote:
> @@ -162,6 +166,10 @@ static void __init parse_crashkernel(const char *str)
> kexec_crash_area.start = parse_size_and_unit(cur = str + 1,
> &str);
> else if ( *str == '<' )
> kexec_crash_area_limit = parse_size_and_unit(cur = st
>>> On 28.04.17 at 12:16, wrote:
> On Fri, Apr 28, 2017 at 9:23 AM, Jan Beulich wrote:
>> >>> On 27.04.17 at 18:56, wrote:
>> > 2. xen/drivers/passthrough/vtd/x86/vtd.c:143:
>> > ...
>> > tmp = 1 << (PAGE_SHIFT - PAGE_SHIFT_4K);
>> > for ( j = 0; j < tmp; j++ )
>> > {
>> > int ret = iommu_ma
Hi, Jan.
Thank you for your reply.
On Fri, Apr 28, 2017 at 9:23 AM, Jan Beulich wrote:
>
> >>> On 27.04.17 at 18:56, wrote:
> > Now I am trying to replace single-page stuff with the multi-page one.
> > Currently, with the single-page API, if map fails we always try to unmap
> > already mapped p
On Wed, Apr 26, Andrew Cooper wrote:
> On 26/04/17 16:43, Olaf Hering wrote:
> > On Thu, Apr 20, Jan Beulich wrote:
> >
> > On 20.04.17 at 18:04, wrote:
> >>> On Thu, Apr 20, Andrew Cooper wrote:
> >>>
> As it currently stands, the sending side iterates from 0 to p2m_size,
> and sen
>>> On 28.04.17 at 11:09, wrote:
> On Fri, Apr 28, 2017 at 02:36:11AM -0600, Jan Beulich wrote:
> On 27.04.17 at 04:47, wrote:
>>> --- a/xen/include/asm-x86/hvm/vpt.h
>>> +++ b/xen/include/asm-x86/hvm/vpt.h
>>> @@ -46,6 +46,12 @@ struct periodic_time {
>>> #define PTSRC_lapic 2 /* LAPIC tim
flight 107841 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107841/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 107636
build-arm64-xsm
flight 107851 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107851/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 5 libvirt-buildfail REGR. vs. 107640
build-i386-libvirt
grub2 requires that the '<' character be escaped which is
inconvienet for users, provide a more natural specifier.
Signed-off-by: Simon Crowe
---
docs/misc/kexec_and_kdump.txt | 8 +++-
docs/misc/xen-command-line.markdown | 5 +
xen/common/kexec.c | 12 +
On Fri, Apr 28, 2017 at 02:36:11AM -0600, Jan Beulich wrote:
On 27.04.17 at 04:47, wrote:
>> When injecting periodic timer interrupt in vmx_intr_assist(),
>> multi-read operations are done during one event delivery. For
>> example, if a periodic timer interrupt is from PIT, when set the
>> co
>>> On 26.04.17 at 17:54, wrote:
> Remove the redundant is_pv_domain check. Rearrange setup_compat calls.
Well, as said earlier, I don't really see the value of the latter, but
anyway ...
> Signed-off-by: Wei Liu
Acked-by: Jan Beulich
___
Xen-dev
>>> On 26.04.17 at 17:54, wrote:
> Move updating type_info after clearing the page. Add spaces.
Suggested-by: Andrew ... ?
> Signed-off-by: Wei Liu
Reviewed-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/
>>> On 26.04.17 at 17:54, wrote:
> --- a/xen/include/asm-x86/domain.h
> +++ b/xen/include/asm-x86/domain.h
> @@ -655,6 +655,9 @@ static inline void pv_inject_page_fault(int errcode,
> unsigned long cr2)
> pv_inject_event(&event);
> }
>
> +void paravirt_ctxt_switch_from(struct vcpu *v);
>
flight 107867 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107867/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-buildfail REGR. vs. 106986
build-amd64
flight 71239 distros-debian-jessie real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71239/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-armhf-jessie-netboot-pygrub 14 guest-start/debian.repeat fail
REGR. v
>>> On 26.04.17 at 17:54, wrote:
> Now this function also frees the perdomain mapping. It is safe to do so
> because destroy_perdomain_mapping is idempotent.
>
> Move free_perdomain_mappings after pv_domain_destroy. It is safe to do
> so because both destroy_perdomain_mapping and free_perdomain_m
>>> On 26.04.17 at 17:54, wrote:
> Move PV specific vcpu initialisation code to said function, but leave
> the only line needed by idle domain in vcpu_initialise.
>
> Use pv_vcpu_destroy in error path to simplify code. It is safe to do so
> because the destruction function accepts partially initi
>>> On 26.04.17 at 17:54, wrote:
> This patch encapsulates the perdomain creation and destruction into
> helper functions and use them where appropriate.
>
> Since destroy_perdomain_mapping is idempotent, it is safe to call the
> destruction function multiple times.
>
> Signed-off-by: Wei Liu
>>> On 27.04.17 at 04:47, wrote:
> When injecting periodic timer interrupt in vmx_intr_assist(),
> multi-read operations are done during one event delivery. For
> example, if a periodic timer interrupt is from PIT, when set the
> corresponding bit in vIRR, the corresponding RTE is accessed in
> pt
Eric Blake writes:
> We now have macros in place to make it less verbose to add a scalar
> to QDict and QList, so use them. To make this patch smaller to
> review, a couple of subdirectories were done in earlier patches.
Scratch the last sentence. Can do on commit.
> Patch created mechanicall
flight 107829 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107829/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 107358
Tests which are faili
* Eric Blake (ebl...@redhat.com) wrote:
> We want to track why a guest was shutdown; in particular, being able
> to tell the difference between a guest request (such as ACPI request)
> and host request (such as SIGINT) will prove useful to libvirt.
> Since all requests eventually end up changing sh
flight 107819 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107819/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 6 xen-boot fail REGR. vs. 59254
test-armhf-armhf-xl
I found this patch couldn't work, the reason is inline. And need propose to
fix this.
> diff --git a/xen/arch/x86/hvm/dm.c b/xen/arch/x86/hvm/dm.c
> index 7e0da81..d72b7bd 100644
> --- a/xen/arch/x86/hvm/dm.c
> +++ b/xen/arch/x86/hvm/dm.c
> @@ -384,15 +384,50 @@ static int dm_op(domid_t domid,
>
>>> On 28.04.17 at 08:52, wrote:
> btw regardless of clarification which I'm trying to get, I think we do
> need disallow such guest operation going to physical MSR. It's not
> good to have guest impact physical PMU interrupt behavior. Even
> when we want to support guest PC operation in the futur
>>> On 28.04.17 at 08:45, wrote:
> On 04/28/2017 09:25 AM, Jan Beulich wrote:
> On 27.04.17 at 19:31, wrote:
>>> On 27/04/17 09:52, Jan Beulich wrote:
>>> On 27.04.17 at 10:34, wrote:
> On 27/04/2017 09:01, Jan Beulich wrote:
> On 27.04.17 at 09:22, wrote:
>>> --- a/xen/
>>> On 28.04.17 at 08:33, wrote:
> A compile error was introduced between 4.9.20170413T172409.e412c03be2
> and 4.9.20170426T155707.0a5370ee1f when gcc-4.3/4.5 is used:
See https://lists.xenproject.org/archives/html/xen-devel/2017-04/msg03240.html
Jan
___
>>> On 28.04.17 at 03:19, wrote:
> flight 107791 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/107791/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemut-win7-amd64 15 guest-l
flight 107858 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107858/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-buildfail REGR. vs. 106986
build-amd64
96 matches
Mail list logo
