[Xen-devel] [qemu-upstream-unstable test] 34570: regressions - FAIL

flight 34570 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/34570/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-i386 11 guest-localmigrate fail REGR. vs. 33488 test-amd64

[Xen-devel] [PATCH v1 3/3] xen/arm: check for psci-0.2 dt node

From: Vijaya Kumar K Add psci-0.2 compatibility check while parsing psci dt node Signed-off-by: Vijaya Kumar K --- xen/arch/arm/domain_build.c |1 + 1 file changed, 1 insertion(+) diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c index c2dcb49..0be639b 100644 --- a/xe

[Xen-devel] [PATCH v1 2/3] xen/arm: Add early printk support for ThunderX platform

From: Vijaya Kumar K ThunderX platform uses pl011 uart. Signed-off-by: Vijaya Kumar K --- xen/arch/arm/Rules.mk |4 1 file changed, 4 insertions(+) diff --git a/xen/arch/arm/Rules.mk b/xen/arch/arm/Rules.mk index c7bd227..54efa91 100644 --- a/xen/arch/arm/Rules.mk +++ b/xen/arch/arm/

[Xen-devel] [PATCH v1 0/3] ThunderX platform support

From: Vijaya Kumar K Changes in v1: - Add support for ThunderX platform - Add early printk support - Add psci-0.2 check while parsing dt node Vijaya Kumar K (3): xen/arm: Add ThunderX platform support xen/arm: Add early printk support for ThunderX platform xen/arm: check for psci-0.2 d

[Xen-devel] [PATCH v1 1/3] xen/arm: Add ThunderX platform support

From: Vijaya Kumar K Add basic support for Cavium ThunderX platform Signed-off-by: Vijaya Kumar K --- xen/arch/arm/platforms/Makefile |1 + xen/arch/arm/platforms/thunderx.c | 66 + 2 files changed, 67 insertions(+) diff --git a/xen/arch/arm/platfor

Re: [Xen-devel] [PATCH v1 0/3] ThunderX platform support

Please ignore this series. I have missed to update processor_implementers[] with cavium in xen/arch/arm/setup.c Sending v2 version On Mon, Feb 16, 2015 at 2:36 PM, wrote: > From: Vijaya Kumar K > > Changes in v1: > - Add support for ThunderX platform > - Add early printk support > - Add psc

Re: [Xen-devel] [PATCH v2] xen/arm: allow console=hvc0 to be omitted for guests

On 13 February 2015 at 15:17, Julien Grall wrote: > > > On 13/02/2015 15:12, Ard Biesheuvel wrote: >> >> On 13 February 2015 at 15:03, Julien Grall >> wrote: >>> >>> Hi Ard, >>> >>> >>> On 12/02/2015 19:29, Ard Biesheuvel wrote: This patch registers hvc0 as the preferred console if

Re: [Xen-devel] [PATCH v2] xen/arm: allow console=hvc0 to be omitted for guests

Hi Ard, On 16/02/15 09:37, Ard Biesheuvel wrote: > On 13 February 2015 at 15:17, Julien Grall wrote: >> >> >> On 13/02/2015 15:12, Ard Biesheuvel wrote: >>> >>> On 13 February 2015 at 15:03, Julien Grall >>> wrote: Hi Ard, On 12/02/2015 19:29, Ard Biesheuvel wrote: >

Re: [Xen-devel] [PATCH for-4.6 0/5] xen: arm: Parse PCI DT nodes' ranges and interrupt-map

Hi Suravee, On 16/02/15 03:49, Suravee Suthikulpanit wrote: > On 10/24/2014 04:58 AM, Ian Campbell wrote: >> This message has been archived. View the original item >>

Re: [Xen-devel] [PATCH OSSTEST 11/12] Changes on test step of debain hvm guest install

On Sun, Feb 15, 2015 at 09:43:33AM +, Hu, Robert wrote: > > -Original Message- > > From: Ian Jackson [mailto:ian.jack...@eu.citrix.com] > > Sent: Friday, February 13, 2015 8:03 PM > > To: Hu, Robert > > Cc: xen-devel@lists.xen.org; jfeh...@suse.com; wei.l...@citrix.com; > > ian.campb...

Re: [Xen-devel] Vmap allocator fails to allocate beyond 128MB

Hi Ian, For ThunderX/arm64 this issue needs to be fixed. Could you please comment on this? I could think of below 1) Add new call for ARM under CONFIG_ARM_32/CONFIG_ARM_64 in vm_init() and manage map_pages_to_xen(va, 0, vm_low - nr, MAP_SMALL_PAGES); with different function call for ar

Re: [Xen-devel] Vmap allocator fails to allocate beyond 128MB

On 16/02/15 10:17, Vijay Kilari wrote: Hello Vijay, > For ThunderX/arm64 this issue needs to be fixed. > Could you please comment on this? AFAICS, x86 is also using a 1G area for the vmap. Does it mean that x86 never use vmap for more than 128M? > I could think of below > > 1) Add ne

Re: [Xen-devel] Vmap allocator fails to allocate beyond 128MB

On Mon, Feb 16, 2015 at 3:58 PM, Julien Grall wrote: > On 16/02/15 10:17, Vijay Kilari wrote: > > Hello Vijay, > >> For ThunderX/arm64 this issue needs to be fixed. >> Could you please comment on this? > > AFAICS, x86 is also using a 1G area for the vmap. Does it mean that x86 > never use vmap f

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

flight 34574 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/34574/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail pass in 34529 test-armhf-armhf-libvirt 13 gu

Re: [Xen-devel] Vmap allocator fails to allocate beyond 128MB

On 16/02/15 10:50, Vijay Kilari wrote: > On Mon, Feb 16, 2015 at 3:58 PM, Julien Grall wrote: >> On 16/02/15 10:17, Vijay Kilari wrote: >> >> Hello Vijay, >> >>> For ThunderX/arm64 this issue needs to be fixed. >>> Could you please comment on this? >> >> AFAICS, x86 is also using a 1G area for t

Re: [Xen-devel] Vmap allocator fails to allocate beyond 128MB

On 16/02/15 10:57, Julien Grall wrote: > On 16/02/15 10:50, Vijay Kilari wrote: >> On Mon, Feb 16, 2015 at 3:58 PM, Julien Grall >> wrote: >>> On 16/02/15 10:17, Vijay Kilari wrote: >>> >>> Hello Vijay, >>> For ThunderX/arm64 this issue needs to be fixed. Could you please comment on t

Re: [Xen-devel] PML (Page Modification Logging) design for Xen

On 14/02/15 03:01, Kai Huang wrote: >>> This will only function correctly if superpage shattering is used. >>> >>> As soon as a superpage D bit transitions from 0 to 1, the gfn is logged >>> and the guest can make further updated in the same frame without further >>> log entries being recorded. The

Re: [Xen-devel] [PATCH 3/3] mini-os: sort objects in binary archives

On Thu, Feb 05, Ian Campbell wrote: > On Tue, 2015-02-03 at 12:45 +0100, Olaf Hering wrote: > > When building stubdom the mini-os objects are also linked into the > > binary. Unfortunately the linker will place them in the order found in > > the archive. Since this order is random the resulting st

Re: [Xen-devel] [PATCH RFC 00/20] Change parts of the shadow interface to be domain based

Hi, Thanks for this; I think the code looks a lot saner with all the vcpu<->domain fiddling removed. :) At 17:15 + on 12 Feb (1423757759), Andrew Cooper wrote: > The purpose of this series is to prevent toolstack entry points into the > shadow code from passing d->vcpu[0] for actions which ar

[Xen-devel] Xen 4.6 Development Update

Hi all We are now one month into 4.6 development window. This is an email to keep track of all the patch series I gathered. It is by no means complete and / or acurate. Feel free to reply this email with new projects or correct my misunderstanding. = Timeline = We are planning on a 9-month relea

Re: [Xen-devel] [rumpuserxen test] 34575: regressions - FAIL

On 15/02/15 18:51, xen.org wrote: flight 34575 rumpuserxen real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/34575/ Regressions :-( This looks like a new failure: === snip === checking for ncurses.h... no configure: error: Unable to find a suitable curses library configure: error: .

Re: [Xen-devel] [PATCH RFC 00/20] Change parts of the shadow interface to be domain based

On 16/02/15 12:29, Tim Deegan wrote: > Hi, > > Thanks for this; I think the code looks a lot saner with all the > vcpu<->domain fiddling removed. :) > > At 17:15 + on 12 Feb (1423757759), Andrew Cooper wrote: >> The purpose of this series is to prevent toolstack entry points into the >> shadow

Re: [Xen-devel] [PATCH v1 3/3] xen/arm: check for psci-0.2 dt node

Hi Vijay, On 16/02/15 09:06, vijay.kil...@gmail.com wrote: > From: Vijaya Kumar K > > Add psci-0.2 compatibility check while parsing psci dt node Reading the commit title/description gives the impression that you are adding support with PSCI 0.2. While it has been added in Xen 4.5, this patch

Re: [Xen-devel] [PATCH v3 7/7] libxl: Add interface for querying hypervisor about PCI topology

On Mon, 2015-02-09 at 15:04 -0500, Boris Ostrovsky wrote: > .. and use this new interface to display it along with CPU topology > and NUMA information when 'xl info -n' command is issued > > The output will look like > ... > cpu_topology : > cpu:coresocket node > 0: 0

Re: [Xen-devel] [PATCH] tools/hotplug: introduce XENSTORED_ARGS= in sysconfig file.

On Fri, Feb 13, Ian Jackson wrote: > Olaf Hering writes ("[PATCH] tools/hotplug: introduce XENSTORED_ARGS= in > sysconfig file."): > > It is already used in the runlevel script and the service file. It is > > supposed to replace XENSTORED_TRACE= boolean, which cant be easily > > supported in the

Re: [Xen-devel] [PATCH v3 1/7] x86/numa: Make use of NUMA_NO_NODE consistent

On Tue, 2015-02-10 at 10:41 +, Andrew Cooper wrote: > On 09/02/15 20:04, Boris Ostrovsky wrote: > > diff --git a/xen/arch/x86/srat.c b/xen/arch/x86/srat.c > > index 29fc724..4dfa1c3 100644 > > --- a/xen/arch/x86/srat.c > > +++ b/xen/arch/x86/srat.c > > @@ -21,13 +21,16 @@ > > #include > > #

Re: [Xen-devel] PML (Page Modification Logging) design for Xen

On Fri, Feb 13, 2015 at 10:50 AM, Kai Huang wrote: > > On 02/12/2015 08:34 PM, Tim Deegan wrote: >> >> Hi, >> >> Thanks for posting this design! >> >> At 16:28 +0800 on 11 Feb (1423668493), Kai Huang wrote: >>> >>> Design >>> == >>> >>> - PML feature is used globally >>> >>> A new Xen boot par

Re: [Xen-devel] [MirageOS-devel] 2015 GSoC Application : Tick

MirageOS projects are done. I edited the Xen GSoC wiki page with one item that points to our curated list at: https://github.com/mirage/mirage-www/wiki/Pioneer-Projects AC On 13 Feb 2015, at 17:00, Lars Kurth wrote: > Just a quick note that I filled out the GSoC Mentoring Organisation > ap

Re: [Xen-devel] PML (Page Modification Logging) design for Xen

On Mon, Feb 16, 2015 at 7:44 PM, Andrew Cooper wrote: > On 14/02/15 03:01, Kai Huang wrote: This will only function correctly if superpage shattering is used. As soon as a superpage D bit transitions from 0 to 1, the gfn is logged and the guest can make further updated in the s

Re: [Xen-devel] [PATCH v3 3/7] sysctl: Make topologyinfo and numainfo sysctls a little more efficient

On Mon, 2015-02-09 at 15:04 -0500, Boris Ostrovsky wrote: > Currently both of these sysctls make a copy to userspace for each index of > various query arrays. We should try to copy whole arrays instead. > > This requires some changes in sysctl's public data structure, thus bump > interface version

Re: [Xen-devel] [PATCH v3 5/7] libxl/libxc: Move libxl_get_cpu_topology()'s hypercall buffer management to libxc

On Mon, 2015-02-09 at 15:04 -0500, Boris Ostrovsky wrote: > Signed-off-by: Boris Ostrovsky > Reviewed-by: Dario Faggioli Just one thing: > --- a/tools/libxl/libxl.c > +++ b/tools/libxl/libxl.c > @@ -5072,38 +5072,23 @@ int libxl_get_physinfo(libxl_ctx *ctx, libxl_physinfo > *physinfo) > libxl

Re: [Xen-devel] Xen 4.6 Development Update

writes: > Hi all > > We are now one month into 4.6 development window. This is an email to keep > track of all the patch series I gathered. It is by no means complete and / or > acurate. Feel free to reply this email with new projects or correct my > misunderstanding. Hi Wei, I have my "[PATCH

[Xen-devel] [PATCH] tools/configure: detect $host_vendor of rumprun, not just rumpxen [and 1 more messages]

Antti Kantee writes ("Re: [rumpuserxen test] 34575: regressions - FAIL"): > On 15/02/15 18:51, xen.org wrote: > > flight 34575 rumpuserxen real [real] > > http://www.chiark.greenend.org.uk/~xensrcts/logs/34575/ > > > > Regressions :-( > > This looks like a new failure: > === snip === > checking fo

Re: [Xen-devel] [PATCH v5 01/24] xen: dump vNUMA information with debug key "u"

On Fri, 2015-02-13 at 11:50 +, Andrew Cooper wrote: > On 12/02/15 19:44, Wei Liu wrote: > > Signed-off-by: Elena Ufimsteva > > Signed-off-by: Wei Liu > > Cc: Jan Beulich > > Reviewed-by: Andrew Cooper Reviewed-by: Dario Faggioli Regards, Dario signature.asc Description: This is a digi

Re: [Xen-devel] [PATCH v5 04/24] libxc: add p2m_size to xc_dom_image

On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > Add a new field p2m_size to keep track of the number of pages covert by > Here and in the code (comment): is it 'covert' or 'covered' (or maybe even something else)? In any case... > p2m. Change total_pages to p2m_size in functions which in fac

Re: [Xen-devel] Xen 4.6 Development Update

On 16/02/15 12:38, wei.l...@citrix.com wrote: > > = Prognosis = Does anyone find this section useful? I imagine its a non-trivial amount of work to keep up-to-date. Tracking Linux series in this way also doesn't make sense to me as the release cycles don't line up. David _

Re: [Xen-devel] [PATCH v2] libxc: introduce a per architecture scratch pfn for temporary grant mapping

Ian Jackson writes ("Re: [PATCH v2] libxc: introduce a per architecture scratch pfn for temporary grant mapping"): > Ian Campbell writes ("Re: [PATCH v2] libxc: introduce a per architecture > scratch pfn for temporary grant mapping"): > > Ian, Julien has suggested this for backport to 4.5 but not

Re: [Xen-devel] [PATCH v2] rump kernels: use new platform macro [and 1 more messages]

Ian Jackson writes ("Re: [PATCH v2] rump kernels: use new platform macro"): > Wei Liu writes ("[PATCH v2] rump kernels: use new platform macro"): > > Starting from rump kernel changeset 91d5623 ("Renaming platform macros, > > app-tools and autoconf target string"), __RUMPUSER_XEN__ and __RUMPAPP__

Re: [Xen-devel] [PATCH v5 04/24] libxc: add p2m_size to xc_dom_image

On Mon, Feb 16, 2015 at 02:46:54PM +, Dario Faggioli wrote: > On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > > Add a new field p2m_size to keep track of the number of pages covert by > > > Here and in the code (comment): is it 'covert' or 'covered' (or maybe > even something else)? Should

Re: [Xen-devel] Xen 4.6 Development Update

On 16/02/15 13:24, Julien Grall wrote: > (Strimming the cc list) Sorry I forgot to add back xen-devel. > On 16/02/15 12:38, wei.l...@citrix.com wrote: >> Hi all > > Hi Wei, > >> We are now one month into 4.6 development window. This is an email to keep >> track of all the patch series I gather

[Xen-devel] [PATCH v3 01/15] xen/arm: vgic-v3: Correctly set GICD_TYPER.IDbits

>From Linux 3.19, the GICv3 drivers is using GICD_TYPER.IDbits to check the validity of the hardware interrupt number. The field IDBits in the register GICD_TYPER is used to know the number of interrupt identifiers (SPI, PPIs, SGIs, LPIs) supported by GIC Stream Protocol Interface. This field con

[Xen-devel] [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC

Hello, The first goal of this series is to fix Linux 3.19 DOM0 boot on GICv3 systems (see patch #1). It turns out to a bigger series because there were some outstanding bugs in the vGIC emulation. The most important one is the way we emulate the re-distributor. Each re-distributor should be assoc

[Xen-devel] [PATCH v3 03/15] xen/arm: vgic-v3: Correctly handle GICD_CTLR

As backward GICv2 compatibility is not supported in the vGICv3 driver, the bit ARE_NS is RAO/WI. Furthermore, when ARE_NS is set, the guest can only modify EnableGrp1A. At same time take the vgic_lock to write into domain.arch.vgic.ctrl. It was already taken during read. Signed-off-by: Julien Gr

[Xen-devel] [PATCH v3 02/15] xen/arm: vgic-v3: Correctly set GICD_TYPER.CPUNumber

On GICv3, the value (CPUNumber + 1) indicates the number of processor that may be used as interrupts targets when ARE bit is zero. The maximum is 8 processors. Signed-off-by: Julien Grall Acked-by: Ian Campbell --- The current code of the vGIC doesn't support ARE = 0. Nonetheless, the pa

[Xen-devel] [PATCH v3 13/15] xen/arm: vgic-v2: GICD_I{S, C}PENDR* are only word-accessible

Signed-off-by: Julien Grall Acked-by: Ian Campbell --- This patch is candidate for backporting to Xen 4.4 and Xen 4.5. Although, this patch won't apply directly to Xen 4.4. Changes in v3: - Add Ian's ack Changes in v2: - Patch added --- xen/arch/arm/vgic-v2.c

[Xen-devel] [PATCH v3 06/15] xen/arm: vgic-v3: Set stride during domain initialization

The stride may not be set if the hardware GIC is using the default layout. It happens on the Foundation model. On GICv3, the default stride is 2 * 64K. Therefore it's possible to avoid checking at every redistributor MMIO access if the stride is not set. Because domU uses a static stride configur

[Xen-devel] [PATCH v3 14/15] xen/arm: vgic: Drop iactive, ipend, pendsgi field

The current VGIC code doesn't support to change the pending and active status of an IRQ via the (re-)distributor. Futhermore, all the access size wasn't support correctly and some registers was implemented as write-ignore. The latter make very difficult for a kernel developer to find that we don't

[Xen-devel] [PATCH v3 12/15] xen/arm: vgic-v2: Take the lock when writing into GICD_CTLR

This register is shared between every vCPUs and the lock was already taken for read. Signed-off-by: Julien Grall Acked-by: Ian Campbell --- This patch should be backported to Xen 4.4 and Xen 4.5. Although, it won't apply directly for Xen 4.4. Changes in v2: - Add Ian's ack

[Xen-devel] [PATCH v3 08/15] xen/arm: vgic-v3: Emulate correctly the re-distributor

There is a one-to-one mapping between each re-distributors and processors. Each re-distributors can be accessed by any processor at any time. For instance during the initialization of the GIC, the drivers will browse the re-distributor to find the one associated to the current processor (via GICR_T

[Xen-devel] [PATCH v3 09/15] xen/arm: vgic-v3: Clarify which distributor is used in the common emulation

The messages in the common emulation doesn't specify which distributor (redistributor or distributor) is used. This make difficult to find the correct registers. Signed-off-by: Julien Grall Acked-by: Ian Campbell --- Changes in v3: - Add Ian's ack Changes in v2: - Patch

[Xen-devel] [PATCH v3 07/15] xen/arm: vgic-v3: Use a struct to describe contiguous rdist regions

Also update the different comment to make clear that we register one MMIO region per contiguous regions and not per re-distributor. Signed-off-by: Julien Grall Acked-by: Ian Campbell --- Changes in v3: - Add Ian's ack Changes in v2: - Patch added --- xen/arch/arm/gic-v

[Xen-devel] [PATCH v3 04/15] xen/arm: vgic-v3: Correctly handle RAZ/WI registers

Some of the registers are accessible via multiple size (see GICD_IPRIORITYR*). Those registers are incorrectly implemented when they should be RAZ. Only word-access size are currently allowed for them. The paragraph 5.3.1 in the GICv3 spec (PRD03-GENC-010745 24.0) indicates the different access-s

[Xen-devel] [PATCH v3 15/15] xen/arm: gic-v3: Update some comments in the code

- Drop wrong comment about the default stride. It's not always 2 * SZ_64K. When the re-distributor support VLPIs (from GICv4), the default stride is 4 * SZ_64K - Explain why SZ_64K * 2 Signed-off-by: Julien Grall --- Changes in v3: - Update commit message Change

[Xen-devel] [PATCH v3 10/15] xen/arm: vgic-v2: Correctly set GICD_TYPER.CPUNumber

The number of implemented CPU interfaces is one more than the value of this field. Also avoid hardcoding the shift and remove useless mask. Signed-off-by: Julien Grall Acked-by: Ian Campbell --- This patch should be backported to Xen 4.4 and Xen 4.5. Although this patch won't apply di

[Xen-devel] [PATCH v3 05/15] xen/arm: vgic-v3: Correctly implement read into GICR_NSACR

The 32-bit register GICR_NSACR is RAZ/WI on non-secure state. Therefore we should not inject a data abort to the guest. Signed-off-by: Julien Grall Acked-by: Ian Campbell --- This patch should be backport to Xen 4.5. The current implementation will inject a data abort into the guest.

[Xen-devel] [PATCH v3 11/15] xen/arm: vgic-v2: Correctly handle RAZ/WI registers

All the GICv2 registers are word-accessible. Some them are also byte-accessible (see GICD_IPRIORITYR*). Those registers are incorrectly implemented when they should be RAZ. Only word-access size are currently allowed for them. To avoid further issues, introduce different label following the acces

Re: [Xen-devel] [PATCH qemu-trad] cirrus: fix an uninitialized variable

Ian Jackson writes ("Re: [PATCH qemu-trad] cirrus: fix an uninitialized variable"): > Jan Beulich writes ("[PATCH qemu-trad] cirrus: fix an uninitialized > variable"): > > Noticed by paying attention to a compiler warning (reported for the > > only caller of the function modified, vga_ioport_read

Re: [Xen-devel] [PATCH v2] libxc: introduce a per architecture scratch pfn for temporary grant mapping

On 16/02/15 14:49, Ian Jackson wrote: > Ian Jackson writes ("Re: [PATCH v2] libxc: introduce a per architecture > scratch pfn for temporary grant mapping"): >> Ian Campbell writes ("Re: [PATCH v2] libxc: introduce a per architecture >> scratch pfn for temporary grant mapping"): >>> Ian, Julien ha

Re: [Xen-devel] [PATCH v5 06/24] libxl: introduce vNUMA types

On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > A domain can contain several virtual NUMA nodes, hence we introduce an > array in libxl_domain_build_info. > > libxl_vnode_info contains the size of memory in that node, the distance > from that node to every nodes, the underlying pnode and a bit

Re: [Xen-devel] [PATCH v5 06/24] libxl: introduce vNUMA types

On Mon, Feb 16, 2015 at 02:58:32PM +, Dario Faggioli wrote: > On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > > A domain can contain several virtual NUMA nodes, hence we introduce an > > array in libxl_domain_build_info. > > > > libxl_vnode_info contains the size of memory in that node, th

Re: [Xen-devel] Xen 4.6 Development Update

On Mon, Feb 16, 2015 at 02:39:40PM +, David Vrabel wrote: > On 16/02/15 12:38, wei.l...@citrix.com wrote: > > > > = Prognosis = > > Does anyone find this section useful? > I do find it useful. > I imagine its a non-trivial amount of work to keep up-to-date. > Yes. But it's better than lo

Re: [Xen-devel] Xen 4.6 Development Update

Thanks. I will update my list. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.6 Development Update

On Mon, Feb 16, 2015 at 03:20:44PM +0100, Vitaly Kuznetsov wrote: > writes: > > > Hi all > > > > We are now one month into 4.6 development window. This is an email to keep > > track of all the patch series I gathered. It is by no means complete and / > > or > > acurate. Feel free to reply this e

Re: [Xen-devel] [PATCH v3 7/7] libxl: Add interface for querying hypervisor about PCI topology

On 02/16/2015 08:45 AM, Dario Faggioli wrote: @@ -1070,6 +1078,12 @@ void libxl_vminfo_list_free(libxl_vminfo *list, int nb_vm); libxl_cputopology *libxl_get_cpu_topology(libxl_ctx *ctx, int *nb_cpu_out); void libxl_cputopology_list_free(libxl_cputopology *, int nb_cpu); +#ifdef LIBXL_H

Re: [Xen-devel] [PATCH v5 06/24] libxl: introduce vNUMA types

On Mon, 2015-02-16 at 15:17 +, Wei Liu wrote: > On Mon, Feb 16, 2015 at 02:58:32PM +, Dario Faggioli wrote: > > > +libxl_vnode_info = Struct("vnode_info", [ > > > +("memkb", MemKB), > > > +("distances", Array(uint32, "num_distances")), # distances from this > > > node to other nod

Re: [Xen-devel] [PATCH v3 3/7] sysctl: Make topologyinfo and numainfo sysctls a little more efficient

On 02/16/2015 09:08 AM, Dario Faggioli wrote: On Mon, 2015-02-09 at 15:04 -0500, Boris Ostrovsky wrote: Currently both of these sysctls make a copy to userspace for each index of various query arrays. We should try to copy whole arrays instead. This requires some changes in sysctl's public data

Re: [Xen-devel] Xen 4.6 Development Update

Il 16/02/2015 16:21, Wei Liu ha scritto: On Mon, Feb 16, 2015 at 02:39:40PM +, David Vrabel wrote: On 16/02/15 12:38, wei.l...@citrix.com wrote: = Prognosis = Does anyone find this section useful? I do find it useful. I also find it useful, thanks. If can be useful there is also small

Re: [Xen-devel] [PATCH v5 07/24] libxl: add vmemrange to libxl__domain_build_state

On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > A vnode consists of one or more vmemranges (virtual memory range). One > example of multiple vmemranges is that there is a hole in one vnode. > > Currently we haven't exported vmemrange interface to libxl user. > Vmemranges are generated during

Re: [Xen-devel] [PATCH v3 7/7] libxl: Add interface for querying hypervisor about PCI topology

On Mon, 2015-02-16 at 10:54 -0500, Boris Ostrovsky wrote: > I am not sure what the standard practice is for LIBXL_HAVE_ macros. I > see a couple of examples where '#ifdef LIBXL_HAVE_*" is used in libxl > code, which is why I have it here as well. > Yes, that is the case for two of them, AFAICS:

Re: [Xen-devel] [PATCH v5 06/24] libxl: introduce vNUMA types

On Mon, Feb 16, 2015 at 03:56:21PM +, Dario Faggioli wrote: > On Mon, 2015-02-16 at 15:17 +, Wei Liu wrote: > > On Mon, Feb 16, 2015 at 02:58:32PM +, Dario Faggioli wrote: > > > > > +libxl_vnode_info = Struct("vnode_info", [ > > > > +("memkb", MemKB), > > > > +("distances", Arr

Re: [Xen-devel] [PATCH v5 07/24] libxl: add vmemrange to libxl__domain_build_state

On Mon, Feb 16, 2015 at 04:00:19PM +, Dario Faggioli wrote: > On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > > A vnode consists of one or more vmemranges (virtual memory range). One > > example of multiple vmemranges is that there is a hole in one vnode. > > > > Currently we haven't expo

Re: [Xen-devel] [PATCH V5] x86 spinlock: Fix memory corruption on completing completions

On 15/02/15 17:30, Raghavendra K T wrote: > --- a/arch/x86/xen/spinlock.c > +++ b/arch/x86/xen/spinlock.c > @@ -41,7 +41,7 @@ static u8 zero_stats; > static inline void check_zero(void) > { > u8 ret; > - u8 old = ACCESS_ONCE(zero_stats); > + u8 old = READ_ONCE(zero_stats); > i

Re: [Xen-devel] [PATCH v3 7/7] libxl: Add interface for querying hypervisor about PCI topology

On Mon, Feb 16, 2015 at 10:54:11AM -0500, Boris Ostrovsky wrote: [...] > >>+if (valid_devs == 0) > >>+printf("No device topology data available\n"); > >>+ > >>+libxl_pcitopology_list_free(pciinfo, nr); > >>+#endif > >> > >And for implementation too, I think. > > > I am not sure wh

Re: [Xen-devel] [PATCH v5 06/24] libxl: introduce vNUMA types

On Mon, 2015-02-16 at 16:11 +, Wei Liu wrote: > On Mon, Feb 16, 2015 at 03:56:21PM +, Dario Faggioli wrote: > > On Mon, 2015-02-16 at 15:17 +, Wei Liu wrote: > > > And there is no way to > > > specify priority among the group of nodes you specify with a single > > > bitmap. > > > > >

Re: [Xen-devel] [PATCH v5 05/24] libxc: allocate memory with vNUMA information for PV guest

On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > @@ -760,7 +760,8 @@ static int x86_shadow(xc_interface *xch, domid_t domid) > int arch_setup_meminit(struct xc_dom_image *dom) > { > int rc; > -xen_pfn_t pfn, allocsz, i, j, mfn; > +xen_pfn_t pfn, allocsz, mfn, total, pfn_base; > +

Re: [Xen-devel] [PATCH v5 09/24] libxl: x86: factor out e820_host_sanitize

On Fri, 2015-02-13 at 15:42 +, Andrew Cooper wrote: > On 12/02/15 19:44, Wei Liu wrote: > > This function gets the machine E820 map and sanitize it according to PV > > guest configuration. > > > > This will be used in later patch. No functional change introduced in > > this patch. > > > > Signe

Re: [Xen-devel] [PATCH v5 06/24] libxl: introduce vNUMA types

On Mon, Feb 16, 2015 at 04:51:43PM +, Dario Faggioli wrote: > On Mon, 2015-02-16 at 16:11 +, Wei Liu wrote: > > On Mon, Feb 16, 2015 at 03:56:21PM +, Dario Faggioli wrote: > > > On Mon, 2015-02-16 at 15:17 +, Wei Liu wrote: > > > > > And there is no way to > > > > specify priority

Re: [Xen-devel] [PATCH v5 05/24] libxc: allocate memory with vNUMA information for PV guest

On Mon, Feb 16, 2015 at 04:58:11PM +, Dario Faggioli wrote: > On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote: > > > @@ -760,7 +760,8 @@ static int x86_shadow(xc_interface *xch, domid_t domid) > > int arch_setup_meminit(struct xc_dom_image *dom) > > { > > int rc; > > -xen_pfn_t pfn

Re: [Xen-devel] PML (Page Modification Logging) design for Xen

Hi, At 22:01 +0800 on 16 Feb (1424120474), Kai Huang wrote: > On Fri, Feb 13, 2015 at 10:50 AM, Kai Huang wrote: > > > > On 02/12/2015 08:34 PM, Tim Deegan wrote: > >> > >> Hi, > >> > >> Thanks for posting this design! > >> > >> At 16:28 +0800 on 11 Feb (1423668493), Kai Huang wrote: > >>> > >>>

[Xen-devel] [PATCH] tools/xenconsoled: Increase file descriptor limit

XenServer's VM density testing uncovered a regression when moving from sysvinit to systemd where the file descriptor limit dropped from 4096 to 1024. (XenServer had previously inserted a ulimit statement into its initscripts.) One solution is to use LimitNOFILE=4096 in xenconsoled.service to match

Re: [Xen-devel] [PATCH RFC 00/20] Change parts of the shadow interface to be domain based

At 13:35 + on 16 Feb (1424090147), Andrew Cooper wrote: > On 16/02/15 12:29, Tim Deegan wrote: > > Hi, > > > > Thanks for this; I think the code looks a lot saner with all the > > vcpu<->domain fiddling removed. :) > > > > At 17:15 + on 12 Feb (1423757759), Andrew Cooper wrote: > >> The pur

[Xen-devel] [ovmf test] 34582: regressions - FAIL

flight 34582 ovmf real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/34582/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 7 debian-hvm-install fail REGR. vs. 33686 test-amd64-i386-xl-qemuu-ovm

Re: [Xen-devel] [PATCH v5 22/24] libxlu: introduce new APIs

On Fri, Feb 13, 2015 at 02:12:29PM +, Ian Jackson wrote: > Wei Liu writes ("[PATCH v5 22/24] libxlu: introduce new APIs"): > > These APIs can be used to manipulate XLU_ConfigValue and XLU_ConfigList. > > > > +if (value->type != XLU_STRING) { > > +if (!dont_warn) > > +fp

Re: [Xen-devel] pvSCSI test

On Monday, February 16, 2015 07:32, Juergen Gross wrote: > To: Kristian Hagsted Rasmussen; Olaf Hering; xen-de...@lists.xensource.com > Subject: Re: [Xen-devel] pvSCSI test > > On 02/12/2015 05:43 PM, Kristian Hagsted Rasmussen wrote: >> On Monday, February 9, 2015 07:02, Juergen Gross wrote: >>

Re: [Xen-devel] [PATCH v5 22/24] libxlu: introduce new APIs

On Mon, Feb 16, 2015 at 07:10:46PM +, Wei Liu wrote: [...] > > (being a function or macro which always returns EINVAL), or some such. > > > > Do feel very keen about this since the format string differs from Don't... > functions. And it's only one printf anyway. > > Wei. > > > Thanks, > >

[Xen-devel] Bug nestedhvm: staging-4.5, stable-4.5, staging and master. xen in xen and hvm

I have tried several of these xen versions both as host and as guest. They all do the same thing for me. Not sure I have tried all possible. So far I have not found a way to use nestedhvm and xen. When I try and start a HVM guest, I get: [root@xen-in-xen ~]# xl -vvv cre -V /home/don/C63-min-too

Re: [Xen-devel] [PATCH] tools/xenconsoled: Increase file descriptor limit

On 02/16/15 13:17, Andrew Cooper wrote: > XenServer's VM density testing uncovered a regression when moving from > sysvinit to systemd where the file descriptor limit dropped from 4096 to > 1024. (XenServer had previously inserted a ulimit statement into its > initscripts.) > > One solution is to

Re: [Xen-devel] Xen 4.6 Development Update

Hi Wei, 2015-02-16 7:38 GMT-05:00 : > > Hi all > > We are now one month into 4.6 development window. This is an email to keep > track of all the patch series I gathered. It is by no means complete and / or > acurate. Feel free to reply this email with new projects or correct my > misunderstanding.

Re: [Xen-devel] [PATCH v3] modify the IO_TLB_SEGSIZE and IO_TLB_DEFAULT_SIZE configurable as flexible requirement about SW-IOMMU.

On Mon, Feb 16, 2015 at 10:38:18AM +0800, Wang Xiaoming wrote: > The maximum of SW-IOMMU is limited to 2^11*128 = 256K. > And the maximum of IO_TLB_DEFAULT_SIZE is limited to (64UL<<20) 64M. > While in different platform and different requirement this seems improper. > So modifing the IO_TLB_SEGSIZ

[Xen-devel] [qemu-mainline test] 34596: regressions - FAIL

flight 34596 qemu-mainline real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/34596/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-debianhvm-amd64 7 debian-hvm-install fail REGR. vs. 33480 test-amd64-i38

[Xen-devel] [PATCH v18 13/16] x86/VPMU: Add privileged PMU mode

Add support for privileged PMU mode (XENPMU_MODE_ALL) which allows privileged domain (dom0) profile both itself (and the hypervisor) and the guests. While this mode is on profiling in guests is disabled. Signed-off-by: Boris Ostrovsky Acked-by: Jan Beulich Reviewed-by: Dietmar Hahn Tested-by: D

[Xen-devel] [PATCH v18 01/16] common/symbols: Export hypervisor symbols to privileged guest

Export Xen's symbols as {} triplet via new XENPF_get_symbol hypercall Signed-off-by: Boris Ostrovsky Acked-by: Daniel De Graaf Reviewed-by: Konrad Rzeszutek Wilk Reviewed-by: Dietmar Hahn Tested-by: Dietmar Hahn --- xen/arch/x86/platform_hypercall.c | 28 +++ xen/common/sym

[Xen-devel] [PATCH v18 15/16] x86/VPMU: VPMU should not exist when vpmu_initialise() is called

We don't need to try to destroy it since it can't be already allocated at the time we try to initialize it. Signed-off-by: Boris Ostrovsky Suggested-by: Andrew Cooper --- xen/arch/x86/hvm/vpmu.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/xen/arch/x86/hvm/vpmu.c b/

[Xen-devel] [PATCH v18 09/16] x86/VPMU: When handling MSR accesses, leave fault injection to callers

With this patch return value of 1 of vpmu_do_msr() will now indicate whether an error was encountered during MSR processing (instead of stating that the access was to a VPMU register). As part of this patch we also check for validity of certain MSR accesses right when we determine which register i

[Xen-devel] [PATCH v18 08/16] x86/VPMU: Save VPMU state for PV guests during context switch

Save VPMU state during context switch for both HVM and PV(H) guests. A subsequent patch ("x86/VPMU: NMI-based VPMU support") will make it possible for vpmu_switch_to() to call vmx_vmcs_try_enter()->vcpu_pause() which needs is_running to be correctly set/cleared. To prepare for that, call context_

[Xen-devel] [PATCH v18 07/16] x86/VPMU: Initialize PMU for PV(H) guests

Code for initializing/tearing down PMU for PV guests Signed-off-by: Boris Ostrovsky Acked-by: Kevin Tian Acked-by: Daniel De Graaf --- tools/flask/policy/policy/modules/xen/xen.te | 4 ++ xen/arch/x86/domain.c| 2 + xen/arch/x86/hvm/hvm.c | 1

[Xen-devel] [PATCH v18 02/16] x86/VPMU: Add public xenpmu.h

Add pmu.h header files, move various macros and structures that will be shared between hypervisor and PV guests to it. Move MSR banks out of architectural PMU structures to allow for larger sizes in the future. The banks are allocated immediately after the context and PMU structures store offsets

[Xen-devel] [PATCH v18 06/16] x86/VPMU: Initialize VPMUs with __initcall

Move some VPMU initilization operations into __initcalls to avoid performing same tests and calculations for each vcpu. Signed-off-by: Boris Ostrovsky --- xen/arch/x86/hvm/svm/vpmu.c | 112 xen/arch/x86/hvm/vmx/vpmu_core2.c | 151 +++

[Xen-devel] [PATCH v18 16/16] x86/VPMU: Move VPMU files up from hvm/ directory

Since PMU is now not HVM specific we can move VPMU-related files up from arch/x86/hvm/ directory. Specifically: arch/x86/hvm/vpmu.c -> arch/x86/cpu/vpmu.c arch/x86/hvm/svm/vpmu.c -> arch/x86/cpu/vpmu_amd.c arch/x86/hvm/vmx/vpmu_core2.c -> arch/x86/cpu/vpmu_intel.c include/asm-x86/h

[Xen-devel] [PATCH v18 05/16] x86/VPMU: Interface for setting PMU mode and flags

Add runtime interface for setting PMU mode and flags. Three main modes are provided: * XENPMU_MODE_OFF: PMU is not virtualized * XENPMU_MODE_SELF: Guests can access PMU MSRs and receive PMU interrupts. * XENPMU_MODE_HV: Same as XENPMU_MODE_SELF for non-proviledged guests, dom0 can profile itself

  1   2   >