Re: [Xen-devel] POSIX error names and codes in PV protocols

>>> On 26.01.17 at 18:28, wrote: > The problem is that it is not exposed to Linux, but I can see it > in FreeBSD [1] and the helper to convert error codes [2] there as well. > Is there any reason these are not available in Linux? Well, the header should eventually get added

Re: [Xen-devel] POSIX error names and codes in PV protocols

On 01/27/2017 10:01 AM, Jan Beulich wrote: On 26.01.17 at 18:28, wrote: The problem is that it is not exposed to Linux, but I can see it in FreeBSD [1] and the helper to convert error codes [2] there as well. Is there any reason these are not available in Linux? Well, the

Re: [Xen-devel] [PATCH v1] displif: add ABI for para-virtual display

BTW, what do you think about adding FB functionality into DISPLIF protocol? Of course it will duplicate FB, but allow future extensions On 01/27/2017 09:56 AM, Jan Beulich wrote: On 26.01.17 at 19:39, wrote: Does the below answer your question? I think that's fine, once

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On 27/01/17 08:53, Oleksandr Andrushchenko wrote: > On 01/27/2017 09:46 AM, Juergen Gross wrote: >> On 27/01/17 08:21, Oleksandr Andrushchenko wrote: >>> On 01/27/2017 09:12 AM, Juergen Gross wrote: Instead of using the default resolution of 800*600 for the pointing device of

Re: [Xen-devel] [PATCH v1] displif: add ABI for para-virtual display

>>> On 27.01.17 at 09:11, wrote: > BTW, what do you think about adding FB functionality into DISPLIF protocol? > > Of course it will duplicate FB, but allow future extensions I have no particular opinion here, other than my general dislike of duplication / redundancy. Jan

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On 01/27/2017 10:14 AM, Juergen Gross wrote: On 27/01/17 08:53, Oleksandr Andrushchenko wrote: On 01/27/2017 09:46 AM, Juergen Gross wrote: On 27/01/17 08:21, Oleksandr Andrushchenko wrote: On 01/27/2017 09:12 AM, Juergen Gross wrote: Instead of using the default resolution of 800*600 for

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On 27/01/17 09:26, Oleksandr Andrushchenko wrote: > On 01/27/2017 10:14 AM, Juergen Gross wrote: >> On 27/01/17 08:53, Oleksandr Andrushchenko wrote: >>> On 01/27/2017 09:46 AM, Juergen Gross wrote: On 27/01/17 08:21, Oleksandr Andrushchenko wrote: > On 01/27/2017 09:12 AM, Juergen Gross

Re: [Xen-devel] Xen on lager for DOMU

Hi George, I didn't test official Renesas yocto layer for Lager board. But general approach to bring-up xen-tools in Dom0 rootfs are follow: 1. clone meta-virtualization layer along with other layers 2. Append xen-base package into default package list (e.g. core-image-minimal or

[Xen-devel] [xen-4.8-testing test] 104736: regressions - FAIL

flight 104736 xen-4.8-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/104736/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-win7-amd64 9 windows-install fail REGR. vs. 104358 Regressions

Re: [Xen-devel] [xen-unstable test] 104728: regressions - FAIL

>>> On 27.01.17 at 05:47, wrote: > flight 104728 xen-unstable real [real] > http://logs.test-lab.xenproject.org/osstest/logs/104728/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: >

Re: [Xen-devel] [Qemu-devel] Commit 3a6c9 breaks QEMU on FreeBSD/Xen

On 26/01/17 22:21, Peter Maydell wrote: > On 26 January 2017 at 20:47, Peter Maydell wrote: >> On 26 January 2017 at 19:36, Stefano Stabellini >> wrote: >>> It should be just a matter of replacing qdev_init_nofail with something >>> that can

Re: [Xen-devel] [xen-4.8-testing test] 104736: regressions - FAIL

>>> On 27.01.17 at 09:59, wrote: > version targeted for testing: > xen b29aed8b0355fe9f7d49faa9aef12b2f8f983c2c > baseline version: > xen e1cefedd80f9972854769bfc6e32e23b56cd0712 > > Last test of basis 104358 2017-01-20

Re: [Xen-devel] [PATCH v2] docs: clarify xl mem-max semantics

On 24/01/17 22:47, Jim Fehlig wrote: > On 01/23/2017 02:49 AM, Juergen Gross wrote: >> The information given in the xl man page for the mem-max command is >> rather brief. Expand it in order to let the reader understand what it >> is really doing. >> >> As the related libxl function

Re: [Xen-devel] [PATCH] x86/xen: Fix APIC id mismatch warning on Intel

On 26/01/17 19:12, Mohit Gambhir wrote: > This patch fixes the following warning message seen when booting the > kernel as Dom0 with Xen on Intel machines. > > [0.003000] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 0 APIC: 1] > > The code generating the warning in

[Xen-devel] [libvirt test] 104742: regressions - FAIL

flight 104742 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/104742/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt 9 debian-install fail REGR. vs. 104685 Regressions which are

Re: [Xen-devel] [Qemu-devel] [PATCH v3 3/3] xen-platform: add missing disk unplug option

On 01/26/2017 04:37 AM, Paul Durrant wrote: > The Xen HVM unplug protocol [1] specifies a mechanism to allow guests to > request unplug of 'aux' disks (which is stated to mean all IDE disks, > except the primary master). This patch adds support for that unplug request. > > NOTE: The semantics

Re: [Xen-devel] Commit 3a6c9 breaks QEMU on FreeBSD/Xen

On 24/01/17 17:42, Roger Pau Monné wrote: > Hello, > > The following commit: > > commit 3a6c9172ac5951e6dac2b3f6cbce3cfccdec5894 > Author: Juergen Gross > Date: Tue Nov 22 07:10:58 2016 +0100 > > xen: create qdev for each backend device > > Prevents me from running QEMU on

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

At 05:41 -0700 on 26 Jan (1485409318), Jan Beulich wrote: > >>> On 19.01.17 at 18:29, wrote: > > +/* Size of the VM86 TSS for virtual 8086 mode to use. */ > > +#define HVM_VM86_TSS_SIZE 128 > > I continue to be puzzled by this value. Why 128? I think this really > needs

Re: [Xen-devel] [xen-unstable test] 104728: regressions - FAIL

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 27 January 2017 09:00 > To: Paul Durrant > Cc: xen-devel ; osstest- > ad...@xenproject.org > Subject: Re: [Xen-devel] [xen-unstable test] 104728:

Re: [Xen-devel] [PATCH v2] docs: clarify xl mem-max semantics

On Fri, Jan 27, 2017 at 10:37:51AM +0100, Juergen Gross wrote: > On 24/01/17 22:47, Jim Fehlig wrote: > > On 01/23/2017 02:49 AM, Juergen Gross wrote: > >> The information given in the xl man page for the mem-max command is > >> rather brief. Expand it in order to let the reader understand what it

Re: [Xen-devel] [PATCH RFC 1/8] golang/xenlight: Create stub package

On 23/01/17 16:43, Ronald Rojas wrote: > Create a basic Makefile to build and install libxenlight Golang > bindings. Also add a stub package which only opens libxl context. > > Include a global xenlight.Ctx variable which can be used as the > default context by the entire program if desired. > >

[Xen-devel] [PATCH v3] docs: clarify xl mem-max semantics

The information given in the xl man page for the mem-max command is rather brief. Expand it in order to let the reader understand what it is really doing. As the related libxl function libxl_domain_setmaxmem() isn't much clearer add a comment to it explaining the desired semantics.

[Xen-devel] [PATCH v3] xenstore: remove XS_RESTRICT support

XS_RESTRICT and the xenstore library function xs_restrict() have never been usable in all configurations and there are no known users. This functionality was thought to limit access rights of device models to xenstore in order to avoid affecting other domains in case of a security breech.

Re: [Xen-devel] [PATCH v3] docs: clarify xl mem-max semantics

On Fri, Jan 27, 2017 at 12:45:18PM +0100, Juergen Gross wrote: > The information given in the xl man page for the mem-max command is > rather brief. Expand it in order to let the reader understand what it > is really doing. > > As the related libxl function libxl_domain_setmaxmem() isn't much >

Re: [Xen-devel] Xen ARM - Exposing a PL011 to the guest

Hi, I have done the changes for emulating pl011 in Xen. Currently, I have verified the emulation code by manually reading/writing data to /dev/ttyAMA0 which is the device file for pl011 device. The data is flowing fine between xenconsoled and the guest domain. As a next step, I wanted to use

Re: [Xen-devel] [PATCH RFC 2/8] golang/xenlight: Add error constants and standard handling

On 23/01/17 16:43, Ronald Rojas wrote: > Create error type Errorxl for throwing proper xenlight > errors. > > Update Ctx functions to throw Errorxl errors. > > Signed-off-by: Ronald Rojas Everything here looks, good with a few nitpicks... > --- >

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

On Thu, Jan 26, 2017 at 05:41:58AM -0700, Jan Beulich wrote: > >>> On 19.01.17 at 18:29, wrote: > > @@ -43,6 +44,9 @@ static long __initdata dom0_nrpages; > > static long __initdata dom0_min_nrpages; > > static long __initdata dom0_max_nrpages = LONG_MAX; > > > > +/*

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

On Fri, Jan 27, 2017 at 11:14:10AM +, Tim Deegan wrote: > At 05:41 -0700 on 26 Jan (1485409318), Jan Beulich wrote: > > >>> On 19.01.17 at 18:29, wrote: > > > +/* Size of the VM86 TSS for virtual 8086 mode to use. */ > > > +#define HVM_VM86_TSS_SIZE 128 > > > > I

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

On 27/01/17 11:14, Tim Deegan wrote: > At 05:41 -0700 on 26 Jan (1485409318), Jan Beulich wrote: > On 19.01.17 at 18:29, wrote: >>> +/* Size of the VM86 TSS for virtual 8086 mode to use. */ >>> +#define HVM_VM86_TSS_SIZE 128 >> I continue to be puzzled by this value.

[Xen-devel] [PATCH v16] sndif: add ABI for para-virtual sound

From: Oleksandr Andrushchenko Hi, all! Please find the next version of the ABI for the PV sound after addressing review comments. Thank you, Oleksandr Andrushchenko Oleksandr Grytsov Oleksandr Andrushchenko (1): xen/sndif: Add sound-device ABI

[Xen-devel] [PATCH v16] xen/sndif: Add sound-device ABI

From: Oleksandr Andrushchenko This is the ABI for the two halves of a para-virtualized sound driver to communicate with each other. The ABI allows implementing audio playback and capture as well as volume control and possibility to mute/unmute audio sources.

[Xen-devel] [PATCH v2] displif: add ABI for para-virtual display

From: Oleksandr Andrushchenko This is the ABI for the two halves of a para-virtualized display driver. This protocol aims to provide a unified protocol which fits more sophisticated use-cases than a framebuffer device can handle. At the moment basic

[Xen-devel] [PATCH v2] displif: add ABI for para-virtual display

From: Oleksandr Andrushchenko This is the ABI for the two halves of a para-virtualized display driver. This protocol aims to provide a unified protocol which fits more sophisticated use-cases than a framebuffer device can handle. At the moment basic

Re: [Xen-devel] [PATCH v2] displif: add ABI for para-virtual display

PFA pahole output On 01/27/2017 03:08 PM, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko This is the ABI for the two halves of a para-virtualized display driver. This protocol aims to provide a unified protocol which fits more

Re: [Xen-devel] [PATCH v16] sndif: add ABI for para-virtual sound

PFA pahole output On 01/27/2017 03:03 PM, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Hi, all! Please find the next version of the ABI for the PV sound after addressing review comments. Thank you, Oleksandr Andrushchenko Oleksandr Grytsov

[Xen-devel] [linux-linus test] 104741: regressions - trouble: blocked/broken/fail/pass

flight 104741 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/104741/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-winxpsp3 3 host-install(3)broken REGR. vs. 59254

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

Hi, At 12:51 + on 27 Jan (1485521470), Andrew Cooper wrote: > On 27/01/17 11:14, Tim Deegan wrote: > > But looking at it now, I'm not convinced of exactly how. The magic > > bitmap in the TSS is at [I/O Map Base Address] - 32, and the I/O map > > base address itself lives at offset 100. A

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

On 27/01/17 13:20, Tim Deegan wrote: > Hi, > > At 12:51 + on 27 Jan (1485521470), Andrew Cooper wrote: >> On 27/01/17 11:14, Tim Deegan wrote: >>> But looking at it now, I'm not convinced of exactly how. The magic >>> bitmap in the TSS is at [I/O Map Base Address] - 32, and the I/O map >>>

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

Hi, At 13:46 + on 27 Jan (1485524765), Andrew Cooper wrote: > The actual behaviour can be determined by putting the TSS on a page > boundary, making the previous frame non-readable via EPT, and seeing > whether an EPT violation occurs. Indeed. Or likewise with normal pagetables. > > Yes,

[Xen-devel] [PATCH] xsm: Permit dom0 to use dmops

c/s 524a98c2ac5 "public / x86: introduce __HYPERCALL_dm_op" gave flask permisisons for a stubdomain to use dmops, but omitted the case of a device model running in dom0. Signed-off-by: Andrew Cooper --- CC: Paul Durrant CC: Ian Jackson

[Xen-devel] [xen-unstable-smoke test] 104764: tolerable trouble: broken/fail/pass - PUSHED

flight 104764 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/104764/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 12

Re: [Xen-devel] [PATCH] xsm: Permit dom0 to use dmops

On Fri, Jan 27, 2017 at 02:16:58PM +, Andrew Cooper wrote: > c/s 524a98c2ac5 "public / x86: introduce __HYPERCALL_dm_op" gave flask > permisisons for a stubdomain to use dmops, but omitted the case of a device > model running in dom0. > > Signed-off-by: Andrew Cooper

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

On 27/01/17 14:01, Tim Deegan wrote: > Hi, > > At 13:46 + on 27 Jan (1485524765), Andrew Cooper wrote: >> The actual behaviour can be determined by putting the TSS on a page >> boundary, making the previous frame non-readable via EPT, and seeing >> whether an EPT violation occurs. > Indeed.

Re: [Xen-devel] [PATCH v3] xenstore: remove XS_RESTRICT support

On Fri, Jan 27, 2017 at 12:47:22PM +0100, Juergen Gross wrote: > XS_RESTRICT and the xenstore library function xs_restrict() have never > been usable in all configurations and there are no known users. > > This functionality was thought to limit access rights of device models > to xenstore in

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Thu, Jan 26, 2017 at 03:16:22PM -0700, Tamas K Lengyel wrote: > When the toolstack modifies memory of a running ARM VM it may happen > that the underlying memory of a current vCPU PC is changed. Without > flushing the icache the vCPU may continue executing stale instructions. > Why is this

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

On Thu, Jan 26, 2017 at 12:09:30PM +0100, Dario Faggioli wrote: > On Thu, 2017-01-26 at 12:02 +0200, Oleksandr Andrushchenko wrote: > > Hi, Konrad! > > > > First of all thank you very much for the valuable comments > > > > and your time! > > > > The number of changes (mostly in description) is

Re: [Xen-devel] [PATCH v1 3/3] MAINTAINERS: xen, kvm: track pvclock-abi.h changes

On 25/01/17 18:33, Joao Martins wrote: > This file defines an ABI shared between guest and hypervisor(s) > (KVM, Xen) and as such there should be an correspondent entry in > MAINTAINERS file. Notice that there's already a text notice at the > top of the header file, hence this commit simply

Re: [Xen-devel] [PATCH v5 5/9] x86/hvm: add vcpu parameter to guest memory copy function

On Thu, Jan 26, 2017 at 06:33:11AM -0700, Jan Beulich wrote: > >>> On 19.01.17 at 18:29, wrote: > > --- a/xen/include/asm-x86/hvm/support.h > > +++ b/xen/include/asm-x86/hvm/support.h > > @@ -71,6 +71,8 @@ enum hvm_copy_result hvm_copy_to_guest_phys( > > paddr_t paddr,

Re: [Xen-devel] [PATCH] xsm: Permit dom0 to use dmops

> -Original Message- > From: Wei Liu [mailto:wei.l...@citrix.com] > Sent: 27 January 2017 14:33 > To: Andrew Cooper > Cc: Xen-devel ; Paul Durrant > ; Ian Jackson ; Wei Liu >

Re: [Xen-devel] [PATCH] libs/gnttab: add FreeBSD handlers for the grant-table user-space device

On Thu, Jan 26, 2017 at 03:35:46PM +, Roger Pau Monne wrote: > This patch adds the headers and helpers for the FreeBSD gntdev, used in order > to map grants from remote domains and to allocate grants on behalf of the > current domain. > > Current code has been tested with the QEMU/Qdisk

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

>>> On 27.01.17 at 13:23, wrote: > On Thu, Jan 26, 2017 at 05:41:58AM -0700, Jan Beulich wrote: >> >>> On 19.01.17 at 18:29, wrote: >> > @@ -43,6 +44,9 @@ static long __initdata dom0_nrpages; >> > static long __initdata dom0_min_nrpages; >> > static

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

On Thu, Jan 26, 2017 at 12:02:49PM +0200, Oleksandr Andrushchenko wrote: > Hi, Konrad! > > First of all thank you very much for the valuable comments > > and your time! > > The number of changes (mostly in description) is going to > > be huge, so do you think I can publish something like > >

Re: [Xen-devel] [PATCH RESEND v5 24/24] docs: add L2 CAT description in docs.

On Thu, Jan 19, 2017 at 02:01:26PM +0800, Yi Sun wrote: > This patch adds L2 CAT description in related documents. > > Signed-off-by: He Chen > Signed-off-by: Yi Sun Acked-by: Wei Liu

Re: [Xen-devel] [PATCH RESEND v5 23/24] tools: L2 CAT: support set cbm for L2 CAT.

On Thu, Jan 19, 2017 at 02:01:25PM +0800, Yi Sun wrote: > This patch implements the xl/xc changes to support set CBM > for L2 CAT. > > The new level option is introduced to original CAT setting > command in order to set CBM for specified level CAT. > - 'xl psr-cat-cbm-set' is updated to set cache

Re: [Xen-devel] [PATCH RESEND v5 22/24] tools: L2 CAT: support show cbm for L2 CAT.

On Thu, Jan 19, 2017 at 02:01:24PM +0800, Yi Sun wrote: > This patch implements changes in xl/xc changes to support > showing CBM of L2 CAT. > > The new level option is introduced to original CAT showing > command in order to show CBM for specified level CAT. > - 'xl psr-cat-show' is updated to

Re: [Xen-devel] [PATCH RESEND v5 21/24] tools: L2 CAT: support get HW info for L2 CAT.

On Thu, Jan 19, 2017 at 02:01:23PM +0800, Yi Sun wrote: > This patch implements xl/xc changes to support get HW info > for L2 CAT. > > 'xl psr-hwinfo' is updated to show both L3 CAT and L2 CAT > info. > > Example(on machine which only supports L2 CAT): > Cache Monitoring Technology (CMT): >

[Xen-devel] [xen-unstable test] 104743: regressions - FAIL

flight 104743 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104743/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail REGR. vs. 104681

Re: [Xen-devel] [PATCH v2 8/9] xen/pvh: Enable CPU hotplug

On 26/01/17 20:41, Boris Ostrovsky wrote: > PVH guests don't (yet) receive ACPI hotplug interrupts and therefore > need to monitor xenstore for CPU hotplug event. > > Signed-off-by: Boris Ostrovsky Reviewed-by: Juergen Gross Juergen

Re: [Xen-devel] [PATCH v3] x86/ept: Allow write-combining on !mfn_valid() MMIO mappings again

. snip .. > > Signed-off-by: David Woodhouse > > Reviewed-by: Jan Beulich > > But before committing I'd prefer to have a VMX maintainer ack > too. Who is gone until Feb yth (Spring festival in China). ___

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Fri, Jan 27, 2017 at 7:49 AM, Wei Liu wrote: > On Thu, Jan 26, 2017 at 03:16:22PM -0700, Tamas K Lengyel wrote: >> When the toolstack modifies memory of a running ARM VM it may happen >> that the underlying memory of a current vCPU PC is changed. Without >> flushing the

Re: [Xen-devel] [PATCH v2 9/9] xen/pvh: Use Xen's emergency_restart op for PVH guests

On 26/01/17 20:41, Boris Ostrovsky wrote: > Using native_machine_emergency_restart (called during reboot) will > lead PVH guests to machine_real_restart() where we try to use > real_mode_header which is not initialized. > > Signed-off-by: Boris Ostrovsky

Re: [Xen-devel] [PATCH v2 6/9] xen/pvh: Initialize grant table for PVH guests

On 26/01/17 20:41, Boris Ostrovsky wrote: > Like PV guests, PVH does not have PCI devices and therefore cannot > use MMIO space to store grants. Instead it balloons out memory and > keeps grants there. > > Signed-off-by: Boris Ostrovsky Reviewed-by: Juergen Gross

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Fri, Jan 27, 2017 at 08:37:33AM -0700, Tamas K Lengyel wrote: > On Fri, Jan 27, 2017 at 7:49 AM, Wei Liu wrote: > > On Thu, Jan 26, 2017 at 03:16:22PM -0700, Tamas K Lengyel wrote: > >> When the toolstack modifies memory of a running ARM VM it may happen > >> that the

[Xen-devel] altp2m: unexpected behavior

Hello, In developing against the altp2m API, I've encountered something I wasn't expecting. Here's the scenario: 1. Create a new altp2m memory view. Assume we get view ID 1. 2. Change some MFN permissions in view 1. 3. Destroy view 1. 4. Create another altp2m view. Get view ID 1 again. Now, I

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

thank you for comments, please find answers below Can we please switch to v16 discussion as v15 vs v16 is a big change? On 01/27/2017 05:14 PM, Konrad Rzeszutek Wilk wrote: On Thu, Jan 26, 2017 at 12:02:49PM +0200, Oleksandr Andrushchenko wrote: Hi, Konrad! First of all thank you very much

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Jan 27, 2017 08:43, "Wei Liu" wrote: On Fri, Jan 27, 2017 at 08:37:33AM -0700, Tamas K Lengyel wrote: > On Fri, Jan 27, 2017 at 7:49 AM, Wei Liu wrote: > > On Thu, Jan 26, 2017 at 03:16:22PM -0700, Tamas K Lengyel wrote: > >> When the toolstack

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

On Fri, Jan 27, 2017 at 08:11:56AM -0700, Jan Beulich wrote: > >>> On 27.01.17 at 13:23, wrote: > > On Thu, Jan 26, 2017 at 05:41:58AM -0700, Jan Beulich wrote: > >> >>> On 19.01.17 at 18:29, wrote: > >> > @@ -43,6 +44,9 @@ static long __initdata

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Fri, Jan 27, 2017 at 08:52:50AM -0700, Tamas K Lengyel wrote: > On Jan 27, 2017 08:43, "Wei Liu" wrote: > > On Fri, Jan 27, 2017 at 08:37:33AM -0700, Tamas K Lengyel wrote: > > On Fri, Jan 27, 2017 at 7:49 AM, Wei Liu wrote: > > > On Thu, Jan 26,

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On January 27, 2017 12:31:19 AM PST, Juergen Gross wrote: >On 27/01/17 09:26, Oleksandr Andrushchenko wrote: >> On 01/27/2017 10:14 AM, Juergen Gross wrote: >>> On 27/01/17 08:53, Oleksandr Andrushchenko wrote: On 01/27/2017 09:46 AM, Juergen Gross wrote: > On 27/01/17

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

Hello, On 27/01/17 15:52, Tamas K Lengyel wrote: Well, yes, only ARM could _should_ call this function. The comment I think is important to tell the user don't expect it to do anything on x86. Doesn't mean they can't call it though - if that was the case it would be wrapped in an ifdef like

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Fri, Jan 27, 2017 at 9:15 AM, Julien Grall wrote: > Hello, > > On 27/01/17 15:52, Tamas K Lengyel wrote: >> >> Well, yes, only ARM could _should_ call this function. The comment I >> think is important to tell the user don't expect it to do anything on >> x86. Doesn't

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

Hi Tamas, On 27/01/17 16:23, Tamas K Lengyel wrote: On Fri, Jan 27, 2017 at 9:15 AM, Julien Grall wrote: Hello, On 27/01/17 15:52, Tamas K Lengyel wrote: Well, yes, only ARM could _should_ call this function. The comment I think is important to tell the user don't

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

>>> On 27.01.17 at 17:04, wrote: > On Fri, Jan 27, 2017 at 08:11:56AM -0700, Jan Beulich wrote: >> >>> On 27.01.17 at 13:23, wrote: >> > On Thu, Jan 26, 2017 at 05:41:58AM -0700, Jan Beulich wrote: >> >> >>> On 19.01.17 at 18:29,

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Fri, Jan 27, 2017 at 9:29 AM, Julien Grall wrote: > Hi Tamas, > > On 27/01/17 16:23, Tamas K Lengyel wrote: >> >> On Fri, Jan 27, 2017 at 9:15 AM, Julien Grall >> wrote: >>> >>> Hello, >>> >>> On 27/01/17 15:52, Tamas K Lengyel wrote:

Re: [Xen-devel] [PATCH] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Fri, Jan 27, 2017 at 09:32:25AM -0700, Tamas K Lengyel wrote: > On Fri, Jan 27, 2017 at 9:29 AM, Julien Grall wrote: > > Hi Tamas, > > > > On 27/01/17 16:23, Tamas K Lengyel wrote: > >> > >> On Fri, Jan 27, 2017 at 9:15 AM, Julien Grall > >> wrote:

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

On Fri, Jan 27, 2017 at 05:50:36PM +0200, Oleksandr Andrushchenko wrote: > thank you for comments, please find answers below > > Can we please switch to v16 discussion as v15 vs v16 is > a big change? This channel seemed appropiate to hash this out. I will look at v16 next week (out of time

Re: [Xen-devel] [PATCH v5 4/9] xen/x86: populate PVHv2 Dom0 physical memory map

>>> On 27.01.17 at 14:20, wrote: > At 12:51 + on 27 Jan (1485521470), Andrew Cooper wrote: >> On 27/01/17 11:14, Tim Deegan wrote: >> > But looking at it now, I'm not convinced of exactly how. The magic >> > bitmap in the TSS is at [I/O Map Base Address] - 32, and the I/O map

[Xen-devel] [PATCH v2] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

When the toolstack modifies memory of a running ARM VM it may happen that the underlying memory of a current vCPU PC is changed. Without flushing the icache the vCPU may continue executing stale instructions. In this patch we introduce VA-based icache flushing macros. Also expose the

Re: [Xen-devel] [PATCH RFC 2/6] COLO-Proxy: Setup userspace colo-proxy on primary side

On Thu, Jan 26, 2017 at 02:36:05PM +0800, Zhang Chen wrote: > In this patch we close kernel COLO-Proxy on primary side. > > Signed-off-by: Zhang Chen Acked-by: Wei Liu I don't claim I know much about COLO though, nor have I ever run it, so

Re: [Xen-devel] [PATCH RFC 6/6] COLO-Proxy: Use socket to get checkpoint event.

On Thu, Jan 26, 2017 at 02:36:09PM +0800, Zhang Chen wrote: > We use old kernel colo proxy way to get the checkpoint event from qemu. > This patch have some TODO job. > Qemu compare need add a API to support this(I will add this in qemu). > > Signed-off-by: Zhang Chen

Re: [Xen-devel] [PATCH RFC 1/6] COLO-Proxy: Add remus command to open userspace proxy

On Thu, Jan 26, 2017 at 02:36:04PM +0800, Zhang Chen wrote: > Add remus '-p' to enable userspace colo proxy(in qemu). > > Signed-off-by: Zhang Chen > --- > docs/man/xl.pod.1.in | 4 > tools/libxl/libxl_colo.h | 5 + >

Re: [Xen-devel] [PATCH RFC 0/6] COLO-Proxy: Make Xen COLO use userspace colo-proxy

On Thu, Jan 26, 2017 at 02:36:03PM +0800, Zhang Chen wrote: > Hi~ All~ Happy Chinese New Year~~ Happy Chinese New Year to you, too! I skimmed through this series and made some comments based on my preliminary assessment. If you have any questions, feel free to ask. I suppose we would need to

Re: [Xen-devel] [PATCH v2] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

On Fri, Jan 27, 2017 at 09:45:45AM -0700, Tamas K Lengyel wrote: > When the toolstack modifies memory of a running ARM VM it may happen > that the underlying memory of a current vCPU PC is changed. Without > flushing the icache the vCPU may continue executing stale instructions. > > In this patch

Re: [Xen-devel] [PATCH RFC 5/6] COLO-Proxy: Add secondary userspace colo-proxy start args

On Thu, Jan 26, 2017 at 02:36:08PM +0800, Zhang Chen wrote: > Qemu need this args to start userspace colo-proxy. > > Signed-off-by: Zhang Chen See previous patch. Same comments apply here. Wei. ___ Xen-devel mailing

Re: [Xen-devel] [PATCH RFC 4/6] COLO-Proxy: Add primary userspace colo proxy start args

On Thu, Jan 26, 2017 at 02:36:07PM +0800, Zhang Chen wrote: > Qemu need this args to start userspace colo-proxy. > > Signed-off-by: Zhang Chen Since we have: # Note that the COLO configuration settings should be considered unstable. # They may change

Re: [Xen-devel] [PATCH] xen: sched: improve debug dump output.

On Thu, Jan 26, 2017 at 5:08 PM, Dario Faggioli wrote: > On Thu, 2017-01-26 at 13:59 -0500, Meng Xu wrote: >> Hi Dario, >> > Hi, > >> On Thu, Jan 26, 2017 at 11:52 AM, Dario Faggioli >> wrote: >> > >> > Runqueue 0: >> > CPU[00] runq=0,

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

On 01/27/2017 06:36 PM, Konrad Rzeszutek Wilk wrote: On Fri, Jan 27, 2017 at 05:50:36PM +0200, Oleksandr Andrushchenko wrote: thank you for comments, please find answers below Can we please switch to v16 discussion as v15 vs v16 is a big change? This channel seemed appropiate to hash this

Re: [Xen-devel] [PATCH v5 6/9] xen/x86: parse Dom0 kernel for PVHv2

On Thu, Jan 26, 2017 at 06:37:00AM -0700, Jan Beulich wrote: > >>> On 19.01.17 at 18:29, wrote: > > @@ -1959,12 +1960,146 @@ static int __init pvh_setup_p2m(struct domain *d) > > #undef MB1_PAGES > > } > > > > +static int __init pvh_load_kernel(struct domain *d, const

Re: [Xen-devel] [PATCH v2] xen/arm: flush icache as well when XEN_DOMCTL_cacheflush is issued

Hello Tamas, Please give a bit more time to people for reviewing before sending a new version. Patches adding cache instruction are never easy to review. On 27/01/17 16:45, Tamas K Lengyel wrote: When the toolstack modifies memory of a running ARM VM it may happen that the underlying memory

Re: [Xen-devel] [PATCH v5 6/9] xen/x86: parse Dom0 kernel for PVHv2

On Fri, Jan 27, 2017 at 05:22:03PM +, Roger Pau Monne wrote: > On Thu, Jan 26, 2017 at 06:37:00AM -0700, Jan Beulich wrote: > > >>> On 19.01.17 at 18:29, wrote: > > > +if ( cmdline != NULL ) > > > +{ > > > +rc = hvm_copy_to_guest_phys_vcpu(last_addr,

Re: [Xen-devel] [PATCH RFC 3/6] COLO-Proxy: Setup userspace colo-proxy on secondary side

On Thu, Jan 26, 2017 at 02:36:06PM +0800, Zhang Chen wrote: > In this patch we add a function to close > kernel COLO-Proxy on secondary side. > > Signed-off-by: Zhang Chen > --- > tools/libxl/libxl_colo_restore.c | 9 +++-- > tools/libxl/libxl_create.c

Re: [Xen-devel] [GIT PULL] (xen-blkfront) stable/for-jens-4.10 for your 'linux-next' branch.

On 01/27/2017 11:47 AM, Konrad Rzeszutek Wilk wrote: > Hey Jens, > > Please pull in your 'for-linus' branch two little fixes for Xen > block front: > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git > stable/for-jens-4.10 > > One fix is for handling the XEN_PAGE_SIZE != PAGE_SIZE

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

On Fri, Jan 27, 2017 at 08:38:29PM +0200, Oleksandr Andrushchenko wrote: > > > On 01/27/2017 08:13 PM, Konrad Rzeszutek Wilk wrote: > > .snip.. > > > I am looking at this from FAE's or integrator's POV, when one would need > > FAE? > > > Field Applications Engineer > > > to touch different

Re: [Xen-devel] altp2m: unexpected behavior

On Fri, Jan 27, 2017 at 11:30 AM, Andrew Cooper wrote: > On 27/01/17 18:22, Tamas K Lengyel wrote: >> On Fri, Jan 27, 2017 at 8:44 AM, Matt Leinhos wrote: >>> Hello, >>> >>> In developing against the altp2m API, I've encountered something I >>> wasn't

Re: [Xen-devel] Xen ARM - Exposing a PL011 to the guest

On Fri, 27 Jan 2017, Bhupinder Thakur wrote: > Hi, > > I have done the changes for emulating pl011 in Xen. Currently, I have > verified the emulation code by manually reading/writing data to > /dev/ttyAMA0 which is the device file for pl011 device. The data is > flowing fine between xenconsoled

Re: [Xen-devel] [PATCH] xen: sched: improve debug dump output.

> > > > TBH, what I don't especially like in the output above is, within > > > the > > > vCPU info being printed: > > > - the spaces inside '[' ']'; > > > - the big numbers; > > > - the fact that last_start is rather useless (it's more tracing > > > info > > >than debug dump info, IMO); > >

Re: [Xen-devel] [PATCH] arm/monitor: flush the icache during SMC traps

On Thu, 26 Jan 2017, Tamas K Lengyel wrote: > On Thu, Jan 26, 2017 at 10:54 AM, Tamas K Lengyel > wrote: > > On Thu, Jan 26, 2017 at 4:30 AM, Julien Grall wrote: > >> (CC xen-devel, Ravzan, and Stefao) > >> > >> Hi Tamas, > >> > >> Not sure why

Re: [Xen-devel] [PATCH] xen: sched: improve debug dump output.

On Thu, Jan 26, 2017 at 11:52 AM, Dario Faggioli wrote: > Scheduling information debug dump for Credit2 is hard > to read as it contains the same information repeated > multiple time in different ways. > > In fact, in Credit2, CPUs are grouped in runqueus. > Here's the

Re: [Xen-devel] [PATCH] xen: sched: improve debug dump output.

On Fri, 2017-01-27 at 12:05 -0500, Meng Xu wrote: > On Thu, Jan 26, 2017 at 5:08 PM, Dario Faggioli > wrote: > > "Runqueue 0" tells that what follow is information about the pCPUs > > and > > the vCPUs of that runqueue (it's the same label used above for, > > showing >

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

On 01/27/2017 08:13 PM, Konrad Rzeszutek Wilk wrote: .snip.. I am looking at this from FAE's or integrator's POV, when one would need FAE? Field Applications Engineer to touch different parts of the system. "/0/0/0" makes me feel sad just because either you have to keep all those numbers

  1   2   >