[Xen-devel] [xen-unstable test] 112416: regressions - trouble: blocked/broken/fail/pass

flight 112416 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/112416/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs. 112286

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

flight 112412 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/112412/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 7 xen-boot fail REGR. vs. 110515

Re: [Xen-devel] [PATCH v2] xen: get rid of paravirt op adjust_exception_frame

On Tue, Aug 1, 2017 at 4:38 PM, Andrew Cooper wrote: > On 01/08/2017 20:45, Andy Lutomirski wrote: >> Also, IMO it would be nice to fully finish the job. Remaining steps are: >> >> 1. Unsuck the SYSCALL entries on Xen PV. >> 2. Unsuck the SYENTER entry on Xen PV. >> 3.

Re: [Xen-devel] [PATCH v2] xen: get rid of paravirt op adjust_exception_frame

On 01/08/2017 20:45, Andy Lutomirski wrote: > Also, IMO it would be nice to fully finish the job. Remaining steps are: > > 1. Unsuck the SYSCALL entries on Xen PV. > 2. Unsuck the SYENTER entry on Xen PV. > 3. Make a xen_nmi that's actually correct (should be trivial) > > #1 is here: > >

Re: [Xen-devel] [PATCH 1/2] arm: smccc: handle SMCs/HVCs according to SMCCC

Hi Edgar, On 01/08/2017 22:22, Edgar E. Iglesias wrote: On Tue, Aug 01, 2017 at 10:02:45PM +0100, Julien Grall wrote: Hi, On 01/08/2017 21:40, Stefano Stabellini wrote: On Tue, 1 Aug 2017, Edgar E. Iglesias wrote: On Tue, Aug 01, 2017 at 11:59:00AM +0100, Julien Grall wrote: (+ Edgar,

[Xen-devel] [qemu-mainline test] 112407: regressions - trouble: blocked/broken/fail/pass

flight 112407 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/112407/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-win7-amd64 10 windows-install fail REGR. vs. 111765

[Xen-devel] [ovmf baseline-only test] 71929: all pass

This run is configured for baseline tests only. flight 71929 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/71929/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf c1acb0f9b8222a97d2ad72dbebbcefc214d9ce03 baseline

Re: [Xen-devel] [PATCH 1/2] arm: smccc: handle SMCs/HVCs according to SMCCC

On Tue, Aug 01, 2017 at 10:02:45PM +0100, Julien Grall wrote: > Hi, > > On 01/08/2017 21:40, Stefano Stabellini wrote: > >On Tue, 1 Aug 2017, Edgar E. Iglesias wrote: > >>On Tue, Aug 01, 2017 at 11:59:00AM +0100, Julien Grall wrote: > >>>(+ Edgar, Mark, Dave) > >>> > >>>Hi, > >> > >>Hi Julien, >

Re: [Xen-devel] [PATCH 1/2] arm: smccc: handle SMCs/HVCs according to SMCCC

Hi, On 01/08/2017 21:40, Stefano Stabellini wrote: On Tue, 1 Aug 2017, Edgar E. Iglesias wrote: On Tue, Aug 01, 2017 at 11:59:00AM +0100, Julien Grall wrote: (+ Edgar, Mark, Dave) Hi, Hi Julien, I'll share some thoughts based on our platforms. On 14/06/17 15:10, Volodymyr Babchuk

Re: [Xen-devel] [PATCH 1/2] arm: smccc: handle SMCs/HVCs according to SMCCC

On Tue, 1 Aug 2017, Edgar E. Iglesias wrote: > On Tue, Aug 01, 2017 at 11:59:00AM +0100, Julien Grall wrote: > > (+ Edgar, Mark, Dave) > > > > Hi, > > Hi Julien, > > I'll share some thoughts based on our platforms. > > > > On 14/06/17 15:10, Volodymyr Babchuk wrote: > > >SMCCC (SMC Call

Re: [Xen-devel] [PATCH v1 0/1] xen/arm: zynqmp: Disable PCIe

On Tue, 1 Aug 2017, Edgar E. Iglesias wrote: > On Mon, Jul 31, 2017 at 11:11:39PM +0100, Julien Grall wrote: > > > > > > On 31/07/2017 20:37, Edgar E. Iglesias wrote: > > >From: "Edgar E. Iglesias" > > > > > >Hi, > > > > Hi Edgar, > > > > > > >We're seeing panics

Re: [Xen-devel] [PATCH v2] xen: get rid of paravirt op adjust_exception_frame

On Tue, Aug 1, 2017 at 3:39 AM, Juergen Gross wrote: > When running as Xen pv-guest the exception frame on the stack contains > %r11 and %rcx additional to the other data pushed by the processor. > > Instead of having a paravirt op being called for each exception type > prepend

[Xen-devel] [PATCH v4] xen: rtds: only tickle non-already tickled CPUs

When more than one idle VCPUs that have the same PCPU as their previous running core invoke runq_tickle(), they will tickle the same PCPU. The tickled PCPU will only pick at most one VCPU, i.e., the highest-priority one, to execute. The other VCPUs will not be scheduled for a period, even when

Re: [Xen-devel] [PATCH v6] x86/monitor: Notify monitor if an emulation fails.

On 07/25/2017 08:40 PM, Razvan Cojocaru wrote: > On 07/18/2017 01:20 PM, Razvan Cojocaru wrote: >> On 07/18/2017 01:09 PM, Andrew Cooper wrote: >>> On 18/07/17 10:37, Petre Pircalabu wrote: If case of a vm_event with the emulate_flags set, if the instruction cannot be emulated, the

[Xen-devel] [ovmf test] 112415: all pass - PUSHED

flight 112415 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/112415/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf c1acb0f9b8222a97d2ad72dbebbcefc214d9ce03 baseline version: ovmf

Re: [Xen-devel] [PATCH 5/5] xen: RCU: avoid busy waiting until the end of grace period.

On Tue, 1 Aug 2017, Dario Faggioli wrote: > On Mon, 2017-07-31 at 16:58 -0700, Stefano Stabellini wrote: > > On Tue, 1 Aug 2017, Dario Faggioli wrote: > > > On Mon, 2017-07-31 at 14:20 -0700, Stefano Stabellini wrote: > > > > On Thu, 27 Jul 2017, Dario Faggioli wrote: > > > > > > > > > > diff

Re: [Xen-devel] [PATCH RFC v1 0/3] Enable XL to set and get per-VCPU work conserving flag for RTDS scheduler

On Tue, Aug 1, 2017 at 2:33 PM, Meng Xu wrote: > > This series of patches enable the toolstack to > set and get per-VCPU work-conserving flag. > With the toolstack, system administrators can decide > which VCPUs will be made work-conserving. > > The design of the

Re: [Xen-devel] PV drivers and zero copying

On Tue, 1 Aug 2017, Oleksandr Andrushchenko wrote: > Hi, Stefano! > > On 07/31/2017 11:28 PM, Stefano Stabellini wrote: > > On Mon, 31 Jul 2017, Oleksandr Andrushchenko wrote: > > > 3 Sharing with page exchange (XENMEM_exchange) > > > == > > > > > >

Re: [Xen-devel] stage1-xen for Fedora

CC'ing xen-devel in case somebody else in the community has a better answer for you On Tue, 1 Aug 2017, Rajiv Ranganath wrote: > Hi Stefano, > > I was wondering if you had instructions on building stage1-xen on Fedora? > > If so can you please share. > > Thank you! Hello Rajiv, It's great to

[Xen-devel] [PATCH RFC v1 0/3] Enable XL to set and get per-VCPU work conserving flag for RTDS scheduler

This series of patches enable the toolstack to set and get per-VCPU work-conserving flag. With the toolstack, system administrators can decide which VCPUs will be made work-conserving. The design of the work-conserving RTDS was discussed in

[Xen-devel] [PATCH RFC v1 3/3] xl: enable per-VCPU work conserving flag for RTDS

Change main_sched_rtds and related output functions to support per-VCPU work conserving flag. Signed-off-by: Meng Xu --- tools/xl/xl_cmdtable.c | 3 ++- tools/xl/xl_sched.c| 56 ++ 2 files changed, 40 insertions(+), 19

[Xen-devel] [PATCH RFC v1 1/3] xen:rtds: enable XL to set and get vcpu work conserving flag

Extend the hypercalls(XEN_DOMCTL_SCHEDOP_getvcpuinfo/putvcpuinfo) to get/set a domain's per-VCPU work conserving parameters. Signed-off-by: Meng Xu --- xen/common/sched_rt.c | 2 ++ xen/include/public/domctl.h | 1 + 2 files changed, 3 insertions(+) diff --git

Re: [Xen-devel] DESIGN v2: CPUID part 3

On 31/07/2017 20:49, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 05, 2017 at 02:22:00PM +0100, Joao Martins wrote: >> On 07/05/2017 12:16 PM, Andrew Cooper wrote: >>> On 05/07/17 10:46, Joao Martins wrote: Hey Andrew, On 07/04/2017 03:55 PM, Andrew Cooper wrote: > (RFC:

[Xen-devel] [PATCH RFC v1 2/3] libxl: enable per-VCPU work conserving flag for RTDS

Modify libxl_vcpu_sched_params_get/set and sched_rtds_vcpu_get/set functions to support per-VCPU work conserving flag Signed-off-by: Meng Xu --- tools/libxl/libxl.h | 1 + tools/libxl/libxl_sched.c | 3 +++ tools/libxl/libxl_types.idl | 2 ++ 3 files changed, 6

Re: [Xen-devel] [PATCH v2 00/13] "Non-shared" IOMMU support on ARM

СС persons from all patches in current series into the cover letter. On Tue, Aug 1, 2017 at 9:09 PM, Julien Grall wrote: > > > On 01/08/17 04:06, Tian, Kevin wrote: >>> >>> From: Oleksandr Tyshchenko [mailto:olekst...@gmail.com] >>> Sent: Monday, July 31, 2017 7:58 PM >>>

[Xen-devel] [PATCH RFC v1] xen:rtds: towards work conserving RTDS

Make RTDS scheduler work conserving to utilize the idle resource, without breaking the real-time guarantees. VCPU model: Each real-time VCPU is extended to have a work conserving flag and a priority_level field. When a VCPU's budget is depleted in the current period, if it has work conserving

Re: [Xen-devel] [PATCH v2 00/13] "Non-shared" IOMMU support on ARM

On 01/08/17 04:06, Tian, Kevin wrote: From: Oleksandr Tyshchenko [mailto:olekst...@gmail.com] Sent: Monday, July 31, 2017 7:58 PM Hi, Kevin On Mon, Jul 31, 2017 at 8:57 AM, Tian, Kevin wrote: From: Oleksandr Tyshchenko Sent: Wednesday, July 26, 2017 1:27 AM From:

Re: [Xen-devel] [PATCH v2 00/13] "Non-shared" IOMMU support on ARM

On 31/07/17 06:57, Tian, Kevin wrote: From: Oleksandr Tyshchenko Sent: Wednesday, July 26, 2017 1:27 AM From: Oleksandr Tyshchenko Hi, all. The purpose of this patch series is to create a base for porting any "Non-shared" IOMMUs to Xen on ARM. Saying

[Xen-devel] [linux-4.9 test] 112405: tolerable trouble: blocked/broken/fail/pass - PUSHED

flight 112405 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/112405/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): build-arm64-xsm 2 hosts-allocate broken REGR. vs. 112193 build-arm64-pvops

Re: [Xen-devel] [PATCH OSSTEST v2 11/11] sg-run-job: hook the memdisk test into examine

Roger Pau Monne writes ("[PATCH OSSTEST v2 11/11] sg-run-job: hook the memdisk test into examine"): > Hook the memdisk parameter detection and the saving of the host > properties into the examine jobs. ... > catching-otherwise fail { > + run-ts . =ts-memdisk-try-append +

Re: [Xen-devel] [PATCH OSSTEST v2 09/11] ts-examine-hostprops-save: introduce a script to save properties

Roger Pau Monne writes ("[PATCH OSSTEST v2 09/11] ts-examine-hostprops-save: introduce a script to save properties"): > The introduce script turns the properties stored in the runvars using > the format hostprop_$hotname_$prop=$val into host properties stored in > the database. "This script ..."

Re: [Xen-devel] [PATCH OSSTEST v2 08/11] ts-memdisk-try-append: introduce a script to test memdisk options

Roger Pau Monne writes ("[PATCH OSSTEST v2 08/11] ts-memdisk-try-append: introduce a script to test memdisk options"): > The intended usage is to run this script against every host in order > to record the possible needed memdisk flags. Acked-by: Ian Jackson

Re: [Xen-devel] [PATCH OSSTEST v2 04/11] HostDB: introduce set_property

Roger Pau Monne writes ("[PATCH OSSTEST v2 04/11] HostDB: introduce set_property"): > And provide a helper in TestSupport to use it. This allows osstest to > set host properties from test script themselves (instead of using > the mg-hosts clu). ... > +sub set_property() { > +my ($hd, $ho,

Re: [Xen-devel] [PATCH OSSTEST v2 07/11] ts-freebsd-host-install: add arguments to test memdisk append options

Roger Pau Monne writes ("[PATCH OSSTEST v2 07/11] ts-freebsd-host-install: add arguments to test memdisk append options"): > This is needed in order to figure out which memdisk options should be > used to boot the images on each specific box. > > Note that upon success the script stores the

Re: [Xen-devel] Next Xen ARM community call - Wednesday 2nd August 2017

On Tue, 1 Aug 2017, Julien Grall wrote: > On 01/08/17 17:44, Edgar E. Iglesias wrote: > > On Wed, Jul 26, 2017 at 04:59:43PM +0100, Julien Grall wrote: > > > Hi all, > > > > > > The next Xen ARM community call will be Wednesday 2nd August 2017 5pm BST. > > > > > > Do you have any specific topic

Re: [Xen-devel] [PATCH OSSTEST v2 01/11] netboot_memdisk: allow each host to have different append values

Roger Pau Monne writes ("[PATCH OSSTEST v2 01/11] netboot_memdisk: allow each host to have different append values"): > Some hosts require "append raw" [0] when booting with memdisk, while > others don't. This is based on the hardware/BIOS, and needs to be set > on a per-host basis. Acked-by:

[Xen-devel] [libvirt test] 112406: tolerable trouble: blocked/broken/pass - PUSHED

flight 112406 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/112406/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): build-arm64 2 hosts-allocate broken REGR. vs. 112276 build-arm64-pvops 2

Re: [Xen-devel] [RFC PATCH v1 0/7] IPMMU-VMSA support on ARM

Hi, Julien On Tue, Aug 1, 2017 at 3:27 PM, Julien Grall wrote: > On 26/07/17 16:09, Oleksandr Tyshchenko wrote: >> >> From: Oleksandr Tyshchenko >> >> Hi, all. > > > Hi, > > Please CC maintainers and any relevant person on the cover letter.

Re: [Xen-devel] [XenSummit 2017] Shared coprocessor framework followup

On Tue, Aug 01, 2017 at 08:04:09PM +0300, Andrii Anisov wrote: > Hello Edgar, > > > On 01.08.17 17:56, Edgar E. Iglesias wrote: > >On the PL, there's a chunk of programmable logic that allows you to > >create your own custom accellerators or devices. > >Some devices are tied to specific boards

Re: [Xen-devel] [XenSummit 2017] Shared coprocessor framework followup

Hello Edgar, On 01.08.17 17:56, Edgar E. Iglesias wrote: On the PL, there's a chunk of programmable logic that allows you to create your own custom accellerators or devices. Some devices are tied to specific boards (e.g when they depend on specific IO) but others are not (for example memory to

Re: [Xen-devel] Next Xen ARM community call - Wednesday 2nd August 2017

Hi Edgar, On 01/08/17 17:44, Edgar E. Iglesias wrote: On Wed, Jul 26, 2017 at 04:59:43PM +0100, Julien Grall wrote: Hi all, The next Xen ARM community call will be Wednesday 2nd August 2017 5pm BST. Do you have any specific topic you would like to discuss? CC: Davorin and Mirella from

Re: [Xen-devel] Next Xen ARM community call - Wednesday 2nd August 2017

On Wed, Jul 26, 2017 at 04:59:43PM +0100, Julien Grall wrote: > Hi all, > > The next Xen ARM community call will be Wednesday 2nd August 2017 5pm BST. > > Do you have any specific topic you would like to discuss? CC: Davorin and Mirella from Aggios Hi Julien, I was talking with the Aggios

[Xen-devel] [ovmf baseline-only test] 71925: all pass

This run is configured for baseline tests only. flight 71925 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/71925/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf c65df5d9a14331d2b6d583359f1cf88c3b710d34 baseline

Re: [Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

On Tue, Aug 01, 2017 at 04:07:18PM +0100, Ian Jackson wrote: > Roger Pau Monne writes ("Re: [PATCH OSSTEST 04/11] TestSupport: introduce > set_host_prop"): > > After reading README osstest doesn't seem to have any limitation on > > the characters that can be used for host idents, would you be

Re: [Xen-devel] [PATCH v2] xl: add --clear option to dmesg command

On Tue, Aug 01, 2017 at 11:57:50PM +0800, Xiao Liang wrote: > From: xiliang > > The manual of xl says --clear option is supported and that option worked for > xm. Add that to xl now. I will wrap this long line to 72 columns while committing. > > Signed-off-by: xiliang

Re: [Xen-devel] [PATCH v2] x86/hvm: Allow guest_request vm_events coming from userspace

On Tue, Aug 1, 2017 at 4:30 AM, Andrew Cooper wrote: > On 01/08/17 10:46, Alexandru Isaila wrote: >> Allow guest userspace code to request that a vm_event be sent out >> via VMCALL. This functionality seems to be handy for a number of >> Xen developers, as stated on the

Re: [Xen-devel] [RFC v4]Proposal to allow setting up shared memory areas between VMs from xl config file

Hi Edgar, Thank you for being interested in this project. 2017-08-01 5:55 GMT+08:00 Edgar E. Iglesias : > On Mon, Jul 31, 2017 at 02:30:47PM -0700, Stefano Stabellini wrote: >> On Mon, 31 Jul 2017, Edgar E. Iglesias wrote: >> > On Fri, Jul 28, 2017 at 09:03:15PM +0800,

[Xen-devel] [PATCH v2] xl: add --clear option to dmesg command

From: xiliang The manual of xl says --clear option is supported and that option worked for xm. Add that to xl now. Signed-off-by: xiliang --- tools/xl/xl_info.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tools/xl/xl_info.c

Re: [Xen-devel] [PATCH v2 11/13] xen/pvcalls: implement release command

>> BTW, I also noticed that in rcvmsg you are calling >> wait_event_interruptible() while holding the lock. Have you tested with >> CONFIG_DEBUG_ATOMIC_SLEEP? (or maybe it's some other config option that >> would complain about those sorts of thing) > I believe sleeping while holding a mutex is

Re: [Xen-devel] [PATCH v2 11/13] xen/pvcalls: implement release command

On 01/08/17 17:23, Boris Ostrovsky wrote: > On 07/31/2017 06:34 PM, Stefano Stabellini wrote: >> On Thu, 27 Jul 2017, Boris Ostrovsky wrote: +int pvcalls_front_release(struct socket *sock) +{ + struct pvcalls_bedata *bedata; + struct sock_mapping *map; + int req_id,

Re: [Xen-devel] [PATCH v2 11/13] xen/pvcalls: implement release command

On 07/31/2017 06:34 PM, Stefano Stabellini wrote: > On Thu, 27 Jul 2017, Boris Ostrovsky wrote: >>> +int pvcalls_front_release(struct socket *sock) >>> +{ >>> + struct pvcalls_bedata *bedata; >>> + struct sock_mapping *map; >>> + int req_id, notify; >>> + struct xen_pvcalls_request *req;

[Xen-devel] [linux-3.18 test] 112403: regressions - trouble: blocked/broken/fail/pass

flight 112403 linux-3.18 real [real] http://logs.test-lab.xenproject.org/osstest/logs/112403/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 2 hosts-allocate broken REGR. vs. 112102 build-arm64-pvops

Re: [Xen-devel] [PATCH] vtpmmgr: make inline functions static

Ping On Fri, Jun 23, Olaf Hering wrote: > gcc7 is more strict with functions marked as inline. They are not > automatically inlined. Instead a function call is generated, but the > actual code is not visible by the linker. > > Do a mechanical change and mark every 'inline' as 'static inline'.

Re: [Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

Roger Pau Monne writes ("Re: [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop"): > After reading README osstest doesn't seem to have any limitation on > the characters that can be used for host idents, would you be fine > with me modifying it to add that '-' cannot be used in host

Re: [Xen-devel] [XenSummit 2017] Shared coprocessor framework followup

On Tue, Aug 01, 2017 at 02:52:22PM +0300, Andrii Anisov wrote: > Dear Edgar, > > > On 31.07.17 23:42, Edgar E. Iglesias wrote: > >Yes I'm interested in this. > It's good to hear at least one vote for the stuff :) > > > I'm not sure how much time I'll be able to contribute but at least I can >

Re: [Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

On Tue, Aug 01, 2017 at 03:13:33PM +0100, Ian Jackson wrote: > Roger Pau Monne writes ("Re: [PATCH OSSTEST 04/11] TestSupport: introduce > set_host_prop"): > > On Tue, Aug 01, 2017 at 02:01:35PM +0100, Ian Jackson wrote: > > > TBH, since this is only being called in the one > > >

Re: [Xen-devel] [PATCH]tools: updated "xl_info.c" to accept "--clear" as parameter following "xl dmesg"

On Tue, Aug 01, 2017 at 10:19:35PM +0800, Xiao Liang wrote: > From 85c4bb378cb456fba96bbe6cdc8734f493daeb0c Mon Sep 17 00:00:00 2001 > From: xiliang > Date: Tue, 1 Aug 2017 17:33:02 +0800 > Subject: [PATCH] tools: updated "xl_info.c" to accept "--clear" as parameter >

Re: [Xen-devel] [PATCH]tools: updated "xl_info.c" to accept "--clear" as parameter following "xl dmesg"

On Tue, Aug 01, 2017 at 10:19:35PM +0800, Xiao Liang wrote: > Hello, > > Today I found a minor problem that "xl dmesg --clear" failed to clear Xen's > message buffer. From manual page, it should accept "-c" or "--clear". > I proposed a fix and please help review. I also attached the path in the >

[Xen-devel] [xen-unstable test] 112401: trouble: blocked/broken/fail/pass

flight 112401 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/112401/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 2 hosts-allocate broken REGR. vs.

Re: [Xen-devel] Xen 4.9 + kernel 4.13rc2 -- ballooning regression? reappearance of "Over-allocation for domain 1" errors

On 7/28/17 9:02 AM, PGNet Dev wrote: On 7/27/17 11:23 PM, Juergen Gross wrote: Can you please post the domain's config file used to create the domain and the kernel config? Sure.   https://pastebin.com/M6cr2pX7 Any add'l info needed? ___

Re: [Xen-devel] [PATCH 1/2] arm: smccc: handle SMCs/HVCs according to SMCCC

On Tue, Aug 01, 2017 at 11:59:00AM +0100, Julien Grall wrote: > (+ Edgar, Mark, Dave) > > Hi, Hi Julien, I'll share some thoughts based on our platforms. > On 14/06/17 15:10, Volodymyr Babchuk wrote: > >SMCCC (SMC Call Convention) describes how to handle both HVCs and SMCs. > >SMCCC states

[Xen-devel] [PATCH]tools: updated "xl_info.c" to accept "--clear" as parameter following "xl dmesg"

Hello, Today I found a minor problem that "xl dmesg --clear" failed to clear Xen's message buffer. From manual page, it should accept "-c" or "--clear". I proposed a fix and please help review. I also attached the path in the mail in case mail client format problem. Thanks Fail log: # xl

Re: [Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

Roger Pau Monne writes ("Re: [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop"): > On Tue, Aug 01, 2017 at 02:01:35PM +0100, Ian Jackson wrote: > > TBH, since this is only being called in the one > > ts-set-host-properties-from-runvars script (or whatever you're calling > > it), I think

Re: [Xen-devel] [PATCH] libxc: check pointer is not null before printing

Wei Liu writes ("[PATCH] libxc: check pointer is not null before printing"): > Signed-off-by: Wei Liu Acked-by: Ian Jackson ___ Xen-devel mailing list Xen-devel@lists.xen.org

Re: [Xen-devel] [OSSTEST PATCH] mg-repro-setup: Slightly better document the alloc: syntax

On Tue, Aug 01, 2017 at 02:19:34PM +0100, Ian Jackson wrote: > Provide a clearer indication that the is passed to > mg-allocate (and therefore, implicitly, that mg-allocate's docs should > be consulted). > > Signed-off-by: Ian Jackson > CC: Wei Liu

[Xen-devel] [ovmf test] 112404: all pass - PUSHED

flight 112404 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/112404/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf c65df5d9a14331d2b6d583359f1cf88c3b710d34 baseline version: ovmf

Re: [Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

On Tue, Aug 01, 2017 at 02:01:35PM +0100, Ian Jackson wrote: > Roger Pau Monne writes ("Re: [PATCH OSSTEST 04/11] TestSupport: introduce > set_host_prop"): > > IMHO, I think the right approach is to leave mg-hosts as it is now, > > Yes. > > > and implement a set_property in

[Xen-devel] [OSSTEST PATCH] mg-repro-setup: Slightly better document the alloc: syntax

Provide a clearer indication that the is passed to mg-allocate (and therefore, implicitly, that mg-allocate's docs should be consulted). Signed-off-by: Ian Jackson CC: Wei Liu --- mg-repro-setup | 2 +- 1 file changed, 1 insertion(+), 1

Re: [Xen-devel] [PATCH 0/5] xen: RCU: x86/ARM: Add support of rcu_idle_{enter, exit}

On Tue, 2017-08-01 at 13:02 +, Tomas Thoresen wrote: > With the patch series I was able to create, destroy and re-create the > domU. >   > "Tested-by: Tomas Thoresen " >   Thanks. I'll have to resend the series. If I will not have to change the code much (as it, so far,

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

flight 112400 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/112400/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64 2 hosts-allocate broken REGR. vs. 110515 build-arm64-pvops

[Xen-devel] [PATCH 0/5] xen: RCU: x86/ARM: Add support of rcu_idle_{enter, exit}

With the patch series I was able to create, destroy and re-create the domU. "Tested-by: Tomas Thoresen >" ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

Roger Pau Monne writes ("Re: [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop"): > IMHO, I think the right approach is to leave mg-hosts as it is now, Yes. > and implement a set_property in HostDB/{Executive/Static}.pm and > implement a helper in TestSupport that makes use of it >

Re: [Xen-devel] [PATCH v4 06/13] libxl: change p9 to use generec add function

On Tue, Aug 01, 2017 at 02:58:19PM +0300, Oleksandr Grytsov wrote: > On Mon, Jul 31, 2017 at 5:36 PM, Wei Liu wrote: > > On Sun, Jul 30, 2017 at 09:42:09PM +0300, Oleksandr Grytsov wrote: > >> On Fri, Jul 28, 2017 at 7:23 PM, Wei Liu wrote: > >> > On

Re: [Xen-devel] [RFC PATCH v1 0/7] IPMMU-VMSA support on ARM

On 26/07/17 16:09, Oleksandr Tyshchenko wrote: From: Oleksandr Tyshchenko Hi, all. Hi, Please CC maintainers and any relevant person on the cover letter. This is quite useful to have in the inbox. The purpose of this patch series is to add IPMMU-VMSA

[Xen-devel] [PATCH OSSTEST v2 07/11] ts-freebsd-host-install: add arguments to test memdisk append options

This is needed in order to figure out which memdisk options should be used to boot the images on each specific box. Note that upon success the script stores the tentative host property in the runvars. Signed-off-by: Roger Pau Monné --- Changes since v1: - Provide a

[Xen-devel] [PATCH OSSTEST v2 04/11] HostDB: introduce set_property

And provide a helper in TestSupport to use it. This allows osstest to set host properties from test script themselves (instead of using the mg-hosts clu). Signed-off-by: Roger Pau Monné --- Osstest/HostDB/Executive.pm | 19 +++ Osstest/HostDB/Static.pm|

[Xen-devel] [PATCH OSSTEST v2 02/11] ts-freebsd-host-install: fix image permissions

Make sure images copied to the tftp path have the right permissions, so use dd instead of cp, which will obviously not preserve the original permissions. Signed-off-by: Roger Pau Monné Acked-by: Ian Jackson --- ts-freebsd-host-install | 3 ++- 1

[Xen-devel] [PATCH OSSTEST v2 00/11] Add support to examine the needed memdisk flags for each host

Hello, This builds on top of my previous osstest FreeBSD support series, and expands the examine flight in order to test which memdisk options should be used for each host. Hopefully all of this will be automatic upon running a examine flight. The required options are detected by

[Xen-devel] [PATCH OSSTEST v2 10/11] make-hosts-flight: set runvars for FreeBSD test

This is needed in order to run the memdisk test. Signed-off-by: Roger Pau Monné Acked-by: Ian Jackson --- make-hosts-flight | 3 +++ 1 file changed, 3 insertions(+) diff --git a/make-hosts-flight b/make-hosts-flight index 0152dfe1..d5670857

[Xen-devel] [PATCH OSSTEST v2 08/11] ts-memdisk-try-append: introduce a script to test memdisk options

The intended usage is to run this script against every host in order to record the possible needed memdisk flags. Signed-off-by: Roger Pau Monné --- Changes since v1: - Get the arch of the job and exit with 0 if it's not supported. - Pass the --recordappend argument to

[Xen-devel] [PATCH OSSTEST v2 09/11] ts-examine-hostprops-save: introduce a script to save properties

The introduce script turns the properties stored in the runvars using the format hostprop_$hotname_$prop=$val into host properties stored in the database. Signed-off-by: Roger Pau Monné --- Changes since v1: - Select a host for setting the properties. - Print a message

[Xen-devel] [PATCH OSSTEST v2 03/11] sg-run-job: fix typo in the examine jobs

proc prep-job/host-examine-xen is declared twice, one of them should be prep-job/host-examine-linux instead. Signed-off-by: Roger Pau Monné Acked-by: Ian Jackson --- sg-run-job | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[Xen-devel] [PATCH OSSTEST v2 11/11] sg-run-job: hook the memdisk test into examine

Hook the memdisk parameter detection and the saving of the host properties into the examine jobs. Signed-off-by: Roger Pau Monné --- Changes since v1: - Run the memdisk test first (so that we don't leave the host in a weird state). - Pass a host to the

[Xen-devel] [PATCH OSSTEST v2 05/11] mfi-common: move set_freebsd_runvars to mfi-common

So that it can also be used by make-hosts-flight. No functional change intended. Signed-off-by: Roger Pau Monné Acked-by: Ian Jackson --- make-freebsd-flight | 31 --- mfi-common | 31

[Xen-devel] [PATCH OSSTEST v2 06/11] TestSupport: introduce hostprop_putative_record

This is used to store tentative host properties in the runvars of a job, with the expectation that at some point (ie: at the end of the job) they will be turned into real properties stored in the database. Signed-off-by: Roger Pau Monné Acked-by: Ian Jackson

[Xen-devel] [PATCH OSSTEST v2 01/11] netboot_memdisk: allow each host to have different append values

Some hosts require "append raw" [0] when booting with memdisk, while others don't. This is based on the hardware/BIOS, and needs to be set on a per-host basis. In order to do this, add a new "MemdiskAppend" host property and make use of it in the setup_netboot_memdisk helper. [0]

Re: [Xen-devel] [PATCH v2 1/2] libxl: use xen-blkback for 'vbd' disk types by default

On Mon, Jul 31, 2017 at 05:01:08PM +0100, Wei Liu wrote: > On Mon, Jul 31, 2017 at 04:56:04PM +0100, Wei Liu wrote: > > On Fri, Jul 28, 2017 at 06:42:13PM +0200, Marek Marczykowski-Górecki wrote: > > > This will allow later to make HVM domain without qemu in dom0 (in > > > addition to the one in

Re: [Xen-devel] [PATCH v4 06/13] libxl: change p9 to use generec add function

On Mon, Jul 31, 2017 at 5:36 PM, Wei Liu wrote: > On Sun, Jul 30, 2017 at 09:42:09PM +0300, Oleksandr Grytsov wrote: >> On Fri, Jul 28, 2017 at 7:23 PM, Wei Liu wrote: >> > On Fri, Jul 28, 2017 at 03:11:34PM +0100, Wei Liu wrote: >> >> On Tue, Jul 18,

Re: [Xen-devel] [XenSummit 2017] Shared coprocessor framework followup

Dear Edgar, On 31.07.17 23:42, Edgar E. Iglesias wrote: Yes I'm interested in this. It's good to hear at least one vote for the stuff :) I'm not sure how much time I'll be able to contribute but at least I can review proposals and hopefully look at implementing a driver/backend that may

Re: [Xen-devel] [PATCH V2 2/2] xen:arm: earlyprintk configuration for R-Car Gen3 boards

Hi Andrii, On 27/07/17 15:50, Andrii Anisov wrote: From: Andrii Anisov Introduce an earlyprintk configuration for R-Car Gen3 SoC based development boards, like: - Salvator-X [http://elinux.org/R-Car/Boards/Salvator-X] - M3ULCB [http://elinux.org/R-Car/Boards/M3SK] -

Re: [Xen-devel] [PATCH V2 1/2] xen:arm64: Add SCIF UART support for earlyprintk

Hi Andrii, On 27/07/17 15:50, Andrii Anisov wrote: From: Iurii Konovalenko Add support for a SCIF compatible UART found in Renesas R-Car Gen3 SoCs. Signed-off-by: Iurii Konovalenko Signed-off-by: Iurii Mykhalskyi

Re: [Xen-devel] [RFC v2 3/6] xen/arm: Allow platform_hvc to handle guest SMC calls

On Tue, Aug 01, 2017 at 11:37:05AM +0100, Julien Grall wrote: > Hi Edgar, > > On 31/07/17 23:23, Edgar E. Iglesias wrote: > >On Thu, Feb 09, 2017 at 12:32:09PM -0700, Tamas K Lengyel wrote: > >>On Thu, Feb 9, 2017 at 11:43 AM, Stefano Stabellini > >> wrote: > >>>On Thu, 9

[Xen-devel] [PATCH] libxc: check pointer is not null before printing

Signed-off-by: Wei Liu --- tools/libxc/xc_dom_core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tools/libxc/xc_dom_core.c b/tools/libxc/xc_dom_core.c index cf403432d2..b5f316a1dc 100644 --- a/tools/libxc/xc_dom_core.c +++

Re: [Xen-devel] [PATCH v2 00/13] "Non-shared" IOMMU support on ARM

Hi, Kevin On Tue, Aug 1, 2017 at 6:06 AM, Tian, Kevin wrote: >> From: Oleksandr Tyshchenko [mailto:olekst...@gmail.com] >> Sent: Monday, July 31, 2017 7:58 PM >> >> Hi, Kevin >> >> On Mon, Jul 31, 2017 at 8:57 AM, Tian, Kevin wrote: >> >> From:

Re: [Xen-devel] RT-Xen on ARM

Hello Meng Xu, I've get back to this stuff. On 03.07.17 17:58, Andrii Anisov wrote: That's why we are going to keep configuration (of guests and workloads) close to [1] for evaluation, but on our target SoC. I'm wondering if there are known issues or specifics for ARM. [1]

Re: [Xen-devel] [PATCH v2] x86/hvm: Allow guest_request vm_events coming from userspace

I'm sure we can to this and use a monitor op together with the HVMOP_guest_request_vm_event event. We have discussed this and have a good idea on how to do it. ~Alex From: Andrew Cooper Sent: Tuesday, August 1, 2017 1:30 PM

Re: [Xen-devel] [PATCH 1/2] arm: smccc: handle SMCs/HVCs according to SMCCC

(+ Edgar, Mark, Dave) Hi, On 14/06/17 15:10, Volodymyr Babchuk wrote: SMCCC (SMC Call Convention) describes how to handle both HVCs and SMCs. SMCCC states that both HVC and SMC are valid conduits to call to a different firmware functions. Thus, for example PSCI calls can be made both by SMC or

[Xen-devel] [PATCH v2] xen: get rid of paravirt op adjust_exception_frame

When running as Xen pv-guest the exception frame on the stack contains %r11 and %rcx additional to the other data pushed by the processor. Instead of having a paravirt op being called for each exception type prepend the Xen specific code to each exception entry. When running as Xen pv-guest just

Re: [Xen-devel] [RFC v2 3/6] xen/arm: Allow platform_hvc to handle guest SMC calls

Hi Edgar, On 31/07/17 23:23, Edgar E. Iglesias wrote: On Thu, Feb 09, 2017 at 12:32:09PM -0700, Tamas K Lengyel wrote: On Thu, Feb 9, 2017 at 11:43 AM, Stefano Stabellini wrote: On Thu, 9 Feb 2017, Tamas K Lengyel wrote: On Thu, Feb 9, 2017 at 11:22 AM, Stefano

Re: [Xen-devel] [PATCH 5/5] xen: RCU: avoid busy waiting until the end of grace period.

On Tue, 2017-08-01 at 11:22 +0100, Julien Grall wrote: > On 01/08/17 10:17, Dario Faggioli wrote: > > As soon as this (callbacks being invoked) will have happened, we > > won't > > interrupt it any longer. > > > > And idle CPUs _without_ queued RCU callbacks, won't be interrupted > > at > > all.

  1   2   >