[Xen-devel] [libvirt test] 114793: tolerable all pass - PUSHED

flight 114793 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/114793/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 114713 test-armhf-armhf-libvirt 14

[Xen-devel] [xen-4.7-testing test] 114790: tolerable FAIL - PUSHED

flight 114790 xen-4.7-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/114790/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-xtf-amd64-amd64-4 49 xtf/test-hvm64-lbr-tsx-vmentry fail in 114698 pass in 114790

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

flight 114781 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/114781/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvopsbroken build-armhf-pvops 5

[Xen-devel] [linux-4.9 test] 114766: FAIL

flight 114766 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/114766/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvopsbroken in 114676

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

flight 114786 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/114786/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3866 xen-buildfail REGR. vs. 114507 build-i386-xsm

Re: [Xen-devel] linux-arm-xen branch, commit access, etc.

Hi, Sorry for the formatting. On 20 Oct 2017 19:06, "Stefano Stabellini" wrote: CC'ing Julien On Fri, 20 Oct 2017, Ian Jackson wrote: > Stefano Stabellini writes ("Re: [Xen-devel] linux-arm-xen branch, commit access, etc."): > > On Fri, 20 Oct 2017, Konrad Rzeszutek

Re: [Xen-devel] linux-arm-xen branch, commit access, etc.

CC'ing Julien On Fri, 20 Oct 2017, Ian Jackson wrote: > Stefano Stabellini writes ("Re: [Xen-devel] linux-arm-xen branch, commit > access, etc."): > > On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote: > > > 3. Use upstream released kernels. Follow them when they are released. > > > > I agree

Re: [Xen-devel] [PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support

> On Oct 20, 2017, at 5:20 PM, Ingo Molnar wrote: > > > * Thomas Garnier wrote: > */ - cmpq$.Lentry_SYSCALL_64_after_fastpath_call, (%rsp) + leaq.Lentry_SYSCALL_64_after_fastpath_call(%rip), %r11 + cmpq

Re: [Xen-devel] [PATCH for-4.10 v2] passthrough/vtd: Don't DMA to the stack in queue_invalidate_wait()

On 20/10/17 08:12, Jan Beulich wrote: On 19.10.17 at 18:22, wrote: >> DMA-ing to the stack is generally considered bad practice. In this case, if >> a >> timeout occurs because of a sluggish device which is processing the request, >> the completion notification

Re: [Xen-devel] [RFC 0/4] TEE mediator framework + OP-TEE mediator

On 20.10.17 19:57, Tamas K Lengyel wrote: Hello Tamas, In previous discussion we considered only two variants: in XEN or outside XEN. Stubdomain approach looks more secure, but I'm not sure that it is true. Such stubdomain will need access to all guests memory. If you managed to gain control

Re: [Xen-devel] linux-arm-xen branch, commit access, etc.

Stefano Stabellini writes ("Re: [Xen-devel] linux-arm-xen branch, commit access, etc."): > On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote: > > 3. Use upstream released kernels. Follow them when they are released. > > I agree with Konrad. The reason why that branch is there is that > initially

Re: [Xen-devel] [RFC 0/4] TEE mediator framework + OP-TEE mediator

On Fri, Oct 20, 2017 at 02:11:14PM +0100, Julien Grall wrote: > Hi Volodymyr, Hi Julien, > On 17/10/17 16:59, Volodymyr Babchuk wrote: > >On Mon, Oct 16, 2017 at 01:00:21PM +0100, Julien Grall wrote: > >> > >> > >>On 11/10/17 20:01, Volodymyr Babchuk wrote: > >>>Hello all, > >> > >>Hi Volodymyr,

[Xen-devel] [PATCH for-4.10] scripts: add a script for build testing

Signed-off-by: Wei Liu --- Cc: Andrew Cooper Cc: George Dunlap Cc: Ian Jackson Cc: Jan Beulich Cc: Konrad Rzeszutek Wilk Cc: Stefano Stabellini

Re: [Xen-devel] [PATCH v7] x86/altp2m: Added xc_altp2m_set_mem_access_multi()

On 10/20/2017 07:39 PM, Wei Liu wrote: > On Fri, Oct 20, 2017 at 07:32:50PM +0300, Razvan Cojocaru wrote: >> On 10/20/2017 07:15 PM, Wei Liu wrote: >>> On Mon, Oct 16, 2017 at 08:07:41PM +0300, Petre Pircalabu wrote: From: Razvan Cojocaru For the default

Re: [Xen-devel] linux-arm-xen branch, commit access, etc.

On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote: > On Fri, Oct 20, 2017 at 03:34:40PM +0100, Ian Jackson wrote: > > Currently we are running our ARM tests in osstest off a branch in > > Stefano's personal Linux tree. This is a bit unsatisfactory. > > > > We would like to switch to a branch that

Re: [Xen-devel] [PATCH for-4.10] docs: update coverage.markdown

On Fri, Oct 20, 2017 at 05:30:41PM +0100, Wei Liu wrote: > The coverage support in hypervisor is redone. Update the document. > > Signed-off-by: Wei Liu Adding Julien, although I'm not sure if doc changes also need a release-ack. Reviewed-by: Roger Pau Monné

Re: [Xen-devel] [RFC 0/4] TEE mediator framework + OP-TEE mediator

>> In previous discussion we considered only two variants: in XEN or outside >> XEN. Stubdomain approach looks more secure, but I'm not sure that it is >> true. >> Such stubdomain will need access to all guests memory. If you managed to >> gain control on mediator stubdomain, you can do anything

Re: [Xen-devel] [PATCH for-4.10] docs: update coverage.markdown

Wei Liu writes ("[PATCH for-4.10] docs: update coverage.markdown"): > The coverage support in hypervisor is redone. Update the document. Acked-by: Ian Jackson ___ Xen-devel mailing list Xen-devel@lists.xen.org

Re: [Xen-devel] [PATCH v7] x86/altp2m: Added xc_altp2m_set_mem_access_multi()

On Fri, Oct 20, 2017 at 07:32:50PM +0300, Razvan Cojocaru wrote: > On 10/20/2017 07:15 PM, Wei Liu wrote: > > On Mon, Oct 16, 2017 at 08:07:41PM +0300, Petre Pircalabu wrote: > >> From: Razvan Cojocaru > >> > >> For the default EPT view we have

Re: [Xen-devel] [PATCH v7] x86/altp2m: Added xc_altp2m_set_mem_access_multi()

On Fri, Oct 20, 2017 at 07:32:50PM +0300, Razvan Cojocaru wrote: > On 10/20/2017 07:15 PM, Wei Liu wrote: > > On Mon, Oct 16, 2017 at 08:07:41PM +0300, Petre Pircalabu wrote: > >> From: Razvan Cojocaru > >> > >> For the default EPT view we have

Re: [Xen-devel] [PATCH v7] x86/altp2m: Added xc_altp2m_set_mem_access_multi()

On 10/20/2017 07:15 PM, Wei Liu wrote: > On Mon, Oct 16, 2017 at 08:07:41PM +0300, Petre Pircalabu wrote: >> From: Razvan Cojocaru >> >> For the default EPT view we have xc_set_mem_access_multi(), which >> is able to set an array of pages to an array of access rights

[Xen-devel] [PATCH for-4.10] docs: update coverage.markdown

The coverage support in hypervisor is redone. Update the document. Signed-off-by: Wei Liu --- Cc: Andrew Cooper Cc: George Dunlap Cc: Ian Jackson Cc: Jan Beulich Cc:

Re: [Xen-devel] [PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support

> On Oct 20, 2017, at 5:20 PM, Ingo Molnar wrote: > > > * Thomas Garnier wrote: > */ - cmpq$.Lentry_SYSCALL_64_after_fastpath_call, (%rsp) + leaq.Lentry_SYSCALL_64_after_fastpath_call(%rip), %r11 + cmpq

Re: [Xen-devel] [PATCH v7] x86/altp2m: Added xc_altp2m_set_mem_access_multi()

On Mon, Oct 16, 2017 at 08:07:41PM +0300, Petre Pircalabu wrote: > From: Razvan Cojocaru > > For the default EPT view we have xc_set_mem_access_multi(), which > is able to set an array of pages to an array of access rights with > a single hypercall. However, this

Re: [Xen-devel] [PATCH 54/58] net/xen-netback: Convert timers to use timer_setup()

On Mon, Oct 16, 2017 at 05:29:38PM -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: Wei Liu >

Re: [Xen-devel] linux-arm-xen branch, commit access, etc.

On Fri, Oct 20, 2017 at 03:34:40PM +0100, Ian Jackson wrote: > Currently we are running our ARM tests in osstest off a branch in > Stefano's personal Linux tree. This is a bit unsatisfactory. > > We would like to switch to a branch that Julien can push to too, and > that is in a more official

Re: [Xen-devel] [PATCH for-next] x86/VT-x: Don't use rdmsr() to fill HOST_SYSENTER_{CS, EIP}

On Fri, Oct 20, 2017 at 03:01:30PM +0100, Andrew Cooper wrote: > These are compile-time constants, and don't need to be read back from > hardware. > > Signed-off-by: Andrew Cooper Reviewed-by: Wei Liu

Re: [Xen-devel] [PATCH] x86/xen: support priv-mapping in an HVM tools domain

> -Original Message- > From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of > Boris Ostrovsky > Sent: 20 October 2017 16:09 > To: Paul Durrant ; x...@kernel.org; xen- > de...@lists.xenproject.org; linux-ker...@vger.kernel.org > Cc: Juergen Gross

Re: [Xen-devel] [PATCH 2/3] x86: also show FS/GS base addresses when dumping registers

>>> On 20.10.17 at 16:56, wrote: > On 20/10/17 15:23, Jan Beulich wrote: >> Their state may be important to figure the reason for a crash. To not >> further grow duplicate code, break out a helper function. >> >> I realize that (ab)using the control register array here

Re: [Xen-devel] [PATCH] libxc: don't fail domain creation when unpacking initrd fails

>>> On 19.10.17 at 17:06, wrote: > Jan Beulich writes ("Re: [PATCH] libxc: don't fail domain creation when > unpacking initrd fails"): >> On 16.10.17 at 18:43, wrote: >> > I'm afraid I still find the patch less clear than it could be. >> >

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

On Fri, Oct 20, 2017 at 04:10:16PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct > resume device"): > > On Fri, Oct 20, 2017 at 02:42:53PM +0100, Ian Jackson wrote: > > > Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct

Re: [Xen-devel] [PATCH v12 00/33] osstest: FreeBSD host support

We have decided: We will push the anoint and examine parts of this series to osstest pretest. (You're going to give me a suitable branch on Monday.) This should work because we have anointed FreeBSD builds already. If this works (passes pretest) we will then run a special invocation of the

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

Hi, On 20/10/17 15:51, osstest service owner wrote: flight 114747 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/114747/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt 7 xen-boot

Re: [Xen-devel] [PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support

* Thomas Garnier wrote: > >>*/ > >> - cmpq$.Lentry_SYSCALL_64_after_fastpath_call, (%rsp) > >> + leaq.Lentry_SYSCALL_64_after_fastpath_call(%rip), %r11 > >> + cmpq%r11, (%rsp) > >> jne 1f > > This patch seems to add extra overhead

Re: [Xen-devel] [PATCH 3/3] x86: avoid FS/GS base reads when possible

On 20/10/17 15:24, Jan Beulich wrote: > They're being zeroed a few lines down when non-null selectors are being > found in the respective registers. > > Signed-off-by: Jan Beulich Given that this is within an cpu_has_fsgsbase conditional, there is a moderate chance that the

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device"): > On Fri, Oct 20, 2017 at 02:42:53PM +0100, Ian Jackson wrote: > > Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct > > resume device"): > > I'm not sure what you mean here. We are

Re: [Xen-devel] [PATCH] x86/xen: support priv-mapping in an HVM tools domain

On 10/20/2017 04:35 AM, Paul Durrant wrote: >> -Original Message- >> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of >> Boris Ostrovsky >> Sent: 19 October 2017 18:45 >> To: Paul Durrant ; x...@kernel.org; xen- >> de...@lists.xenproject.org;

Re: [Xen-devel] [PATCH v12 31/33] ts-examine-hostprops-save: introduce a script to save properties

Roger Pau Monne writes ("[PATCH v12 31/33] ts-examine-hostprops-save: introduce a script to save properties"): > This script turns the properties stored in the runvars using the > format hostprop/$ident/$prop=$val into host properties stored in the > database. Acked-by: Ian Jackson

Re: [Xen-devel] [PATCH v12 33/33] sg-run-job: hook the memdisk test into examine

Roger Pau Monne writes ("[PATCH v12 33/33] 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 v2: > - Do not pass

Re: [Xen-devel] [PATCH 2/3] x86: also show FS/GS base addresses when dumping registers

On 20/10/17 15:23, Jan Beulich wrote: > Their state may be important to figure the reason for a crash. To not > further grow duplicate code, break out a helper function. > > I realize that (ab)using the control register array here may not be > considered the nicest solution, but it seems easier

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

On Fri, Oct 20, 2017 at 02:42:53PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct > resume device"): > > On Fri, Oct 20, 2017 at 02:20:29PM +0100, Ian Jackson wrote: > > > I don't think the guest booting "eventually" after some timeout is > > >

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

flight 114747 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/114747/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt 7 xen-boot fail REGR. vs. 114644

Re: [Xen-devel] [PATCH v1 01/27] x86/crypto: Adapt assembly for PIE support

On Fri, Oct 20, 2017 at 1:28 AM, Ard Biesheuvel wrote: > On 20 October 2017 at 09:24, Ingo Molnar wrote: >> >> * Thomas Garnier wrote: >> >>> Change the assembly code to use only relative references of symbols for the >>> kernel

Re: [Xen-devel] [PATCH 1/3] x86: fix GS-base-dirty determination

On 20/10/17 15:22, Jan Beulich wrote: > load_segments() writes the two MSRs in their "canonical" positions > (GS_BASE for the user base, SHADOW_GS_BASE for the kernel one) and uses > SWAPGS to switch them around if the incoming vCPU is in kernel mode. In > order to not leave a stale kernel address

Re: [Xen-devel] [PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support

On Fri, Oct 20, 2017 at 1:26 AM, Ingo Molnar wrote: > > * Thomas Garnier wrote: > >> Change the assembly code to use only relative references of symbols for the >> kernel to be PIE compatible. >> >> Position Independent Executable (PIE) support will allow

[Xen-devel] Libvirt xl to xml converter only picks up first occurrence of an option

Hi Jim I discovered that libvirt's native config file to xml converter for libxl only pick up the first occurrence of an option. For example in a xl cfg file: extra = "abc" ... extra = "def" xl will pick up "def" because that shows up later and takes precedence, while the converter picks up

Re: [Xen-devel] [PATCH v5 06/13] xen/pvcalls: implement bind command

On 10/19/2017 09:31 PM, Stefano Stabellini wrote: > On Tue, 17 Oct 2017, Boris Ostrovsky wrote: >> On 10/06/2017 08:30 PM, Stefano Stabellini wrote: >>> +int pvcalls_front_bind(struct socket *sock, struct sockaddr *addr, int >>> addr_len) >>> +{ >>> + struct pvcalls_bedata *bedata; >>> +

Re: [Xen-devel] [PATCH v12 29/33] ts-freebsd-host-install: add arguments to test memdisk append options

Roger Pau Monne writes ("[PATCH v12 29/33] 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 when passed the --recordappend argument upon

Re: [Xen-devel] [PATCH for-next] x86/VT-x: Don't use rdmsr() to fill HOST_SYSENTER_{CS, EIP}

>>> On 20.10.17 at 16:01, wrote: > These are compile-time constants, and don't need to be read back from > hardware. > > Signed-off-by: Andrew Cooper Reviewed-by: Jan Beulich

Re: [Xen-devel] [PATCH v5 09/13] xen/pvcalls: implement sendmsg

On 10/19/2017 09:41 PM, Stefano Stabellini wrote: > On Tue, 17 Oct 2017, Boris Ostrovsky wrote: >>> +static int __write_ring(struct pvcalls_data_intf *intf, >>> + struct pvcalls_data *data, >>> + struct iov_iter *msg_iter, >>> + int len) >>> +{

Re: [Xen-devel] [PATCH v5 10/13] xen/pvcalls: implement recvmsg

On 10/19/2017 09:38 PM, Stefano Stabellini wrote: > On Tue, 17 Oct 2017, Boris Ostrovsky wrote: >>> + >>> +int pvcalls_front_recvmsg(struct socket *sock, struct msghdr *msg, size_t >>> len, >>> +int flags) >>> +{ >>> + struct pvcalls_bedata *bedata; >>> + int ret; >>> +

Re: [Xen-devel] [PATCH v12 26/33] HostDB: introduce set_property

Roger Pau Monne writes ("[PATCH v12 26/33] 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). > > Note that the setting of host properties is limited to

[Xen-devel] linux-arm-xen branch, commit access, etc.

Currently we are running our ARM tests in osstest off a branch in Stefano's personal Linux tree. This is a bit unsatisfactory. We would like to switch to a branch that Julien can push to too, and that is in a more official place. There are two options: 1. Create an ARM-specific Xen tree.

Re: [Xen-devel] [PATCH v7 1/5] ptp_kvm: probe for kvm guest availability

2017-10-19 14:39+0100, Joao Martins: > In the event of moving pvclock_pvti_cpu0_va() definition to common > pvclock code, this function could return a value on non KVM guests. > If user tried to load the module (or have it builtin) it would fail > with a GPF on ptp_kvm_init when running on a Xen

[Xen-devel] [PATCH 3/3] x86: avoid FS/GS base reads when possible

They're being zeroed a few lines down when non-null selectors are being found in the respective registers. Signed-off-by: Jan Beulich --- a/xen/arch/x86/domain.c +++ b/xen/arch/x86/domain.c @@ -1449,10 +1449,11 @@ static void save_segments(struct vcpu *v if (

[Xen-devel] [PATCH 2/3] x86: also show FS/GS base addresses when dumping registers

Their state may be important to figure the reason for a crash. To not further grow duplicate code, break out a helper function. I realize that (ab)using the control register array here may not be considered the nicest solution, but it seems easier (and less overall overhead) to do so compared to

[Xen-devel] [PATCH 1/3] x86: fix GS-base-dirty determination

load_segments() writes the two MSRs in their "canonical" positions (GS_BASE for the user base, SHADOW_GS_BASE for the kernel one) and uses SWAPGS to switch them around if the incoming vCPU is in kernel mode. In order to not leave a stale kernel address in GS_BASE when the incoming guest is in user

Re: [Xen-devel] [PATCH v5 04/13] xen/pvcalls: implement socket command and handle events

On 10/19/2017 09:26 PM, Stefano Stabellini wrote: > On Tue, 17 Oct 2017, Boris Ostrovsky wrote: >> On 10/06/2017 08:30 PM, Stefano Stabellini wrote: >> with one question: >> >>> + /* >>> +* PVCalls only supports domain AF_INET, >>> +* type SOCK_STREAM and protocol 0 sockets for now. >>>

Re: [Xen-devel] [PATCH 1/1] xen/time: do not decrease steal time after live migration on xen

On 10/20/2017 01:37 AM, Dongli Zhang wrote: > Hi Boris, > > - boris.ostrov...@oracle.com wrote: > >> On 10/19/2017 04:02 AM, Dongli Zhang wrote: >>> After guest live migration on xen, steal time in /proc/stat >>> (cpustat[CPUTIME_STEAL]) might decrease because steal returned by >>>

Re: [Xen-devel] [PATCH V3 26/29] x86/vvtd: Handle interrupt translation faults

>>> On 20.10.17 at 12:08, wrote: > On Fri, Oct 20, 2017 at 01:54:15PM +0800, Chao Gao wrote: >> On Thu, Oct 19, 2017 at 05:31:37PM +0100, Roger Pau Monné wrote: >> >On Thu, Sep 21, 2017 at 11:02:07PM -0400, Lan Tianyu wrote: >> >> +static int vvtd_alloc_frcd(struct vvtd

Re: [Xen-devel] [PATCH v3 for 4.10] x86/vpt: guarantee the return value of pt_update_irq() set in vIRR or PIR

>>> On 20.10.17 at 15:23, wrote: > On 20/10/17 12:42, Jan Beulich wrote: > On 20.10.17 at 02:35, wrote: >>> pt_update_irq() is expected to return the vector number of periodic >>> timer interrupt, which should be set in vIRR of vlapic or in PIR.

[Xen-devel] [PATCH 0/3] x86: FS/GS base handling adjustments

1: fix GS-base-dirty determination 2: also show FS/GS base addresses when dumping registers 3: avoid FS/GS base reads Patch 1 is a bug fix which should be strongly considered for 4.10. Patch 2 has proven helpful in analyzing the original problem, so would be nice to have upstream rather sooner

[Xen-devel] [PATCH for-next] x86/VT-x: Don't use rdmsr() to fill HOST_SYSENTER_{CS, EIP}

These are compile-time constants, and don't need to be read back from hardware. Signed-off-by: Andrew Cooper --- CC: Jan Beulich CC: Wei Liu CC: Jun Nakajima CC: Kevin Tian ---

[Xen-devel] [PATCH v12 31/33] ts-examine-hostprops-save: introduce a script to save properties

This script turns the properties stored in the runvars using the format hostprop/$ident/$prop=$val into host properties stored in the database. Signed-off-by: Roger Pau Monné --- Changes since v2: - Call selecthost based on the idents passed in the putative hostprops

[Xen-devel] [PATCH v12 00/33] osstest: FreeBSD host support

Hello, These are the remainig (not acked) patches of the FreeBSD host install series. The full branch can be found at: git://xenbits.xen.org/people/royger/osstest.git freebsd_v12 Note that before attempting to run a FreeBSD flight an examine flight with blessing real must be executed, so that

[Xen-devel] [PATCH v12 26/33] 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). Note that the setting of host properties is limited to flights with intended blessing real, and it will fail for any other blessing.

[Xen-devel] [PATCH v12 29/33] 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 when passed the --recordappend argument upon success the script stores the tentative host property in the runvars. Signed-off-by: Roger Pau Monné

[Xen-devel] [PATCH v12 33/33] 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 v2: - Do not pass a host ident to ts-examine-hostprops-save. - Use .- for ts-memdisk-try-append so that the rest of the job

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device"): > On Fri, Oct 20, 2017 at 02:20:29PM +0100, Ian Jackson wrote: > > I don't think the guest booting "eventually" after some timeout is > > correct. > > The OS is honoring whatever is written in the resume

[Xen-devel] [PATCH v5.1 1/8] xen: link against xentoolcore

From: Anthony PERARD Xen libraries in 4.10 include a new xentoolcore library. This contains the xentoolcore_restrict_all function which we are about to want to use. Signed-off-by: Ian Jackson --- v5: More truthful commit message. ---

[Xen-devel] [PATCH v5.1 3/8] xen: defer call to xen_restrict until just before os_setup_post

We need to restrict *all* the control fds that qemu opens. Looking in /proc/PID/fd shows there are many; their allocation seems scattered throughout Xen support code in qemu. We must postpone the restrict call until roughly the same time as qemu changes its uid, chroots (if applicable), and so

[Xen-devel] [PATCH v5.1 5/8] xen: move xc_interface compatibility fallback further up the file

We are going to want to use the dummy xendevicemodel_handle type in new stub functions in the CONFIG_XEN_CTRL_INTERFACE_VERSION < 41000 section. So we need to provide that definition, or (as applicable) include the appropriate header, earlier in the file. (Ideally the newer compatibility layers

[Xen-devel] [PATCH v5.1 4/8] xen: destroy_hvm_domain: Move reason into a variable

We are going to want to reuse this. No functional change. Signed-off-by: Ian Jackson Reviewed-by: Anthony PERARD --- hw/i386/xen/xen-hvm.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/hw/i386/xen/xen-hvm.c

[Xen-devel] [PATCH v5.1 8/8] configure: do_compiler: Dump some extra info under bash

This makes it much easier to find a particular thing in config.log. The information may be lacking in other shells, resulting in harmless empty output. (This is why we don't use the proper ${FUNCNAME[*]} array syntax - other shells will choke on that.) The extra output is only printed if

[Xen-devel] [PATCH v5.1 2/8] xen: restrict: use xentoolcore_restrict_all

And insist that it works. Drop individual use of xendevicemodel_restrict and xenforeignmemory_restrict. These are not actually effective in this version of qemu, because qemu has a large number of fds open onto various Xen control devices. The restriction arrangements are still not right,

[Xen-devel] [PATCH v5.1 6/8] xen: destroy_hvm_domain: Try xendevicemodel_shutdown

xc_interface_open etc. is not going to work if we have dropped privilege, but xendevicemodel_shutdown will if everything is new enough. xendevicemodel_shutdown is only availabe in Xen 4.10 and later, so provide a stub for earlier versions. Signed-off-by: Ian Jackson

[Xen-devel] [PATCH v5.1 7/8] os-posix: Provide new -runas : facility

This allows the caller to specify a uid and gid to use, even if there is no corresponding password entry. This will be useful in certain Xen configurations. We don't support just -runas because: (i) deprivileging without calling setgroups would be ineffective (ii) given only a uid we don't know

Re: [Xen-devel] [PATCH v5 0/8] xen: xen-domid-restrict improvements

Anthony PERARD writes ("Re: [PATCH v5 0/8] xen: xen-domid-restrict improvements"): > The patches in this v5 appear to be the same the one from the patch > series v4. Erk, so they are. I'll post a v5.1 in reply to this email. Ian. ___ Xen-devel

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

On Fri, Oct 20, 2017 at 02:20:29PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct > resume device"): > > I wouldn't call this behaviour a bug. Most people won't notice it > > because the guest will boot eventually. It is not like this will

Re: [Xen-devel] [PATCH v3 2/7] xsm: flask: change the dummy xsm policy and flask hook for map_gmfn_foregin

On 10/20/2017 02:14 AM, Jan Beulich wrote: On 19.10.17 at 19:36, wrote: On 10/19/2017 07:58 AM, Jan Beulich wrote: On 19.10.17 at 04:36, wrote: --- a/xen/include/xsm/dummy.h +++ b/xen/include/xsm/dummy.h @@ -516,7 +516,8 @@ static XSM_INLINE int

Re: [Xen-devel] [PATCH v5 0/8] xen: xen-domid-restrict improvements

Hi Ian, The patches in this v5 appear to be the same the one from the patch series v4. -- Anthony PERARD ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH v3 for 4.10] x86/vpt: guarantee the return value of pt_update_irq() set in vIRR or PIR

Hi Jan, On 20/10/17 12:42, Jan Beulich wrote: On 20.10.17 at 02:35, wrote: pt_update_irq() is expected to return the vector number of periodic timer interrupt, which should be set in vIRR of vlapic or in PIR. Otherwise it would trigger the assertion in vmx_intr_assist(),

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

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

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device"): > I wouldn't call this behaviour a bug. Most people won't notice it > because the guest will boot eventually. It is not like this will cause > the guest to crash. I don't think the guest booting

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

On Fri, Oct 20, 2017 at 01:35:41PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct > resume device"): > > On Fri, Oct 20, 2017 at 12:05:55PM +0100, Ian Jackson wrote: > > > Wei Liu writes ("[OSSTEST PATCH 11/16] ts-debian-fixup: use correct > >

Re: [Xen-devel] [RFC 0/4] TEE mediator framework + OP-TEE mediator

Hi Volodymyr, On 17/10/17 16:59, Volodymyr Babchuk wrote: On Mon, Oct 16, 2017 at 01:00:21PM +0100, Julien Grall wrote: On 11/10/17 20:01, Volodymyr Babchuk wrote: Hello all, Hi Volodymyr, Hi Julien I want to present TEE mediator, that was discussed earlier ([1]). I selected design

Re: [Xen-devel] [OSSTEST PATCH 10/16] ts-debian-fixup: remove extra= before appending our own

On Fri, Oct 20, 2017 at 01:52:50PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [OSSTEST PATCH 10/16] ts-debian-fixup: remove extra= > before appending our own"): > > On Fri, Oct 20, 2017 at 12:03:24PM +0100, Ian Jackson wrote: > > > Wei Liu writes ("[OSSTEST PATCH 10/16] ts-debian-fixup:

Re: [Xen-devel] [PATCH v3 2/7] xsm: flask: change the dummy xsm policy and flask hook for map_gmfn_foregin

On 10/19/2017 08:55 PM, Zhongze Liu wrote: 2017-10-20 8:34 GMT+08:00 Zhongze Liu : Hi Daniel, 2017-10-20 1:36 GMT+08:00 Daniel De Graaf : On 10/18/2017 10:36 PM, Zhongze Liu wrote: The original dummy xsm_map_gmfn_foregin checks if source domain

Re: [Xen-devel] [OSSTEST PATCH 10/16] ts-debian-fixup: remove extra= before appending our own

Wei Liu writes ("Re: [OSSTEST PATCH 10/16] ts-debian-fixup: remove extra= before appending our own"): > On Fri, Oct 20, 2017 at 12:03:24PM +0100, Ian Jackson wrote: > > Wei Liu writes ("[OSSTEST PATCH 10/16] ts-debian-fixup: remove extra= > > before appending our own"): > > > The original extra=

Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device"): > On Fri, Oct 20, 2017 at 12:05:55PM +0100, Ian Jackson wrote: > > Wei Liu writes ("[OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume > > device"): > > > See code comment for explanation. > > ... > >

Re: [Xen-devel] [PATCH v3 for 4.10] x86/vpt: guarantee the return value of pt_update_irq() set in vIRR or PIR

>>> On 20.10.17 at 02:35, wrote: > pt_update_irq() is expected to return the vector number of periodic > timer interrupt, which should be set in vIRR of vlapic or in PIR. > Otherwise it would trigger the assertion in vmx_intr_assist(), please > seeing >

[Xen-devel] [xen-4.8-testing baseline-only test] 72333: regressions - trouble: blocked/broken/fail/pass

This run is configured for baseline tests only. flight 72333 xen-4.8-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/72333/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-livepatch5

Re: [Xen-devel] [OSSTEST PATCH 03/16] ts-xen-build-prep: don't install w3c-dtd-xhtml for Stretch onward

On Fri, Oct 20, 2017 at 11:50:11AM +0100, Ian Jackson wrote: > Wei Liu writes ("[OSSTEST PATCH 03/16] ts-xen-build-prep: don't install > w3c-dtd-xhtml for Stretch onward"): > > It is not included in Stretch. > > > > That package was installed because libvirt build needed it. However > > libvirt

Re: [Xen-devel] [PATCH V3 00/29]

On Thu, Sep 21, 2017 at 11:01:41PM -0400, Lan Tianyu wrote: > Change since v2: >1) Remove vIOMMU hypercall of query capabilities and introduce when > necessary. >2) Remove length field of vIOMMU create parameter of vIOMMU hypercall >3) Introduce irq remapping mode callback

Re: [Xen-devel] [OSSTEST PATCH 16/16] ts-guests-nbd-mirror: make it work with stretch

On Fri, Oct 20, 2017 at 12:24:43PM +0100, Wei Liu wrote: > On Fri, Oct 20, 2017 at 12:09:35PM +0100, Ian Jackson wrote: > > Wei Liu writes ("[OSSTEST PATCH 16/16] ts-guests-nbd-mirror: make it work > > with stretch"): > > > On the server side, only add oldstyle= and port= on jessie. Stretch > > >

Re: [Xen-devel] [PATCH V3 29/29] x86/vvtd: save and restore emulated VT-d

On Thu, Sep 21, 2017 at 11:02:10PM -0400, Lan Tianyu wrote: > From: Chao Gao > > Provide a save-restore pair to save/restore registers and non-register > status. > > Signed-off-by: Chao Gao > Signed-off-by: Lan Tianyu > --- > v3: >

Re: [Xen-devel] [OSSTEST PATCH 16/16] ts-guests-nbd-mirror: make it work with stretch

On Fri, Oct 20, 2017 at 12:09:35PM +0100, Ian Jackson wrote: > Wei Liu writes ("[OSSTEST PATCH 16/16] ts-guests-nbd-mirror: make it work > with stretch"): > > On the server side, only add oldstyle= and port= on jessie. Stretch > > doesn't support or need those anymore. > > See my earlier

Re: [Xen-devel] [PATCH V3 28/29] x86/vvtd: Add queued invalidation (QI) support

On Thu, Sep 21, 2017 at 11:02:09PM -0400, Lan Tianyu wrote: > From: Chao Gao > > Queued Invalidation Interface is an expanded invalidation interface with > extended capabilities. Hardware implementations report support for queued > invalidation interface through the Extended

Re: [Xen-devel] [OSSTEST PATCH 01/16] XXX add a stretch config based on production-config

On Fri, Oct 20, 2017 at 11:54:44AM +0100, Ian Jackson wrote: > Wei Liu writes ("[OSSTEST PATCH 01/16] XXX add a stretch config based on > production-config"): > > diff -ub production-config production-config-stretch > > The changes LGTM but obviously this ought to go straight into >

Re: [Xen-devel] [OSSTEST PATCH 10/16] ts-debian-fixup: remove extra= before appending our own

On Fri, Oct 20, 2017 at 12:03:24PM +0100, Ian Jackson wrote: > Wei Liu writes ("[OSSTEST PATCH 10/16] ts-debian-fixup: remove extra= before > appending our own"): > > The original extra= was not removed, so there were two extra= in the > > resulting config file. > > What is the original extra= ?

  1   2   3   >