[Xen-devel] [xen-4.5-testing test] 83003: regressions - FAIL

flight 83003 xen-4.5-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/83003/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-debianhvm-amd64 15 guest-localmigrate/x10 fail REGR. vs. 78736

Re: [Xen-devel] [PATCH] arm/monitor vm-events: Implement guest-request support

On 2/18/2016 11:25 PM, Tamas K Lengyel wrote: On Thu, Feb 18, 2016 at 1:08 PM, Razvan Cojocaru > wrote: On 02/18/2016 09:35 PM, Corneliu ZUZU wrote: > This patch adds ARM support for guest-request monitor vm-events. >

Re: [Xen-devel] [PATCH v3 01/10] xen: make xen loader callable multiple times

On 18/02/16 17:58, Daniel Kiper wrote: > On Thu, Feb 18, 2016 at 11:32:16AM +0100, Juergen Gross wrote: >> On 18/02/16 11:12, Daniel Kiper wrote: >>> On Wed, Feb 17, 2016 at 06:19:28PM +0100, Juergen Gross wrote: The loader for xen paravirtualized environment isn't callable multiple

Re: [Xen-devel] [PATCH v3 09/10] xen: modify page table construction

On 18/02/16 17:40, Daniel Kiper wrote: > On Wed, Feb 17, 2016 at 06:19: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

Re: [Xen-devel] [PATCH v3 02/10] xen: reduce number of global variables in xen loader

On 18/02/16 18:00, Lennart Sorensen wrote: > On Thu, Feb 18, 2016 at 11:34:49AM +0100, Juergen Gross wrote: >> On 18/02/16 11:22, Daniel Kiper wrote: >>> On Wed, Feb 17, 2016 at 06:19:29PM +0100, Juergen Gross wrote: The loader for xen paravirtualized environment is using lots of global

[Xen-devel] [xen-4.6-testing test] 83001: regressions - FAIL

flight 83001 xen-4.6-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/83001/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-xsm5 xen-build fail REGR. vs. 81632

[Xen-devel] [PATCH v5 1/2] xenoprof: fix up ability to disable it

Allow Xenoprof to be fully disabled when toggling the option off. Signed-off-by: Doug Goldstein --- CC: Keir Fraser CC: Jan Beulich CC: Andrew Cooper change since v4: - as much as possible disabled by

[Xen-devel] [PATCH v5 2/2] build: convert xenoprof to Kconfig

Convert the xenoprof x86 build time option to Kconfig. Signed-off-by: Doug Goldstein Reviewed-by: Andrew Cooper Acked-by: Jan Beulich --- CC: Keir Fraser CC: Jan Beulich CC: Andrew Cooper

[Xen-devel] [PATCH v2 1/4] tools/configure: only require bcc/ld86/as86 when needed

bcc/ld86/as86 are only necessary when we build rombios and not always so failing the build when they aren't available should not happen if the user isn't building rombios. Signed-off-by: Doug Goldstein --- CC: Ian Jackson CC: Stefano Stabellini

Re: [Xen-devel] [PATCH] hvmloader: Use xen/errno.h rather than the host systems errno.h

On Thu, Feb 18, 2016 at 10:10:09PM +, Andrew Cooper wrote: > Signed-off-by: Andrew Cooper Reviewed-by: Konrad Rzeszutek Wilk > --- > CC: Jan Beulich > CC: Ian Campbell > CC: Ian Jackson

[Xen-devel] [PATCH v2 2/4] m4/python: fix typo in LDFLAGS variable name

Reported-by: Jonathan Creekmore Signed-off-by: Doug Goldstein --- CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu

[Xen-devel] [PATCH v2 4/4] configure: rerun autoconf

Signed-off-by: Doug Goldstein --- CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu Before these changes I was seeing the following errors:

[Xen-devel] [PATCH v2 3/4] m4/python: fix checks for Python library support

AC_CHECK_LIB() was running gcc -Llib -lm -lutils conftest.c which on platforms that do as needed operations by default will result in underlinking. Instead AC_CHECK_LIB() suggests supplying the extra libraries necessary in a 5th argument. Signed-off-by: Doug Goldstein --- CC:

Re: [Xen-devel] [PATCH] hvmloader: Use xen/errno.h rather than the host systems errno.h

On 2/18/16 4:10 PM, Andrew Cooper wrote: > Signed-off-by: Andrew Cooper > --- > CC: Jan Beulich > CC: Ian Campbell > CC: Ian Jackson > CC: Wei Liu > CC: Doug Goldstein

[Xen-devel] [PATCH v12 2/2] Add a command line parameter for VT-d posted-interrupts

Enable VT-d Posted-Interrupts and add a command line parameter for it. CC: Jan Beulich Signed-off-by: Feng Wu Reviewed-by: Kevin Tian Acked-by: Jan Beulich --- docs/misc/xen-command-line.markdown | 9 -

[Xen-devel] [PATCH v12 0/2] Add VT-d Posted-Interrupts support

VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt. With VT-d Posted-Interrupts enabled, external interrupts from direct-assigned devices can be delivered to guests without VMM intervention when guest is running in non-root mode. You can find the VT-d Posted-Interrtups Spec. in

Re: [Xen-devel] [RFC Design Doc] Add vNVDIMM support for Xen

> > > QEMU would always use MFN above guest normal ram and I/O holes for > > > vNVDIMM. It would attempt to search in that space for a contiguous range > > > that is large enough for that that vNVDIMM devices. Is guest able to > > > punch holes in such GFN space? > > > > See XENMAPSPACE_* and

[Xen-devel] [PATCH v12 1/2] vmx: VT-d posted-interrupt core logic handling

This is the core logic handling for VT-d posted-interrupts. Basically it deals with how and when to update posted-interrupts during the following scenarios: - vCPU is preempted - vCPU is slept - vCPU is blocked When vCPU is preempted/slept, we update the posted-interrupts during scheduling by

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

flight 83064 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/83064/ 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] MAINTAINERS: add myself as seabios maintainer

On Wed, 2016-02-17 at 16:47 +, Wei Liu wrote: > On Wed, Feb 17, 2016 at 11:45:58AM -0500, Konrad Rzeszutek Wilk > wrote: > > On Wed, Feb 17, 2016 at 09:48:28AM +, Ian Campbell wrote: > > >  > > > Acked-by: Ian Campbell > > > > Acked-by: Konrad Rzeszutek Wilk

Re: [Xen-devel] [PATCH] docs: document handling of metacharacter escape in xl disk format

Ian Campbell wrote: > Signed-off-by: Ian Campbell > Cc: Jim Fehlig > --- > docs/misc/xl-disk-configuration.txt | 18 ++ > 1 file changed, 18 insertions(+) > > diff --git a/docs/misc/xl-disk-configuration.txt >

[Xen-devel] [PATCH 2/4] m4/python: fix typo in LDFLAGS variable name

Reported-by: Jonathan Creekmore Signed-off-by: Doug Goldstein --- CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu

[Xen-devel] [PATCH 1/4] tools/configure: only require bcc/ld86/as86 when needed

bcc/ld86/as86 are only necessary when we build rombios and not always so failing the build when they aren't available should not happen if the user isn't building rombios. Signed-off-by: Doug Goldstein --- CC: Ian Jackson CC: Stefano Stabellini

[Xen-devel] [PATCH] hvmloader: Use xen/errno.h rather than the host systems errno.h

Signed-off-by: Andrew Cooper --- CC: Jan Beulich CC: Ian Campbell CC: Ian Jackson CC: Wei Liu CC: Doug Goldstein --- tools/firmware/hvmloader/xenbus.c |

Re: [Xen-devel] Is: PVH dom0 - MWAIT detection logic to get deeper C-states exposed in ACPI AML code. Was:Re: [PATCH v2 10/30] xen/x86: Annotate VM applicability in featureset

. snip.. > > Hmm, you're right, somehow I've managed to ignore the relevant > > lines grep reported. Yet - how do things work then, without the > > MWAIT feature flag currently getting cleared? > I have never observed it being used. Do you have some local patches in > the

Re: [Xen-devel] [PATCH] arm/monitor vm-events: Implement guest-request support

On Thu, Feb 18, 2016 at 1:08 PM, Razvan Cojocaru wrote: > On 02/18/2016 09:35 PM, Corneliu ZUZU wrote: > > This patch adds ARM support for guest-request monitor vm-events. > > > > Summary of changes: > > == Moved to common-side: > > *

Re: [Xen-devel] [PATCH 4/4] tools/configure: rerun autoconf

On 18/02/2016 21:31, Doug Goldstein wrote: > On 2/18/16 3:22 PM, Doug Goldstein wrote: >> Rerun autoconf to regenerate configure >> >> Signed-off-by: Doug Goldstein >> --- >> CC: Ian Jackson >> CC: Stefano Stabellini

Re: [Xen-devel] [PATCH 4/4] tools/configure: rerun autoconf

On 2/18/16 3:31 PM, Doug Goldstein wrote: > On 2/18/16 3:22 PM, Doug Goldstein wrote: >> Rerun autoconf to regenerate configure >> >> Signed-off-by: Doug Goldstein >> --- >> CC: Ian Jackson >> CC: Stefano Stabellini

Re: [Xen-devel] [PATCH 4/4] tools/configure: rerun autoconf

On 2/18/16 3:22 PM, Doug Goldstein wrote: > Rerun autoconf to regenerate configure > > Signed-off-by: Doug Goldstein > --- > CC: Ian Jackson > CC: Stefano Stabellini > CC: Ian Campbell >

[Xen-devel] [PATCH 4/4] tools/configure: rerun autoconf

Rerun autoconf to regenerate configure Signed-off-by: Doug Goldstein --- CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu --- tools/configure |

[Xen-devel] [PATCH 3/4] m4/python: fix checks for Python library support

AC_CHECK_LIB() was running gcc -Llib -lm -lutils conftest.c which on platforms that do as needed operations by default will result in underlinking. Instead AC_CHECK_LIB() suggests supplying the extra libraries necessary in a 5th argument. Signed-off-by: Doug Goldstein --- CC:

Re: [Xen-devel] [PATCH v3 5/5] mkelf32: Close those file descriptors in the error paths.

On Thu, Feb 18, 2016 at 09:45:30AM -0700, Jan Beulich wrote: > >>> On 18.02.16 at 17:39, wrote: > > Jan Beulich writes ("Re: [PATCH v3 5/5] mkelf32: Close those file > > descriptors > > in the error paths."): > >> On 12.02.16 at 04:08, wrote:

Re: [Xen-devel] [PATCH] arm/monitor vm-events: Implement guest-request support

On 02/18/2016 09:35 PM, Corneliu ZUZU wrote: > This patch adds ARM support for guest-request monitor vm-events. > > Summary of changes: > == Moved to common-side: > * XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST handling (moved from X86 > arch_monitor_domctl_event to common monitor_domctl) >

[Xen-devel] [PATCH] arm/monitor vm-events: Implement guest-request support

This patch adds ARM support for guest-request monitor vm-events. Summary of changes: == Moved to common-side: * XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST handling (moved from X86 arch_monitor_domctl_event to common monitor_domctl) * hvm_event_guest_request, hvm_event_traps (also added

Re: [Xen-devel] [PATCH RFC] osstest: add a cd-{insert/eject} test for Debian HVM

Roger Pau Monne writes ("[PATCH RFC] osstest: add a cd-{insert/eject} test for Debian HVM"): > It could/should be expanded to other guest types, but at least it's a start. > It should also test that the guest can correctly access the disk contents. > > The only supported toolstack for this test

Re: [Xen-devel] [PATCHv1 4/5] x86/viridian: set x87 FIP width to 4 for Windows guests

On 18/02/16 18:52, David Vrabel wrote: > diff --git a/xen/arch/x86/hvm/viridian.c b/xen/arch/x86/hvm/viridian.c > index 6bd844b..fb9f044 100644 > --- a/xen/arch/x86/hvm/viridian.c > +++ b/xen/arch/x86/hvm/viridian.c > @@ -148,6 +148,30 @@ static void dump_guest_os_id(const struct domain *d) >

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

On 18/02/16 18:52, David Vrabel wrote: > 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). ^ of FIP/FDP > diff --git

Re: [Xen-devel] [PATCHv1 2/5] tools/libxc: add xc_domain_get_param() and xc_domain_set_param()

On 18/02/16 18:52, David Vrabel wrote: > These are a thin wrapper around the XEN_DOMCTL_param hypercall. > > Signed-off-by: David Vrabel Reviewed-by: Andrew Cooper ___ Xen-devel mailing list

Re: [Xen-devel] [PATCHv1 1/5] domctl: Add op to get/set generic numeric parameters

On 18/02/16 18:52, David Vrabel wrote: > Add XEN_DOMCTL_param to get/set generic numeric parameters for a domain. > This should reduce the number of specialized domctls that need to be > added. > > Signed-off-by: David Vrabel As far as the code here goes, Reviewed-by:

[Xen-devel] [RFC PATCH 0/5] 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). 32-bit save/restore is always done for Windows guests and the toolstack may override the default behaviour. The first 2 patches add a domctl to get/set

[Xen-devel] [PATCHv1 4/5] x86/viridian: set x87 FIP width to 4 for Windows guests

Microsoft Windows always uses a 32-bit FPU state save/restore and expects the FCS/FDS to be saved/restored. Ensure that for these guests, the hypervisor does 32-bit save/restore to preserve FCS/FDS. These guests are identified by the write to the Guest OS ID MSR. This fixes an 0x3D BugCheck

[Xen-devel] [PATCHv1 1/5] domctl: Add op to get/set generic numeric parameters

Add XEN_DOMCTL_param to get/set generic numeric parameters for a domain. This should reduce the number of specialized domctls that need to be added. Signed-off-by: David Vrabel --- xen/arch/x86/domctl.c | 14 ++ xen/common/domctl.c | 11

[Xen-devel] [PATCHv1 5/5] x86/domctl: Add XEN_DOMCTL_PARAM_ARCH_X86_FIP_WIDTH parameter

Add a parameter to allow the toolstack to set the x87 FIP width in case the hypervisor's heuristics do the wrong thing. Signed-off-by: David Vrabel --- xen/arch/x86/domctl.c | 10 ++ xen/include/public/domctl.h | 1 + 2 files changed, 11 insertions(+)

[Xen-devel] [PATCHv1 3/5] 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

[Xen-devel] [PATCHv1 2/5] tools/libxc: add xc_domain_get_param() and xc_domain_set_param()

These are a thin wrapper around the XEN_DOMCTL_param hypercall. Signed-off-by: David Vrabel --- tools/libxc/include/xenctrl.h | 5 + tools/libxc/xc_domain.c | 35 +++ 2 files changed, 40 insertions(+) diff --git

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

flight 83012 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/83012/ 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] Current LibXL Status

Ian Campbell writes ("Re: [Xen-devel] Current LibXL Status"): > The only one I can find which isn't one of this is > in libxl__event_disaster, and that is only if the applications (or language > bindings) haven't provided a suitable disaster callback. libxl__event_disaster can currently happen in

Re: [Xen-devel] [PATCH] xen/x86: Map Xen code/data/bss with superpages

On 18/02/16 18:03, Andrew Cooper wrote: > And make use of NX and RO attributes wherever possible. > > Andrew Cooper (4): > xen: Introduce IS_ALIGNED() > xen/memguard: Drop memguard_init() entirely > xen/x86: Use 2M superpages for text/data/bss mappings > xen/x86: Unilaterally remove .init

[Xen-devel] libxl and malloc failure (Re: Current LibXL Status)

Andrew Cooper writes ("Re: [Xen-devel] Current LibXL Status"): > There really is a show-stopper, which I have stated before. > > Languages such as OCaml use -ENOMEM as a hint to run the garbage > collector some more. I expect Haskell is the same. This cannot possibly be true (if what you mean

[Xen-devel] [PATCH RFC] osstest: add a cd-{insert/eject} test for Debian HVM

It could/should be expanded to other guest types, but at least it's a start. It should also test that the guest can correctly access the disk contents. The only supported toolstack for this test is xl. Signed-off-by: Roger Pau Monné --- CC: Ian Jackson

[Xen-devel] [PATCH] xen/x86: Unilaterally remove .init mappings

Because of the new 2M alignment of .init and .bss, the existing memory guarding infrastructure causes a shattered 2M superpage with non-present entries for .init, and present entries for the alignment space. Do away with the difference in behaviour between debug and non-debug builds; always

[Xen-devel] [PATCH] xen/memguard: Drop memguard_init() entirely

It is not obvious what this code is doing. Most of it dates from 2007/2008, and there have been substantial changes in Xen's memory handling since then. It was previously optional, and isn't needed for any of the memguard infrastructure to function. The use of MAP_SMALL_PAGES causes needless

[Xen-devel] [PATCH] xen/x86: Use 2M superpages for text/data/bss mappings

This balloons the size of Xen in memory from 3.4MB to 12MB, because of the required alignment adjustments. However * All mappings are 2M superpages. * .text (and .init at boot) are the only sections marked executable. * .text and .rodata are marked read-only. Signed-off-by: Andrew Cooper

[Xen-devel] [PATCH] xen/x86: Map Xen code/data/bss with superpages

And make use of NX and RO attributes wherever possible. Andrew Cooper (4): xen: Introduce IS_ALIGNED() xen/memguard: Drop memguard_init() entirely xen/x86: Use 2M superpages for text/data/bss mappings xen/x86: Unilaterally remove .init mappings xen/arch/x86/mm.c | 24

[Xen-devel] [PATCH] xen: Introduce IS_ALIGNED()

And a few open-coded alignment checks which I encountered Signed-off-by: Andrew Cooper --- CC: Jan Beulich CC: Tim Deegan CC: Ian Campbell --- xen/arch/x86/mm.c | 8 xen/arch/x86/xen.lds.S

Re: [Xen-devel] Current LibXL Status

On Thu, 2016-02-18 at 17:39 +, Ian Campbell wrote: > On Thu, 2016-02-18 at 17:26 +, George Dunlap wrote: > > > According to them, the ocaml garbage collector never frees memory.  It > > grows its own internal heap as necessary, but it never reduces the > > size of its heap. > > Assume

Re: [Xen-devel] Current LibXL Status

On Thu, Feb 18, 2016 at 5:39 PM, Ian Campbell wrote: > On Thu, 2016-02-18 at 17:26 +, George Dunlap wrote: > >> According to them, the ocaml garbage collector never frees memory. It >> grows its own internal heap as necessary, but it never reduces the >> size of its

Re: [Xen-devel] Current LibXL Status

On Thu, Feb 18, 2016 at 5:26 PM, Ian Campbell wrote: > On Thu, 2016-02-18 at 17:19 +, Ian Jackson wrote: >> George Dunlap writes ("Re: [Xen-devel] Current LibXL Status"): >> > So what was the conclusion here? It looks like we've confirmed that >> > exit() is only

Re: [Xen-devel] Current LibXL Status

On Thu, 2016-02-18 at 17:26 +, George Dunlap wrote: > According to them, the ocaml garbage collector never frees memory.  It > grows its own internal heap as necessary, but it never reduces the > size of its heap. Assume that's true: Wow! Although, I presume this is a factor of the

Re: [Xen-devel] Current LibXL Status

On Thu, 2016-02-18 at 17:19 +, Ian Jackson wrote: > George Dunlap writes ("Re: [Xen-devel] Current LibXL Status"): > > So what was the conclusion here?  It looks like we've confirmed that > > exit() is only called: > > > > 1. In the case of a malloc() failure > > 2. in libxl-save-helper (a

Re: [Xen-devel] Current LibXL Status

On Thu, Nov 19, 2015 at 11:23 AM, Ian Campbell wrote: > create ! > title it libxl exit() on ENOMEM incompatible with gc'd languages > thanks > > On Thu, 2015-11-19 at 10:55 +, Andrew Cooper wrote: >> On 19/11/15 09:20, Ian Campbell wrote: >> > On Wed, 2015-11-18 at

Re: [Xen-devel] Current LibXL Status

On Thu, 2016-02-18 at 17:09 +, George Dunlap wrote: > On Thu, Nov 19, 2015 at 12:16 PM, Ian Campbell > wrote: > > On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote: > > > On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote: > > > > On Thu, 2015-11-19 at 11:33

Re: [Xen-devel] libxl_device handling for nic and vtmp

On Thu, Feb 18, 2016 at 06:19:07PM +0100, Olaf Hering wrote: > On Thu, Feb 18, Wei Liu wrote: > > > Sorry I don't follow. What do you mean by 1:1 copy? Why does it make the > > update unnecessary? > > The current code does: > > libxl_device_nic_init(_saved); > libxl_device_nic_copy(CTX,

Re: [Xen-devel] Current LibXL Status

George Dunlap writes ("Re: [Xen-devel] Current LibXL Status"): > So what was the conclusion here? It looks like we've confirmed that > exit() is only called: > > 1. In the case of a malloc() failure > 2. in libxl-save-helper (a separate process forked by the library) > 3. In

Re: [Xen-devel] [PATCH v3 08/10] xen: add capability to load initrd outside of initial mapping

On Thu, Feb 18, 2016 at 01:43:33PM +0100, Juergen Gross wrote: > On 18/02/16 12:18, Daniel Kiper wrote: > > On Wed, Feb 17, 2016 at 06:19:35PM +0100, Juergen Gross wrote: > >> Modern pvops linux kernels support an initrd not covered by the initial > >> mapping. This capability is flagged by an

Re: [Xen-devel] libxl_device handling for nic and vtmp

On Thu, Feb 18, Wei Liu wrote: > Sorry I don't follow. What do you mean by 1:1 copy? Why does it make the > update unnecessary? The current code does: libxl_device_nic_init(_saved); libxl_device_nic_copy(CTX, _saved, nic); nic->devid = libxl__device_nextid(gc, domid, "vif");

Re: [Xen-devel] [RFC Design Doc] Add vNVDIMM support for Xen

>>> On 01.02.16 at 06:44, wrote: > This design treats host NVDIMM devices as ordinary MMIO devices: Wrt the cachability note earlier on, I assume you're aware that with the XSA-154 changes we disallow any cachable mappings of MMIO by default. > (1) Dom0 Linux NVDIMM

Re: [Xen-devel] libxl_device handling for nic and vtmp

On Thu, Feb 18, 2016 at 05:54:38PM +0100, Olaf Hering wrote: > On Thu, Feb 18, Wei Liu wrote: > > > For example, user might not have specified mac address so the library > > generates one for (s)he. You don't want mac address to regenerate after > > save / restore or migration. But you don't

Re: [Xen-devel] [PATCH v3 03/10] xen: add elfnote.h to avoid using numbers instead of constants

On Thu, Feb 18, 2016 at 11:35:52AM +0100, Juergen Gross wrote: > On 18/02/16 11:30, Daniel Kiper wrote: > > On Wed, Feb 17, 2016 at 06:19:30PM +0100, Juergen Gross wrote: > >> Various features and parameters of a pv-kernel are specified via > >> elf notes in the kernel image. Those notes are part

[Xen-devel] [PATCH OSSTEST] crontab: adjust to remove "." from mg-list-all-branches output

The regex in mg-list-all-branches assumes that the BRANCHES= will either be a singleton entry separated from the following command by a hard tab or a single quoted list of space separated entries, however the xen-unstable-coverity line is singleton separated from the command by a single space.

Re: [Xen-devel] [PATCH v3 02/10] xen: reduce number of global variables in xen loader

On Thu, Feb 18, 2016 at 11:34:49AM +0100, Juergen Gross wrote: > On 18/02/16 11:22, Daniel Kiper wrote: > > On Wed, Feb 17, 2016 at 06:19:29PM +0100, Juergen Gross wrote: > >> The loader for xen paravirtualized environment is using lots of global > >> variables. Reduce the number by making them

Re: [Xen-devel] Current LibXL Status

On Thu, Nov 19, 2015 at 12:16 PM, Ian Campbell wrote: > On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote: >> On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote: >> > On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote: >> > > >> > > The majority of those are

Re: [Xen-devel] [PATCH v2 15/16] xenalyze: handle RTDS scheduler events

On Thu, 2016-02-18 at 17:06 +, George Dunlap wrote: > On 18/02/16 17:02, Dario Faggioli wrote: > > On Thu, 2016-02-18 at 15:28 +, George Dunlap wrote: > > >  > > > > +case TRC_SCHED_CLASS_EVT(RTDS, 2): /* > > > > RUNQ_PICK*/ > > > > +if(opt.dump_all) { > > > > + 

Re: [Xen-devel] [PATCH v2 15/16] xenalyze: handle RTDS scheduler events

On 18/02/16 17:02, Dario Faggioli wrote: > On Thu, 2016-02-18 at 15:28 +, George Dunlap wrote: >> On 16/02/16 18:13, Dario Faggioli wrote: >>> --- >>> tools/xentrace/xenalyze.c | 59 >>> + >>> 1 file changed, 59 insertions(+) >>> >>> diff --git

Re: [Xen-devel] Stabilising some tools only HVMOPs?

>>> On 18.02.16 at 17:28, wrote: > Wei Liu writes ("Re: Stabilising some tools only HVMOPs?"): >> I think we come to the conclusion that these HVMOPs should be made >> stable. And to do so I'm going to introduce a __XEN_TOOLS_STABLE__ macro >> for them to distinguish

Re: [Xen-devel] Is: PVH dom0 - MWAIT detection logic to get deeper C-states exposed in ACPI AML code. Was:Re: [PATCH v2 10/30] xen/x86: Annotate VM applicability in featureset

El 18/2/16 a les 16:12, Andrew Cooper ha escrit: > On 18/02/16 15:02, Roger Pau Monné wrote: >> El 17/2/16 a les 20:02, Konrad Rzeszutek Wilk ha escrit: >>> On Mon, Feb 15, 2016 at 03:41:41PM +, Andrew Cooper wrote: On 15/02/16 15:02, Jan Beulich wrote: On 15.02.16 at 15:53,

Re: [Xen-devel] [PATCH v2 13/16] xenalyze: handle Credit1 scheduler events

On Thu, 2016-02-18 at 15:31 +, George Dunlap wrote: > On 16/02/16 18:12, Dario Faggioli wrote: > >  > > diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c > > index 17021f1..4ab2dba 100644 > > --- a/tools/xentrace/xenalyze.c > > +++ b/tools/xentrace/xenalyze.c > > @@ -7673,6

Re: [Xen-devel] [PATCH v2 15/16] xenalyze: handle RTDS scheduler events

On Thu, 2016-02-18 at 15:28 +, George Dunlap wrote: > On 16/02/16 18:13, Dario Faggioli wrote: > > --- > >  tools/xentrace/xenalyze.c |   59 > > + > >  1 file changed, 59 insertions(+) > > > > diff --git a/tools/xentrace/xenalyze.c

Re: [Xen-devel] [PATCH v3 02/10] xen: reduce number of global variables in xen loader

On Thu, Feb 18, 2016 at 11:34:49AM +0100, Juergen Gross wrote: > On 18/02/16 11:22, Daniel Kiper wrote: > > On Wed, Feb 17, 2016 at 06:19:29PM +0100, Juergen Gross wrote: > >> The loader for xen paravirtualized environment is using lots of global > >> variables. Reduce the number by making them

Re: [Xen-devel] [PATCH v3 01/10] xen: make xen loader callable multiple times

On Thu, Feb 18, 2016 at 11:32:16AM +0100, Juergen Gross wrote: > On 18/02/16 11:12, Daniel Kiper wrote: > > On Wed, Feb 17, 2016 at 06:19:28PM +0100, Juergen Gross wrote: > >> The loader for xen paravirtualized environment isn't callable multiple > >> times as it won't free any memory in case of

Re: [Xen-devel] libxl_device handling for nic and vtmp

On Thu, Feb 18, Wei Liu wrote: > For example, user might not have specified mac address so the library > generates one for (s)he. You don't want mac address to regenerate after > save / restore or migration. But you don't want to preserve all > autogenerated state, so you use the original copy

Re: [Xen-devel] Stabilising some tools only HVMOPs?

On Thu, Feb 18, 2016 at 09:41:01AM -0700, Jan Beulich wrote: > >>> On 18.02.16 at 17:28, wrote: > > Wei Liu writes ("Re: Stabilising some tools only HVMOPs?"): > >> I think we come to the conclusion that these HVMOPs should be made > >> stable. And to do so I'm going to

Re: [Xen-devel] [PATCH v2 06/16] xen: sched: tracing: enable TSC tracing for all events

On Thu, 2016-02-18 at 11:43 +, George Dunlap wrote: > On 17/02/16 09:52, Dario Faggioli wrote: > >  > > For instance, the thing that you can just change on the fly the way > > a > > trace is shown (by tweaking the format file) looks an interesting > > feature to me, even considering all the

Re: [Xen-devel] Is: PVH dom0 - MWAIT detection logic to get deeper C-states exposed in ACPI AML code. Was:Re: [PATCH v2 10/30] xen/x86: Annotate VM applicability in featureset

On 18/02/16 16:24, Boris Ostrovsky wrote: > > > On 02/18/2016 10:12 AM, Andrew Cooper wrote: >> On 18/02/16 15:02, Roger Pau Monné wrote: >>> El 17/2/16 a les 20:02, Konrad Rzeszutek Wilk ha escrit: On Mon, Feb 15, 2016 at 03:41:41PM +, Andrew Cooper wrote: > On 15/02/16 15:02, Jan

Re: [Xen-devel] [PATCH v3 5/5] mkelf32: Close those file descriptors in the error paths.

>>> On 18.02.16 at 17:39, wrote: > Jan Beulich writes ("Re: [PATCH v3 5/5] mkelf32: Close those file descriptors > in the error paths."): >> On 12.02.16 at 04:08, wrote: >> > While we are operating here we may as well fix some of the >> > file

Re: [Xen-devel] Stabilising some tools only HVMOPs?

Jan Beulich writes ("Re: Stabilising some tools only HVMOPs?"): > On 18.02.16 at 17:28, wrote: > > Wei Liu writes ("Re: Stabilising some tools only HVMOPs?"): > >> I think we come to the conclusion that these HVMOPs should be made > >> stable. And to do so I'm going to

Re: [Xen-devel] [PATCH v3 10/10] xen: add capability to load p2m list outside of kernel mapping

On Wed, Feb 17, 2016 at 06:19:37PM +0100, Juergen Gross wrote: > Modern pvops linux kernels support a p2m list not covered by the > kernel mapping. This capability is flagged by an elf-note specifying > the virtual address the kernel is expecting the p2m list to be mapped > to. > > In case the

Re: [Xen-devel] [PATCH v3 5/5] mkelf32: Close those file descriptors in the error paths.

Jan Beulich writes ("Re: [PATCH v3 5/5] mkelf32: Close those file descriptors in the error paths."): > On 12.02.16 at 04:08, wrote: > > While we are operating here we may as well fix some of the > > file descriptor leaks. > > I'm not convinced. The added goto-s make the

Re: [Xen-devel] [PATCH v3 09/10] xen: modify page table construction

On Wed, Feb 17, 2016 at 06:19: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

Re: [Xen-devel] Stabilising some tools only HVMOPs?

On Thu, 2016-02-18 at 12:51 +, Wei Liu wrote: > On Wed, Feb 17, 2016 at 05:28:08PM +, Wei Liu wrote: > > Hi all > > > > Tools people are in the process of splitting libxenctrl into a set of > > stable libraries. One of the proposed libraries is libxendevicemodel > > which has a collection

Re: [Xen-devel] Stabilising some tools only HVMOPs?

On Thu, Feb 18, 2016 at 04:28:16PM +, Ian Jackson wrote: > Wei Liu writes ("Re: Stabilising some tools only HVMOPs?"): > > I think we come to the conclusion that these HVMOPs should be made > > stable. And to do so I'm going to introduce a __XEN_TOOLS_STABLE__ macro > > for them to distinguish

Re: [Xen-devel] [PATCH v3 5/5] mkelf32: Close those file descriptors in the error paths.

>>> On 12.02.16 at 04:08, wrote: > While we are operating here we may as well fix some of the > file descriptor leaks. I'm not convinced. The added goto-s make the code uglier to read, and this being a standalone utility there's not really any leak here. Jan

Re: [Xen-devel] Stabilising some tools only HVMOPs?

Wei Liu writes ("Re: Stabilising some tools only HVMOPs?"): > I think we come to the conclusion that these HVMOPs should be made > stable. And to do so I'm going to introduce a __XEN_TOOLS_STABLE__ macro > for them to distinguish from __XEN_TOOLS__. And then libxendevicemodel > will have

Re: [Xen-devel] Is: PVH dom0 - MWAIT detection logic to get deeper C-states exposed in ACPI AML code. Was:Re: [PATCH v2 10/30] xen/x86: Annotate VM applicability in featureset

On 02/18/2016 10:12 AM, Andrew Cooper wrote: On 18/02/16 15:02, Roger Pau Monné wrote: El 17/2/16 a les 20:02, Konrad Rzeszutek Wilk ha escrit: On Mon, Feb 15, 2016 at 03:41:41PM +, Andrew Cooper wrote: On 15/02/16 15:02, Jan Beulich wrote: On 15.02.16 at 15:53,

Re: [Xen-devel] [PATCH v3 MISSING/23] xsplice: Design document (v7).

>>> On 12.02.16 at 22:57, wrote: > +struct xsplice_patch_func { > +const char *name; > +Elf64_Xwordnew_addr; Missing space. > +Elf64_Xword old_addr; > +Elf64_Word new_size; > +Elf64_Word long old_size; There are still two types left here.

Re: [Xen-devel] [PATCH] travis: Drop bridge-utils and iproute2

On 2/18/16 8:36 AM, Andrew Cooper wrote: > These packages are not permitted inside travis, and are not necessary for > building Xen. > > Signed-off-by: Andrew Cooper > --- > CC: Doug Goldstein > CC: Ian Campbell > CC: Ian

Re: [Xen-devel] libxl_device handling for nic and vtmp

On Thu, Feb 18, 2016 at 04:13:21PM +0100, Olaf Hering wrote: > What is the point of libxl__update_config_nic and > libxl__update_config_vtmp? > > In libxl__device_type_add (called from DEFINE_DEVICE_ADD) the input > type is copied with libxl_device_type_copy to type_saved, which is a > 1:1 copy.

Re: [Xen-devel] False positive coverity bug id: 1351218

On 18/02/16 15:36, Harmandeep Kaur wrote: > This is about a Coverity bug (included in the end), which I think is > a false positive. I don't think pagesize can be zero in any case. > pagesize = 1 << (((flags >> TMEM_POOL_PAGESIZE_SHIFT) & > TMEM_POOL_PAGESIZE_MASK) +

Re: [Xen-devel] [PATCH] tools/xenalyze: Fix build with clang

On 12/02/16 19:06, Andrew Cooper wrote: > 1) EXIT_REASON_EXCEPTION_NMI is 0, and Clang complains: > > xenalyze.c:513:33: error: initializer overrides prior initialization of this > subobject [-Werror,-Winitializer-overrides] > [EXIT_REASON_EXCEPTION_NMI]="EXCEPTION_NMI", >

[Xen-devel] libxl_device handling for nic and vtmp

What is the point of libxl__update_config_nic and libxl__update_config_vtmp? In libxl__device_type_add (called from DEFINE_DEVICE_ADD) the input type is copied with libxl_device_type_copy to type_saved, which is a 1:1 copy. If needed, a new devid is assigned to the input. Later the copy is

  1   2   >