[Xen-devel] [linux-mingo-tip-master test] 83867: regressions - FAIL

flight 83867 linux-mingo-tip-master real [real] http://logs.test-lab.xenproject.org/osstest/logs/83867/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-xsm 15 guest-localmigratefail REGR. vs. 60684

Re: [Xen-devel] [PATCH RFC 7/8] libxl: introduce topology fields

On Mon, Feb 22, 2016 at 09:02:13PM +, Joao Martins wrote: > Currently there is "smt" option that changes from a flat core topology > to a core+thread topology. This patch adds more expressive options for > describing the topology as seen by the guest i.e. sockets, cores and > threads to adjust

Re: [Xen-devel] [PATCH RFC 4/8] libxl: cpuid: add guest topology support

On Mon, Feb 22, 2016 at 09:02:10PM +, Joao Martins wrote: > Introduce internal cpuid routine for setting the topology > as seen by the guest. The topology is made based on > leaf 1 and leaf 4 for Intel, more specifically setting: > > Number of logical processors: > proccount

Re: [Xen-devel] [PATCH RFC 5/8] libxl: introduce smt field

On Mon, Feb 22, 2016 at 09:02:11PM +, Joao Martins wrote: > By setting it to true, it enables the vcpus set by the guest > to be seen as a SMT-enabled topology. It uses then > libxl__cpuid_set_topology() to change the cpuid accordingly. > This setting is made *before* the cpuid is set so that

Re: [Xen-devel] [PATCH RFC 2/8] libxl: remove whitespace on libxl_types.idl

On Mon, Feb 22, 2016 at 09:02:08PM +, Joao Martins wrote: > Signed-off-by: Joao Martins Acked-by: Wei Liu > --- > CC: Ian Jackson > CC: Stefano Stabellini > CC: Ian Campbell

Re: [Xen-devel] [PATCH] docs/design: introduce HVMMEM_ioreq_serverX types

On 25/02/16 15:49, Paul Durrant wrote: > This patch adds a new 'designs' subdirectory under docs as a repository > for this and future design proposals. > > Signed-off-by: Paul Durrant > --- > > For convenience this document can also be viewed in PDF at: > >

Re: [Xen-devel] [PATCH v3 00/16] Load BIOS via toolstack instead of been embedded in hvmloader.

On 02/25/2016 09:55 AM, Anthony PERARD wrote: Hi all, Many changes in V3: no more cmdline, but use each modules' cmdline to provide a name for it. in libxc: - use xc_dom_alloc_segment() to load modules. see patch #1. - avoid duplication of code between PVHv2 and hvmloader for

Re: [Xen-devel] [PATCH v3 1/2] xen/x86: Zero out .bss for PV guests

On Thu, Feb 25, 2016 at 10:16 AM, Boris Ostrovsky wrote: > Baremetal kernels clear .bss early in the boot but Xen PV guests don't > execute that code. They have been able to run without problems because > Xen domain builder happens to give out zeroed pages. However,

Re: [Xen-devel] [PATCH v10 00/31] COarse-grain LOck-stepping Virtual Machines for Non-stop Service

I managed to go through up to patch 21 today. I will see if I can get some more time to look at the rest. Wei. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

[Xen-devel] [PATCH] docs: Update README to include Clang

Xen now builds on x86 with Clang 3.5 and 3.8. Update README to reflect this. Mark Clang as no longer a permitted failure in Travis, to prevent future regressions slipping back in. Signed-off-by: Andrew Cooper --- CC: Ian Campbell CC: Ian

Re: [Xen-devel] [PATCH v10 18/31] libxc/restore: support COLO restore

On Mon, Feb 22, 2016 at 10:52:22AM +0800, Wen Congyang wrote: [...] > - * With Remus, we buffer the records sent by the primary at checkpoint, > + * With Remus/COLO, we buffer the records sent by the primary at checkpoint, > * in case the primary will fail, we can recover from the last > *

Re: [Xen-devel] [PATCH v10 21/31] libxc/save: support COLO save

On Mon, Feb 22, 2016 at 10:52:25AM +0800, Wen Congyang wrote: [...] > /* > * Suspend the domain and send dirty memory. > * This is the last iteration of the live migration and the > @@ -558,6 +610,16 @@ static int suspend_and_send_dirty(struct xc_sr_context > *ctx) > >

Re: [Xen-devel] [PATCH v10 17/31] primary vm suspend/resume/checkpoint code

On Mon, Feb 22, 2016 at 10:52:21AM +0800, Wen Congyang wrote: [...] > +#include "libxl_osdeps.h" /* must come before any other headers */ > + > +#include "libxl_internal.h" > +#include "libxl_colo.h" > + > +static const libxl__checkpoint_device_instance_ops *colo_ops[] = { > +NULL, > +}; > + >

Re: [Xen-devel] [PATCH v10 10/31] tools/libxl: add back channel support to write stream

On Mon, Feb 22, 2016 at 10:52:14AM +0800, Wen Congyang wrote: > Add back channel support to write stream. If the write stream is > a back channel stream, this means the write stream is used by > Secondary to send some records back. > > Signed-off-by: Yang Hongyang >

Re: [Xen-devel] [PATCH v10 07/31] docs/libxl: Introduce CHECKPOINT_CONTEXT to support migration v2 colo streams

On Mon, Feb 22, 2016 at 10:52:11AM +0800, Wen Congyang wrote: > It is the negotiation record for COLO. > Primary->Secondary: > control_id 0x: Secondary VM is out of sync, start a new > checkpoint > Secondary->Primary: > 0x0001: Secondary VM is suspended >

Re: [Xen-devel] [PATCH v10 05/31] tools/libx{l, c}: add back channel to libxc

On Mon, Feb 22, 2016 at 10:52:09AM +0800, Wen Congyang wrote: > In COLO mode, both VMs are running, and are considered in sync if the > visible network traffic is identical. After some time, they fall out of > sync. > > At this point, the two VMs have definitely diverged. Lets call the >

Re: [Xen-devel] [PATCH v10 04/31] tools/libxl: Introduce new helper function dup_fd_helper()

On Mon, Feb 22, 2016 at 10:52:08AM +0800, Wen Congyang wrote: > It is pure refactoring and no functional changes. > > Signed-off-by: Wen Congyang Assuming this is going to be used later: Acked-by: Wei Liu > --- > tools/libxl/libxl_save_callout.c |

Re: [Xen-devel] [PATCH v10 12/31] tools/libxl: add back channel support to read stream

On Mon, Feb 22, 2016 at 10:52:16AM +0800, Wen Congyang wrote: > This is used by primay to read records sent by secondary. > > Signed-off-by: Yang Hongyang > Signed-off-by: Wen Congyang > --- > tools/libxl/libxl_create.c | 1 + >

Re: [Xen-devel] [PATCH v10 06/31] docs: add colo readme

On Mon, Feb 22, 2016 at 10:52:10AM +0800, Wen Congyang wrote: > add colo readme, refer to > http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping > > Signed-off-by: Yang Hongyang > Acked-by: Ian Campbell > Signed-off-by: Wen Congyang

Re: [Xen-devel] [PATCH v10 01/31] tools/libxl: introduce libxl__domain_restore_device_model to load qemu state

On Mon, Feb 22, 2016 at 10:52:05AM +0800, Wen Congyang wrote: > In normal migration, the qemu state is passed to qemu as a parameter. > With COLO, secondary vm is running. So we will do the following steps > at every checkpoint: > 1. suspend both primary vm and secondary vm > 2. sync the state >

Re: [Xen-devel] [PATCH 4/8] tools/xenalyze: Mark unreachable code as unreachable

On Thu, 2016-02-25 at 15:43 +, George Dunlap wrote: > On 25/02/16 15:28, Ian Campbell wrote: > > On Thu, 2016-02-25 at 15:09 +, George Dunlap wrote: > > > On 25/02/16 15:03, Ian Campbell wrote: > > > > On Thu, 2016-02-25 at 14:48 +, George Dunlap wrote: > > > > > ...so that coverity

Re: [Xen-devel] [PATCH] docs: spell out limits of security support for qemu-xen

Stefano Stabellini writes ("[PATCH] docs: spell out limits of security support for qemu-xen"): > Write down what emulated hardware is supported in qemu-xen. Add a way > for users to ask for a change in the list. Acked-by: Ian Jackson

[Xen-devel] [PATCH] docs: spell out limits of security support for qemu-xen

Write down what emulated hardware is supported in qemu-xen. Add a way for users to ask for a change in the list. Signed-off-by: Stefano Stabellini CC: jbeul...@suse.com CC: ian.jack...@eu.citrix.com CC: lars.ku...@citrix.com CC: konrad.w...@oracle.com ---

Re: [Xen-devel] [PATCH 4/8] tools/xenalyze: Mark unreachable code as unreachable

On 25/02/16 15:28, Ian Campbell wrote: > On Thu, 2016-02-25 at 15:09 +, George Dunlap wrote: >> On 25/02/16 15:03, Ian Campbell wrote: >>> On Thu, 2016-02-25 at 14:48 +, George Dunlap wrote: ...so that coverity knows it's unreachable. >>> >>> I would not be surprised if Coverity

Re: [Xen-devel] [PATCH v5 09/11] xen: add capability to load initrd outside of initial mapping

On 25/02/16 13:47, Daniel Kiper wrote: > On Thu, Feb 25, 2016 at 12:33:35PM +0100, Juergen Gross wrote: >> Modern pvops linux kernels support an initrd not covered by the initial >> mapping. This capability is flagged by an elf-note. >> >> In case the elf-note is set by the kernel don't place the

Re: [Xen-devel] [PATCH 4/8] tools/xenalyze: Mark unreachable code as unreachable

On Thu, 2016-02-25 at 15:09 +, George Dunlap wrote: > On 25/02/16 15:03, Ian Campbell wrote: > > On Thu, 2016-02-25 at 14:48 +, George Dunlap wrote: > > > ...so that coverity knows it's unreachable. > > > > I would not be surprised if Coverity starts complaining about the dead > > code >

[Xen-devel] [PATCH v3 1/2] xen/x86: Zero out .bss for PV guests

Baremetal kernels clear .bss early in the boot but Xen PV guests don't execute that code. They have been able to run without problems because Xen domain builder happens to give out zeroed pages. However, since this is not really guaranteed, .bss should be explicitly cleared. Signed-off-by: Boris

[Xen-devel] [PATCH v3 2/2] xen/x86: Drop mode-selecting ifdefs in startup_xen()

Use asm/asm.h macros instead. Signed-off-by: Boris Ostrovsky --- arch/x86/xen/xen-head.S | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/arch/x86/xen/xen-head.S b/arch/x86/xen/xen-head.S index 11dbe49..2366895 100644 ---

[Xen-devel] [PATCH v3 0/2] Clear .bss for VP guests

PV guests need to have their .bss zeroed out since it is not guaranteed to be cleared by Xen's domain builder v3: * Use existing macros for selecting mode-appropriate instructions/registers * Use 32-bit registers in XOR * Split removal of mode-selecting ifdefs into a separate patch Boris

[Xen-devel] [xen-unstable-smoke test] 83972: tolerable all pass - PUSHED

flight 83972 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/83972/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass test-armhf-armhf-xl 12

Re: [Xen-devel] [PATCH v2 3/3] hvc_xen: make early_printk work with HVM guests

On 02/25/2016 07:10 AM, Stefano Stabellini wrote: Refactor the existing code in xen_raw_console_write to get the generic early_printk console work with HVM guests. Take the opportunity to replace the outb loop with a single outsb call to reduce the number of vmexit. Signed-off-by: Stefano

[Xen-devel] [PATCHv4 0/3] x86: workaround inability to fully restore FPU state

This series extends the workaround for the inability for some x86 CPUs to fully restore the FPU exception state (64-bit FIP/FDP and FCS/FDS). Toolstack (or the guest) may override the default behaviour to always do a 32-bit save/restore. Running Microsoft's Driver Verifier continues to work in a

[Xen-devel] [PATCHv4 2/3] x86/hvm: add HVM_PARAM_X87_FIP_WIDTH

The HVM parameter HVM_PARAM_X87_FIP_WIDTH to allow tools and the guest to adjust the width of the FIP/FDP registers to be saved/restored by the hypervisor. This is in case the hypervisor hueristics do not do the right thing. Add this parameter to the set saved during domain save/migrate.

[Xen-devel] [PATCHv4 3/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

The hardware may not write the FIP/FDP fields with a XSAVE* instruction. e.g., with XSAVEOPT/XSAVES if the state hasn't changed or on AMD CPUs when a floating point exception is not pending. We need to identify this case so we can correctly apply the check for whether to save/restore FCS/FDS.

[Xen-devel] [PATCHv4 1/3] x86/fpu: Add a per-domain field to set the width of FIP/FDP

The x86 architecture allows either: a) the 64-bit FIP/FDP registers to be restored (clearing FCS and FDS); or b) the 32-bit FIP/FDP and FCS/FDS registers to be restored (clearing the upper 32-bits). Add a per-domain field to indicate which of these options a guest needs. The options are: 8, 4 or

Re: [Xen-devel] [PATCH 4/8] tools/xenalyze: Mark unreachable code as unreachable

On 25/02/16 15:03, Ian Campbell wrote: > On Thu, 2016-02-25 at 14:48 +, George Dunlap wrote: >> ...so that coverity knows it's unreachable. > > I would not be surprised if Coverity starts complaining about the dead code > once this is in place. fprintf + abort is probably what would be wanted

Re: [Xen-devel] [PATCHv3 1/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

On 25/02/16 15:07, Andrew Cooper wrote: > On 25/02/16 14:27, Jan Beulich wrote: > On 25.02.16 at 14:16, wrote: >>> No OS is plausibly going to hide non-IP information in FIP. >>> >>> If some theoretical OS does do something like that, there is always the >>>

[Xen-devel] [PATCH v3 16/16] hvmloader: do not depend on SEABIOS_PATH or OVMF_PATH ...

... to compile SeaBIOS and OVMF. Only depends on CONFIG_*. If --with-system-* configure option is used, then set *_CONFIG=n to not compile SEABIOS and OVMF. Signed-off-by: Anthony PERARD --- Please, run ./autogen.sh on this patch. --- tools/configure.ac | 6

[Xen-devel] [PATCH v3 12/16] hvmloader: Specific bios_load function required

All BIOS but ROMBIOS needs to be loaded via modules. ROMBIOS is handled as a special case. Signed-off-by: Anthony PERARD --- Change in V3: - reprint Main BIOS in bios map with now available information from bios modules. - handle rombios, and keep its built-in ROMs.

Re: [Xen-devel] [PATCHv3 1/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

On 25/02/16 14:27, Jan Beulich wrote: On 25.02.16 at 14:16, wrote: >> No OS is plausibly going to hide non-IP information in FIP. >> >> If some theoretical OS does do something like that, there is always the >> override available. > But who says it needs to be an

Re: [Xen-devel] [PATCH v2 2/3] hvc_xen: fix xenboot for DomUs

On 02/25/2016 07:10 AM, Stefano Stabellini wrote: The xenboot early console has been partially broken for DomU for a long time: the output would only go to the hypervisor via hypercall (HYPERVISOR_console_io), while it wouldn't actually go to the DomU console. The reason is that

[Xen-devel] [PATCH v3 13/16] hvmloader: Load ACPI tables from hvm_start_info module

... and use it with both SeaBIOS and OVMF. Signed-off-by: Anthony PERARD --- Changes in V3: - handle rombios --- tools/firmware/hvmloader/config.h| 2 +- tools/firmware/hvmloader/hvmloader.c | 20 +++- tools/firmware/hvmloader/ovmf.c | 9

[Xen-devel] [PATCH v3 11/16] hvmloader: Load OVMF from modules

... and do not include the OVMF ROM into hvmloader anymore. Signed-off-by: Anthony PERARD --- Change in V3: - change makefile to not include ovmf rom into roms.inc. - update the struct bios_config with bios destination --- tools/firmware/hvmloader/Makefile | 15

[Xen-devel] [PATCH v3 14/16] hvmloader: Compile out the qemu-xen ACPI tables

It should now be loaded by libxl. Signed-off-by: Anthony PERARD --- tools/firmware/hvmloader/acpi/Makefile | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/tools/firmware/hvmloader/acpi/Makefile b/tools/firmware/hvmloader/acpi/Makefile

[Xen-devel] [PATCH v3 15/16] hvmloader: Always build-in SeaBIOS and OVMF loader

Signed-off-by: Anthony PERARD --- tools/firmware/hvmloader/Makefile| 11 +-- tools/firmware/hvmloader/hvmloader.c | 4 2 files changed, 1 insertion(+), 14 deletions(-) diff --git a/tools/firmware/hvmloader/Makefile

Re: [Xen-devel] [PATCH 4/8] tools/xenalyze: Mark unreachable code as unreachable

On Thu, 2016-02-25 at 14:48 +, George Dunlap wrote: > ...so that coverity knows it's unreachable. I would not be surprised if Coverity starts complaining about the dead code once this is in place. fprintf + abort is probably what would be wanted to placate it in this case. Ian. > >

[Xen-devel] [PATCH v3 10/16] hvmloader: Load SeaBIOS from hvm_start_info modules

... and do not include the SeaBIOS ROM into hvmloader anymore. This also fix the dependency on roms.inc, hvmloader.o does not include it. Signed-off-by: Anthony PERARD --- Change in V3: - change makefile to not include seabios roms into roms.inc. - update the struct

Re: [Xen-devel] [PATCH v4 13/21] arm/gic-v2: Add ACPI boot support for GICv2

On Thu, 25 Feb 2016, Stefano Stabellini wrote: > On Thu, 25 Feb 2016, Shannon Zhao wrote: > > On 2016/2/25 18:42, Stefano Stabellini wrote: > > > On Thu, 25 Feb 2016, Shannon Zhao wrote: > > >> On 2016/1/28 20:56, Stefano Stabellini wrote: > > >>> On Sat, 23 Jan 2016, Shannon Zhao wrote: > >

Re: [Xen-devel] [PATCH v2 1/3] hvc_xen: add earlycon support

On 02/25/2016 07:10 AM, Stefano Stabellini wrote: Introduce EARLYCON support in hvc_xen, useful for early debugging on arm and arm64, where xen early_printk is not available. It is different from xenboot_write_console on x86 in two ways: - it does not return if !xen_pv_domain(), not only

[Xen-devel] [PATCH v3 05/16] libxl: Load guest BIOS from file

The path to the BIOS blob can be override by the xl's bios_override option, or provided by u.hvm.bios_firmware in the domain_build_info struct by other libxl user. Signed-off-by: Anthony PERARD --- Change in V3: - move seabios_path and ovmf_path to libxl_path.c (with

Re: [Xen-devel] [PATCH v4 13/21] arm/gic-v2: Add ACPI boot support for GICv2

On Thu, 25 Feb 2016, Shannon Zhao wrote: > On 2016/2/25 18:42, Stefano Stabellini wrote: > > On Thu, 25 Feb 2016, Shannon Zhao wrote: > >> On 2016/1/28 20:56, Stefano Stabellini wrote: > >>> On Sat, 23 Jan 2016, Shannon Zhao wrote: > From: Parth Dixit > >

[Xen-devel] [PATCH v3 08/16] hvmloader: Locate the BIOS blob

The BIOS can be found an entry called "bios" of the modlist of the hvm_start_info struct. The found BIOS blob is not loaded by this patch, but only passed as argument to bios_load() function. It is going to be used by the next few patches. Signed-off-by: Anthony PERARD

[Xen-devel] [PATCH v3 02/16] libxc: Load BIOS and ACPI table into guest memory

This adds two new firmware module, bios_module and full_acpi_module. They are loaded in the guest memory and final location is provided to hvmloader via the hvm_start_info struct. This patch create the hvm_start_info struct for HVM guest that have a device model, so this is now common code with

[Xen-devel] [PATCH v3 06/16] libxl: Load guest ACPI table from file

A user can provide a different ACPI tables than the default one by using the existing "acpi_firmware" xl's config option or the field u.hvm.acpi_firmware. libxl will check if the provided table is a DSDT or not. Signed-off-by: Anthony PERARD --- Change in V3: - use

[Xen-devel] [PATCH v3 03/16] configure: #define SEABIOS_PATH and OVMF_PATH

Those paths are to be used by libxl, in order to load the firmware in memory. If a system path is not define, then this default to the Xen firmware directory. Signed-off-by: Anthony PERARD --- Please, run ./autogen.sh on this patch. --- tools/configure.ac | 6 ++

[Xen-devel] [PATCH v3 09/16] hvmloader: Check modules whereabouts

As perform_tests() is going to clear memory past 4MB, we check that the memory can be use. Signed-off-by: Anthony PERARD --- New in V3 --- tools/firmware/hvmloader/hvmloader.c | 9 + 1 file changed, 9 insertions(+) diff --git

[Xen-devel] [PATCH v3 07/16] hvmloader: Grab the hvm_start_info pointer

Signed-off-by: Anthony PERARD --- Change in V3: - remove cmdline parser - load hvm_start_info pointer earlier, before calling main(). - Add struct hvm_start_info definition to hvmloader. --- tools/firmware/hvmloader/hvm_start_info.h | 32

[Xen-devel] [PATCH v3 04/16] firmware/makefile: install BIOS and ACPI blob ...

... into the firmware directory, along with hvmloader. This introduce a rules for dsdt_anycpu_qemu_xen.aml, and change the rule for dsdt_anycpu_qemu_xen.c to temporarly generate both .c and .aml. The generation of dsdt_anycpu_qemu_xen.c will go away in a future patch. Signed-off-by: Anthony

[Xen-devel] [PATCH v3 00/16] Load BIOS via toolstack instead of been embedded in hvmloader.

Hi all, Many changes in V3: no more cmdline, but use each modules' cmdline to provide a name for it. in libxc: - use xc_dom_alloc_segment() to load modules. see patch #1. - avoid duplication of code between PVHv2 and hvmloader for the initialisation of hvm_start_info. in

[Xen-devel] [PATCH v3 01/16] libxc: Rework extra module initialisation

This patch use xc_dom_alloc_segment() to allocate the memory space for the ACPI modules and the SMBIOS modules. This is to replace the arbitrary placement of 1MB after the hvmloader image. In later patches, while trying to load a firmware such as OVMF, the later could easily be loaded past the

[Xen-devel] Ping: [PATCH 2/5] x86emul: limit-check branch targets

>>> On 17.02.16 at 17:35, wrote: > All branches need to #GP when their target violates the segment limit > (in 16- and 32-bit modes) or is non-canonical (in 64-bit mode). For > near branches facilitate this via a zero-byte instruction fetch from > the target address (resulting

[Xen-devel] [PATCH 4/8] tools/xenalyze: Mark unreachable code as unreachable

...so that coverity knows it's unreachable. Signed-off-by: George Dunlap --- CC: Ian Jackson CC: Wei Liu --- tools/xentrace/xenalyze.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/xentrace/xenalyze.c

[Xen-devel] [PATCH 0/8] Fixes to Coverity issues reported on xenalyze

This series fixes a number of issues to coverity with xenalyze. George Dunlap (8): tools/xenalyze: Close symbol_file after reading it tools/xenalyze: Avoid redundant check tools/xenalyze: Handle fstat errors properly tools/xenalyze: Mark unreachable code as unreachable tools/xenalyze:

[Xen-devel] [PATCH 7/8] tools/xenalyze: Fix multiple instances of *HYPERCALL_MAX

We HYPERCALL_MAX defined as the maximum enumerated hypercall, and we have PV_HYPERCALL_MAX defined as some other number (presumably based on experience with actual hypercalls). Both are used to size arrays (hypercall_name[] and pv_data.hypercall_count[], respectively). Rename PV_HYPERCALL_MAX to

[Xen-devel] [PATCH 3/8] tools/xenalyze: Handle fstat errors properly

They're pretty unlikely to fail, but doesn't hurt to check. CID 1311502 CID 1311501 Signed-off-by: George Dunlap --- CC: Ian Jackson CC: Wei Liu --- tools/xentrace/mread.c| 9 - tools/xentrace/xenalyze.c | 5

[Xen-devel] [PATCH 6/8] tools/xenalyze: Fix off-by-one in MAX_CPUS range checks

Skip action / throw error if cpu/vcpu >= MAX_CPUS rather than >. Also add an assertion to vcpu_find, to make future errors of this kind not out-of-bounds. CID 1306871 CID 1306870 CID 1306869 CID 1306867 Signed-off-by: George Dunlap --- CC: Ian Jackson

[Xen-devel] [PATCH 5/8] tools/xenalyze: Fix check for error return value

fdopen returns NULL on failure, not a negative integer. CID 1306863 CID 1306858 Signed-off-by: George Dunlap --- Strangely, coverity counted this as two bugs: one for comparing a pointer with a negative integer, one for the comparison never possibly being true (thus

[Xen-devel] [PATCH 2/8] tools/xenalyze: Avoid redundant check

Coverity notices that if !head is true, that !N can never be true. Don't bother checking N, since we know it has to be at least one. CID 1354243 Signed-off-by: George Dunlap --- CC: Ian Jackson CC: Wei Liu ---

[Xen-devel] [PATCH 1/8] tools/xenalyze: Close symbol_file after reading it

...to avoid leaking the FD and associated memory. CID 1306872 Signed-off-by: George Dunlap --- Not sure if this will actually make coverity happy, or if we need to actually set symbol_file to NULL. CC: Ian Jackson CC: Wei Liu

[Xen-devel] [PATCH 8/8] tools/xenalyze: Actually handle case where number of ipi vectors exceeds static max

find_vec() is supposed to find the vector in the list if it exists, choose an empty slot if it doesn't exist, and return null if all slots are full. However, coverity noticed that although the callers of find_vec() handle the last condition, find_vec() itself didn't. Check to see if we actually

Re: [Xen-devel] [PATCH v5 10/11] xen: modify page table construction

On Thu, Feb 25, 2016 at 12:33:36PM +0100, Juergen Gross wrote: > Modify the page table construction to allow multiple virtual regions > to be mapped. This is done as preparation for removing the p2m list > from the initial kernel mapping in order to support huge pv domains. > > This allows a

[Xen-devel] [xen-unstable test] 83855: tolerable FAIL - PUSHED

flight 83855 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/83855/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 83609 test-armhf-armhf-xl-rtds

Re: [Xen-devel] [PATCHv3 1/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

>>> On 25.02.16 at 14:16, wrote: > No OS is plausibly going to hide non-IP information in FIP. > > If some theoretical OS does do something like that, there is always the > override available. But who says it needs to be an OS to do so? User mode code could as much

Re: [Xen-devel] [PATCH] Fix MAINTAINERS: remove any use of {a,b}

On 2/25/16 6:21 AM, Anthony PERARD wrote: > This is the complain from perl: > Unescaped left brace in regex is deprecated, passed through in regex; marked > by <-- HERE in m/^docs/misc/kconfig{ <-- HERE ,-language}\.txt/ at > scripts/get_maintainer.pl line 731. > > Also, it does not work. > >

Re: [Xen-devel] [PATCH v4 13/21] arm/gic-v2: Add ACPI boot support for GICv2

On 2016/2/25 18:42, Stefano Stabellini wrote: > On Thu, 25 Feb 2016, Shannon Zhao wrote: >> On 2016/1/28 20:56, Stefano Stabellini wrote: >>> On Sat, 23 Jan 2016, Shannon Zhao wrote: From: Parth Dixit ACPI on Xen hypervisor uses MADT table for proper GIC

Re: [Xen-devel] [PATCHv3 1/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

On 25/02/16 12:49, David Vrabel wrote: > On 25/02/16 12:27, Jan Beulich wrote: > On 25.02.16 at 13:18, wrote: >>> On 25/02/16 11:32, Jan Beulich wrote: >>> On 25.02.16 at 11:58, wrote: > The poison value is fixed and thus knowable by

Re: [Xen-devel] [PATCH v5 5/7] VT-d: Refactor iommu_ops .map_page() and unmap_page()

On Thu, 2016-02-25 at 05:23 -0700, Jan Beulich wrote: > > > > On 25.02.16 at 13:14, wrote: > >  > > To me, this might be fine. > > Does Per-CPU flag refer to this_cpu(iommu_dont_flush_iotlb) or > > variant? > > Yes. But I'd prefer ... > > > > However, the same effect could be

Re: [Xen-devel] [PATCH] Fix MAINTAINERS: remove any use of {a,b}

On Thu, Feb 25, 2016 at 12:34:43PM +, Ian Campbell wrote: > On Thu, 2016-02-25 at 05:31 -0700, Jan Beulich wrote: > > > > > On 25.02.16 at 13:21, wrote: > > > This is the complain from perl: > > > Unescaped left brace in regex is deprecated, passed through in regex;

Re: [Xen-devel] [PATCH] Fix MAINTAINERS: remove any use of {a,b}

On 25/02/16 12:21, Anthony PERARD wrote: > This is the complain from perl: > Unescaped left brace in regex is deprecated, passed through in regex; marked > by <-- HERE in m/^docs/misc/kconfig{ <-- HERE ,-language}\.txt/ at > scripts/get_maintainer.pl line 731. F: is supposed to be globs, not

Re: [Xen-devel] [PATCHv3 1/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

On 25/02/16 12:27, Jan Beulich wrote: On 25.02.16 at 13:18, wrote: >> On 25/02/16 11:32, Jan Beulich wrote: >> On 25.02.16 at 11:58, wrote: The poison value is fixed and thus knowable by a guest (or guest userspace). This

Re: [Xen-devel] [PATCH v5 09/11] xen: add capability to load initrd outside of initial mapping

On Thu, Feb 25, 2016 at 12:33:35PM +0100, Juergen Gross wrote: > Modern pvops linux kernels support an initrd not covered by the initial > mapping. This capability is flagged by an elf-note. > > In case the elf-note is set by the kernel don't place the initrd into > the initial mapping. This will

[Xen-devel] (no subject)

Hello, As asked of in the previous mail, I tried compiling Xen from source. I am not sure whether we can ask questions for the task given, but I have been stuck at it from yesterday. I followed all the steps, and wherever there was some problem, I looked up that in wiki of Xen, but after building

Re: [Xen-devel] [PATCH] Fix MAINTAINERS: remove any use of {a,b}

On Thu, 2016-02-25 at 05:31 -0700, Jan Beulich wrote: > > > > On 25.02.16 at 13:21, wrote: > > This is the complain from perl: > > Unescaped left brace in regex is deprecated, passed through in regex; > > marked > > by <-- HERE in m/^docs/misc/kconfig{ <-- HERE

Re: [Xen-devel] [PATCH] Fix MAINTAINERS: remove any use of {a,b}

>>> On 25.02.16 at 13:21, wrote: > This is the complain from perl: > Unescaped left brace in regex is deprecated, passed through in regex; marked > by <-- HERE in m/^docs/misc/kconfig{ <-- HERE ,-language}\.txt/ at > scripts/get_maintainer.pl line 731. > > Also, it

Re: [Xen-devel] Xen Project Infrastructure Maintenance: Feb 25th and 1st of March

Just a quick note to let you know that the following services have been updated this morning - all foo @ lists at xenproject dot org mailing lists - forwarding of mails to foo @ xenproject for org accounts - downloads.xenproject.org Regards Lars ___

Re: [Xen-devel] [PATCHv3 1/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

>>> On 25.02.16 at 13:18, wrote: > On 25/02/16 11:32, Jan Beulich wrote: > On 25.02.16 at 11:58, wrote: >>> The hardware may not write the FIP/FDP fields with a XSAVE* >>> instruction. e.g., with XSAVEOPT/XSAVES if the state hasn't changed

Re: [Xen-devel] [PATCH v5 5/7] VT-d: Refactor iommu_ops .map_page() and unmap_page()

>>> On 25.02.16 at 13:14, wrote: > On February 25, 2016 4:59pm, wrote: >> I'd >> really suggest investigating alternatives. One that comes to mind would be to >> move acquiring/releasing pcidevs_lock into a helper function, and setting a >> per-CPU flag

Re: [Xen-devel] What time is it kvm-clock?

On 02/24/2016 07:55 PM, Owen Hofmann wrote: not-really-well-defined hybrid? --Andy >>> >>> 1. What is not well defined? I fail to spot anything >>> specific in Owen's e-mail. >> >> If I start a guest and query kvm-clock, I get a nanosecond count. >> AFAIK it is, in fact, ill-defined

[Xen-devel] [PATCH] Fix MAINTAINERS: remove any use of {a,b}

This is the complain from perl: Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^docs/misc/kconfig{ <-- HERE ,-language}\.txt/ at scripts/get_maintainer.pl line 731. Also, it does not work. Signed-off-by: Anthony PERARD

Re: [Xen-devel] [PATCHv3 1/3] x86/fpu: improve check for XSAVE* not writing FIP/FDP fields

On 25/02/16 11:32, Jan Beulich wrote: On 25.02.16 at 11:58, wrote: >> The hardware may not write the FIP/FDP fields with a XSAVE* >> instruction. e.g., with XSAVEOPT/XSAVES if the state hasn't changed >> or on AMD CPUs when a floating point exception is not pending.

Re: [Xen-devel] [PATCH v5 02/11] xen: avoid memleaks on error

On Thu, Feb 25, 2016 at 12:33:28PM +0100, Juergen Gross wrote: > When loading a Xen pv-kernel avoid memory leaks in case of errors. > > Signed-off-by: Juergen Gross Reviewed-by: Daniel Kiper Daniel ___

Re: [Xen-devel] [PATCH v5 5/7] VT-d: Refactor iommu_ops .map_page() and unmap_page()

+CC Dario who is also watching this patch set. On February 25, 2016 4:59pm, wrote: > >>> On 25.02.16 at 07:56, wrote: > >> On February 17, 2016 10:23pm, wrote: > >> >>> On 05.02.16 at 11:18, wrote: > >> > to pass down

[Xen-devel] [PATCH v2 1/3] hvc_xen: add earlycon support

Introduce EARLYCON support in hvc_xen, useful for early debugging on arm and arm64, where xen early_printk is not available. It is different from xenboot_write_console on x86 in two ways: - it does not return if !xen_pv_domain(), not only because ARM guests are xen_hvm_domain(), but also

[Xen-devel] [PATCH v2 2/3] hvc_xen: fix xenboot for DomUs

The xenboot early console has been partially broken for DomU for a long time: the output would only go to the hypervisor via hypercall (HYPERVISOR_console_io), while it wouldn't actually go to the DomU console. The reason is that domU_write_console would return early as no xencons structs are

[Xen-devel] [PATCH] libxl: fix comment LIBXL__EGC_INIT -> LIBXL_EGC_INIT

Signed-off-by: Wei Liu Cc: Ian Jackson --- tools/libxl/libxl_internal.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h index 650a958..cda0741 100644 ---

[Xen-devel] [PATCH v2 3/3] hvc_xen: make early_printk work with HVM guests

Refactor the existing code in xen_raw_console_write to get the generic early_printk console work with HVM guests. Take the opportunity to replace the outb loop with a single outsb call to reduce the number of vmexit. Signed-off-by: Stefano Stabellini ---

[Xen-devel] [PATCH v2 0/3] hvc_xen: fix xenboot on x86 and export to ARM

Hi all, this series exports xenboot on ARM and ARM64 as earlycon, and gets xenboot fully working again for PV DomUs on x86 (currently the xenboot output only goes to the hypervisor via hypercall and not to the DomU console). Cheers, Stefano Stefano Stabellini (3): hvc_xen: add earlycon

Re: [Xen-devel] [PATCH 1/2] hvc_xen: add earlycon support

On Wed, 24 Feb 2016, Andrew Cooper wrote: > On 24/02/16 17:18, Konrad Rzeszutek Wilk wrote: > >> I could do the same here by dropping the if (!xen_pv_domain()) check > >> above, but then if somebody specifies earlyprintk=xenboot on a non-Xen > >> environment, I expect Linux would crash. > > Nah,

[Xen-devel] [PATCH v2] vVMX: use latched VMCS machine address

Instead of calling domain_page_map_to_mfn() over and over, latch the guest VMCS machine address unconditionally (i.e. independent of whether VMCS shadowing is supported by the hardware). Since this requires altering the parameters of __[gs]et_vmcs{,_real}() (and hence all their callers) anyway,

Re: [Xen-devel] [PATCHv3 2/3] x86/fpu: Add a per-domain field to set the width of FIP/FDP

>>> On 25.02.16 at 12:38, wrote: > On 25/02/16 11:24, Jan Beulich wrote: > On 25.02.16 at 11:58, wrote: >>> @@ -261,7 +261,15 @@ void xsave(struct vcpu *v, uint64_t mask) >>> "=m" (*ptr), \ >>>

<    1   2   3   >