[Xen-devel] [linux-linus test] 58128: tolerable FAIL - PUSHED

flight 58128 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/58128/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-sedf-pin 6 xen-boot fail REGR. vs. 57931 test-amd64-i386-libvirt 1

Re: [Xen-devel] [PATCH] xen/pass-through: ROM BAR handling adjustments

>>> On 05.06.15 at 18:41, wrote: > On Fri, 5 Jun 2015, Jan Beulich wrote: >> >>> On 05.06.15 at 13:32, wrote: >> >> --- a/hw/xen/xen_pt.c >> >> +++ b/hw/xen/xen_pt.c >> >> @@ -248,7 +248,9 @@ static void xen_pt_pci_write_config(PCID >> >> >> >> /* check unused BAR register */ >> >> in

[Xen-devel] [qemu-mainline bisection] complete test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm

branch xen-unstable xen branch xen-unstable job test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm test guest-saverestore Tree: linux git://xenbits.xen.org/linux-pvops.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

>>> On 07.06.15 at 08:23, wrote: > On Mon, Apr 20, 2015 at 04:32:12PM +0200, Michael S. Tsirkin wrote: >> On Mon, Apr 20, 2015 at 03:08:09PM +0100, Jan Beulich wrote: >> > >>> On 20.04.15 at 15:43, wrote: >> > > On Mon, Apr 13, 2015 at 01:51:06PM +0100, Jan Beulich wrote: >> > >> >>> On 13.04.15

[Xen-devel] PCI Passthrough ARM Design : Draft1

PCI Pass-through in Xen ARM -- Index 1. Background 2. Basic PCI Support in Xen ARM 2.1 pci_hostbridge and pci_hostbridge_ops 2.2 PHYSDEVOP_pci_host_bridge_add hypercall 3. Dom0 Access PCI devices 4. DomU assignment of PCI device 5. NUMA and PCI passthrough 6. DomU pci devi

Re: [Xen-devel] Xen 4.6 Development Update (five months reminder, 5 WEEKS TO FREEZE)

> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com] > Sent: Friday, June 05, 2015 10:28 PM > > On 06/05/2015 09:53 AM, wei.l...@citrix.com wrote: > > > > * VPMU - 'perf' support in Xen (good) > > v21 posted > > Need reviews/final ack. > >- Boris Ostrovsky > > I posted a vers

Re: [Xen-devel] [Qemu-devel] qemu mainline regression with xen-unstable: unable to start QMP

Eric Blake writes: > [adding Markus, as author of the regression] > > On 06/04/2015 03:59 PM, Don Slutz wrote: >> On 06/04/15 11:04, Fabio Fantoni wrote: >>> Today after trying xen-unstable build (tested many hours) of some days >>> ago I tried update qemu to latest development version (from git

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

>>> On 05.06.15 at 12:48, wrote: > On Fri, 2015-06-05 at 10:18 +0100, Jan Beulich wrote: >> >>> On 05.06.15 at 11:07, wrote: >> > WRT the move to the colo, flights in 5 are in the new one, while >> > 3 are in the old one, >> > http://logs.test-lab.xenproject.org/osstest/results/history.te

Re: [Xen-devel] [PATCH v2 6/9] x86/intel_pstate: the main boby of the intel_pstate driver

On 08/06/2015 14:50, Jan Beulich wrote: > >>> On 08.06.15 at 03:47, wrote: > > On 26/05/2015 21:58, Jan Beulich wrote > >> >>> On 13.05.16 at 09:50, wrote: > >> > +static int byt_get_min_pstate(void) { > >> > +u64 value; > >> > + > >> > +rdmsrl(BYT_RATIOS, value); > >> > +return (valu

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

On 08/06/15 08:42, Jan Beulich wrote: On 07.06.15 at 08:23, wrote: >> On Mon, Apr 20, 2015 at 04:32:12PM +0200, Michael S. Tsirkin wrote: >>> On Mon, Apr 20, 2015 at 03:08:09PM +0100, Jan Beulich wrote: >>> On 20.04.15 at 15:43, wrote: > On Mon, Apr 13, 2015 at 01:51:06PM +0100, Jan

Re: [Xen-devel] Xen 4.6 Development Update (five months reminder, 5 WEEKS TO FREEZE)

On 6/5/2015 9:53 PM, wei.l...@citrix.com wrote: (Note, please trim your quotes when replying, and also trim the CC list if necessary. You might also consider changing the subject line of your reply to "Status of (Was: Xen 4.6 Development Update (X months reminder)") Hi all We are now four mo

Re: [Xen-devel] [RFC v2] xSplice design

On 05.06.2015 17:27, Jan Beulich wrote: On 05.06.15 at 17:00, wrote: >> On Wed, May 20, 2015 at 05:11:20PM +0200, Martin Pohlack wrote: >>> * Xen as it is now, has a couple of non-unique symbol names which will >>> make runtime symbol identification hard. Sometimes, static symbols >>> si

Re: [Xen-devel] Xen 4.6 Development Update (five months reminder, 5 WEEKS TO FREEZE)

> -Original Message- > > * Intel GVT-g (none) > > requires refactoring ioreq-server, fixing 16-byte MMIO emulation > > and optional PV IOMMU support > >- Yu, Zhang > ioreq-server: still in development. Previously tried to refactor the > ioreq-server to track the IO resources b

Re: [Xen-devel] [RFC v2] xSplice design

>>> On 08.06.15 at 10:34, wrote: > On 05.06.2015 17:27, Jan Beulich wrote: > On 05.06.15 at 17:00, wrote: >>> On Wed, May 20, 2015 at 05:11:20PM +0200, Martin Pohlack wrote: * Xen as it is now, has a couple of non-unique symbol names which will make runtime symbol identification h

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

On Mon, 2015-06-08 at 09:07 +0100, Jan Beulich wrote: > >>> On 05.06.15 at 12:48, wrote: > > On Fri, 2015-06-05 at 10:18 +0100, Jan Beulich wrote: > >> >>> On 05.06.15 at 11:07, wrote: > >> > WRT the move to the colo, flights in 5 are in the new one, while > >> > 3 are in the old one, > >

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

On Mon, Jun 08, 2015 at 09:09:15AM +0100, Malcolm Crossley wrote: > On 08/06/15 08:42, Jan Beulich wrote: > On 07.06.15 at 08:23, wrote: > >> On Mon, Apr 20, 2015 at 04:32:12PM +0200, Michael S. Tsirkin wrote: > >>> On Mon, Apr 20, 2015 at 03:08:09PM +0100, Jan Beulich wrote: > >>> On 20.

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

>>> On 08.06.15 at 10:09, wrote: > On 08/06/15 08:42, Jan Beulich wrote: >> Not really. All we concluded so far is that _maybe_ the bridge, upon >> seeing the UR, generates a Master Abort, rendering the whole thing >> fatal. Otoh the respective root port also has >> - Received Master Abort set in

[Xen-devel] 答复： Re: [PATCH V3 3/6] libxl: add pvusb API

>>> 在 2:06 的 2015/5/20 上，在讯息 中，George Dunlap 写入： > On Sun, Apr 19, 2015 at 4:50 AM, Chunyan Liu wrote: > > Add pvusb APIs, including: > > - attach/detach (create/destroy) virtual usb controller. > > - attach/detach usb device > > - list usb controller and usb devices > > - some other helpe

Re: [Xen-devel] RFC: making the PVH 64bit ABI as stableo

On Fri, 2015-06-05 at 18:21 +0100, Andrew Cooper wrote: > However, I expect it to turn into (HVM - Qemu + very few extra PV > hypercalls) Don't forget "- " and "- some other stuff which I'm sure I'm forgetting from Tim's original list of things to be made conditional". Ian. ___

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

>>> On 08.06.15 at 10:53, wrote: > That's 6/14 (43%) failure rate on fiano0 and 2/10 (20%) on fiano1. Which > differs form the apparent xen-unstable failure rate. But I wouldn't take > this as evidence that the two systems differ significantly, despite how > the unstable results looked at first gl

Re: [Xen-devel] [qemu-mainline test] 57925: regressions - FAIL

On Sun, 2015-06-07 at 11:28 +, osstest service user wrote: > flight 57925 qemu-mainline real [real] > http://logs.test-lab.xenproject.org/osstest/logs/57925/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: I think it is pretty s

Re: [Xen-devel] [PATCH v2 6/9] x86/intel_pstate: the main boby of the intel_pstate driver

>>> On 08.06.15 at 10:18, wrote: > Regarding the self-documenting related comment here, which of the following > do you think is better? > 1) > #define BYT_MIN_PSTATE_SHIFT8 > #define BYT_MAX_PSTATE_SHIFT 16 > #define BYT_PSTATE_MASK 0x7f > #define BYT

Re: [Xen-devel] [libvirt test] 58119: regressions - FAIL

On Mon, 2015-06-08 at 04:37 +, osstest service user wrote: > flight 58119 libvirt real [real] > http://logs.test-lab.xenproject.org/osstest/logs/58119/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: This has been failing for a

Re: [Xen-devel] [PATCH v23 11/15] VPMU/AMD: Check MSR values before writing to hardware

>>> On 05.06.15 at 18:32, wrote: > On 06/05/2015 12:03 PM, Jan Beulich wrote: > On 29.05.15 at 20:42, wrote: >>> @@ -289,19 +302,24 @@ static int amd_vpmu_do_wrmsr(unsigned int msr, >>> uint64_t > msr_content, >>> { >>> struct vcpu *v = current; >>> struct vpmu_struct *vpmu =

Re: [Xen-devel] [PATCH v2 COLOPre 01/13] libxc/restore: fix error handle of process_record

On 08/06/15 04:43, Yang Hongyang wrote: > If the err is RECORD_NOT_PROCESSED, and it is an optional record, > restore will still fail. The patch fix this. > > Signed-off-by: Yang Hongyang > CC: Ian Campbell > CC: Ian Jackson > CC: Wei Liu > CC: Andrew Cooper > --- > tools/libxc/xc_sr_restore.

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

On Mon, 2015-06-08 at 10:15 +0100, Jan Beulich wrote: > >>> On 08.06.15 at 10:53, wrote: > > That's 6/14 (43%) failure rate on fiano0 and 2/10 (20%) on fiano1. Which > > differs form the apparent xen-unstable failure rate. But I wouldn't take > > this as evidence that the two systems differ signif

Re: [Xen-devel] [qemu-mainline test] 57925: regressions - FAIL

Il 08/06/2015 11:16, Ian Campbell ha scritto: On Sun, 2015-06-07 at 11:28 +, osstest service user wrote: flight 57925 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/57925/ Regressions :-( Tests which did not succeed and are blocking, including tests which could

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

On Mon, Jun 08, 2015 at 08:42:57AM +0100, Jan Beulich wrote: > >>> On 07.06.15 at 08:23, wrote: > > On Mon, Apr 20, 2015 at 04:32:12PM +0200, Michael S. Tsirkin wrote: > >> On Mon, Apr 20, 2015 at 03:08:09PM +0100, Jan Beulich wrote: > >> > >>> On 20.04.15 at 15:43, wrote: > >> > > On Mon, Apr 13

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

On Mon, Jun 08, 2015 at 10:03:18AM +0100, Jan Beulich wrote: > >>> On 08.06.15 at 10:09, wrote: > > On 08/06/15 08:42, Jan Beulich wrote: > >> Not really. All we concluded so far is that _maybe_ the bridge, upon > >> seeing the UR, generates a Master Abort, rendering the whole thing > >> fatal. Ot

Re: [Xen-devel] [PATCH v2 COLOPre 01/13] libxc/restore: fix error handle of process_record

On 06/08/2015 05:24 PM, Andrew Cooper wrote: On 08/06/15 04:43, Yang Hongyang wrote: If the err is RECORD_NOT_PROCESSED, and it is an optional record, restore will still fail. The patch fix this. Signed-off-by: Yang Hongyang CC: Ian Campbell CC: Ian Jackson CC: Wei Liu CC: Andrew Cooper

Re: [Xen-devel] [PATCH v2 COLOPre 01/13] libxc/restore: fix error handle of process_record

On 08/06/15 10:37, Yang Hongyang wrote: > > > On 06/08/2015 05:24 PM, Andrew Cooper wrote: >> On 08/06/15 04:43, Yang Hongyang wrote: >>> If the err is RECORD_NOT_PROCESSED, and it is an optional record, >>> restore will still fail. The patch fix this. >>> >>> Signed-off-by: Yang Hongyang >>> CC:

Re: [Xen-devel] [PATCH v2 COLOPre 03/13] libxc/restore: zero ioreq page only one time

On 08/06/15 04:43, Yang Hongyang wrote: > ioreq page contains evtchn which will be set when we resume the > secondary vm the first time. The hypervisor will check if the > evtchn is corrupted, so we cannot zero the ioreq page more > than one time. > > The ioreq->state is always STATE_IOREQ_NONE aft

Re: [Xen-devel] [PATCH v2 COLOPre 03/13] libxc/restore: zero ioreq page only one time

On 08/06/15 10:46, Andrew Cooper wrote: > On 08/06/15 04:43, Yang Hongyang wrote: >> ioreq page contains evtchn which will be set when we resume the >> secondary vm the first time. The hypervisor will check if the >> evtchn is corrupted, so we cannot zero the ioreq page more >> than one time. >> >>

Re: [Xen-devel] [PATCH v2 COLOPre 03/13] libxc/restore: zero ioreq page only one time

On 06/08/2015 05:46 PM, Andrew Cooper wrote: On 08/06/15 04:43, Yang Hongyang wrote: ioreq page contains evtchn which will be set when we resume the secondary vm the first time. The hypervisor will check if the evtchn is corrupted, so we cannot zero the ioreq page more than one time. The iore

Re: [Xen-devel] [Draft D] Xen on ARM vITS Handling

On Fri, 2015-06-05 at 22:41 +0530, Vijay Kilari wrote: > On Fri, Jun 5, 2015 at 10:08 PM, Ian Campbell wrote: > > On Fri, 2015-06-05 at 21:25 +0530, Vijay Kilari wrote: > >> Let xen mark those phantom devices added using MAPD as dummy and > >> just emulate and does not translate ITS commands for t

Re: [Xen-devel] [PATCH 2/5] xen/vm_access: Support for memory-content hiding

On 05/08/2015 07:07 PM, Jan Beulich wrote: >> > --- a/xen/include/asm-x86/domain.h >> > +++ b/xen/include/asm-x86/domain.h >> > @@ -512,6 +513,7 @@ struct arch_vcpu >> > uint32_t emulate_flags; >> > unsigned long gpa; >> > unsigned long eip; >> > +struct vm_event_

Re: [Xen-devel] [RFC 22/22] xen/arm: gic-v3: Add support of vGICv2 when available

On Fri, 2015-06-05 at 17:35 +0100, Julien Grall wrote: > >> */ > >> static void gicv3_enable_sre(void) > >> { > >> uint32_t val; > >> > >> val = READ_SYSREG32(ICC_SRE_EL2); > >> -val |= GICC_SRE_EL2_SRE | GICC_SRE_EL2_ENEL1; > >> +val |= GICC_SRE_EL2_SRE; > >> > >> W

Re: [Xen-devel] [RFC 20/22] xen/arm: gic: Expose the vGIC versions suported by GIC

On Fri, 2015-06-05 at 18:59 +0100, Julien Grall wrote: > Hi Ian, > > On 05/06/2015 13:35, Ian Campbell wrote: > > On Fri, 2015-05-08 at 14:29 +0100, Julien Grall wrote: > >> Some version of the GIC are able so support multiple versions of the > >> vGIC. > >> > >> For instance, some version of the

Re: [Xen-devel] [PATCH v2 COLOPre 04/13] tools/libxc: export xc_bitops.h

Just to note that xc_bitops.h needs cleanup as Andy pointed out in v1... It will done in v3. On 06/08/2015 11:43 AM, Yang Hongyang wrote: When we are under COLO, we will send dirty page bitmap info from secondary to primary at every checkpoint. So we need to get/test the dirty page bitmap. We ju

[Xen-devel] [PATCH v2] VPMU: add lost Intel processor

From: Alan Robinson commit 6d112f2b50 ("x86/vPMU: change Intel model numbers from decimal to hex") translated 47 to 0x27, now corrected to 0x2f. Signed-off-by: Alan Robinson Signed-off-by: Dietmar Hahn --- Changed since v1: (after talking to Dietmar, he's away from his email for a while)

Re: [Xen-devel] [PATCH v11 8/9] Add IOREQ_TYPE_VMWARE_PORT

On 06/04/2015 12:28 PM, Don Slutz wrote: > On 06/03/15 13:09, George Dunlap wrote: >> On 05/22/2015 04:50 PM, Don Slutz wrote: >>> This adds synchronization of the 6 vcpu registers (only 32bits of >>> them) that vmport.c needs between Xen and QEMU. >>> >>> This is to avoid a 2nd and 3rd exchange be

Re: [Xen-devel] [PATCH V6 03/10] xen/arm: Use the new functions for vCPUID/vaffinity transformation

On Fri, 2015-06-05 at 19:18 +0100, Julien Grall wrote: > On 05/06/2015 16:56, Ian Campbell wrote: > > On Mon, 2015-06-01 at 20:56 +0800, Chen Baozi wrote: > >> From: Chen Baozi > >> > >> There are 3 places to change: > >> > >> * Initialise vMPIDR value in vcpu_initialise() > >> * Find the vCPU fro

Re: [Xen-devel] [PATCH V6 05/10] xen/arm64: gicv3: Use AFF1 when translating ICC_SGI1R_EL1 to cpumask

On Fri, 2015-06-05 at 19:25 +0100, Julien Grall wrote: > > On 05/06/2015 17:09, Ian Campbell wrote: > >> + * injection, ignoring level 2 & 3. > >> + */ > >> +if ( gicv3_sgir_to_cpumask(&vcpu_mask, sgir) ) > >> +{ > >> +gprintk(XENLOG_WARNING, "Wrong affi

Re: [Xen-devel] [Formal Vote] Changes to Xen Project Security Vulnerability Process - Open until June 8th, 2015

> On 5 Jun 2015, at 12:43, Ian Campbell wrote: > > On Fri, 2015-06-05 at 12:32 +0100, Lars Kurth wrote: >>> On 3 Jun 2015, at 10:35, Ian Campbell wrote: >>> >>> On Mon, 2015-06-01 at 10:36 +0100, Lars Kurth wrote: In the event that we do not have a patch available two working weeks b

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

On Mon, 2015-06-08 at 10:15 +0100, Jan Beulich wrote: > (I'm trying to make myself a picture of what debugging options we > have.) In the meantime I've kicked off an adhoc job using no-apicv as suggested by Andy (on IIRC last week IIRC). Assuming that my tweak takes effect in practice I'll run a b

Re: [Xen-devel] [PATCH v2 COLOPre 03/13] libxc/restore: zero ioreq page only one time

On 08/06/15 10:58, Yang Hongyang wrote: > > > On 06/08/2015 05:46 PM, Andrew Cooper wrote: >> On 08/06/15 04:43, Yang Hongyang wrote: >>> ioreq page contains evtchn which will be set when we resume the >>> secondary vm the first time. The hypervisor will check if the >>> evtchn is corrupted, so we

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

>>> On 08.06.15 at 11:27, wrote: > I don't know much about the hardware in the pool other than what can be > gathered from the serial and dmesg logs. Right - this is useful for learning details of an individual system, but isn't really helpful when wanting to compare all system kinds that are in

Re: [Xen-devel] [PATCH v2] xen/pcifront: Remove usage of struct timeval

On 19/05/15 07:08, Tina Ruchandani wrote: > struct timeval uses a 32-bit field for representing seconds, > which will overflow in the year 2038 and beyond. This patch replaces > struct timeval with 64-bit ktime_t which is 2038 safe. > The patch is part of a larger effort to remove instances of > 32

Re: [Xen-devel] clarification of xen Wiki article

On 6/4/2015 3:58 AM, Ian Campbell wrote: On Wed, 2015-06-03 at 09:24 -0600, Linda wrote: Hi all, I was reading http://wiki.xen.org/wiki/XenBus In the section on Store Organization, there is the statement "Information should not be replicated in the store and required to be consistent "

Re: [Xen-devel] [PATCH 1/2 linux-next] Revert "ufs: fix deadlocks introduced by sb mutex merge"

> On 05 June 2015 at 20:50 Al Viro wrote: > > > On Fri, Jun 05, 2015 at 06:27:01PM +0200, Fabian Frederick wrote: > > > You're asking to remove lock_ufs() in allocation and replace it by > > truncate_mutex. I guess you're talking about doing that on current rc > > (without s_lock restored). > >

Re: [Xen-devel] [PATCH 1/2 linux-next] Revert "ufs: fix deadlocks introduced by sb mutex merge"

> On 04 June 2015 at 07:01 Al Viro wrote: > > > On Wed, May 27, 2015 at 02:57:35PM -0700, Andrew Morton wrote: > > On Wed, 27 May 2015 21:15:30 +0200 Fabian Frederick wrote: > > > > > This reverts commit 9ef7db7f38d0 > > > ("ufs: fix deadlocks introduced by sb mutex merge") > > > That patch tri

Re: [Xen-devel] [PATCH 2/5] xen/vm_access: Support for memory-content hiding

>>> On 08.06.15 at 12:02, wrote: > On 05/08/2015 07:07 PM, Jan Beulich wrote: >>> > --- a/xen/include/asm-x86/domain.h >>> > +++ b/xen/include/asm-x86/domain.h >>> > @@ -512,6 +513,7 @@ struct arch_vcpu >>> > uint32_t emulate_flags; >>> > unsigned long gpa; >>> > unsigne

Re: [Xen-devel] [Formal Vote] Changes to Xen Project Security Vulnerability Process - Open until June 8th, 2015

>>> On 08.06.15 at 12:08, wrote: > Any more votes from committers? I'm neither against the change nor too much in favor, and I didn't think explicitly replying with "0" would help much. If it does, here you are: 0 Jan ___ Xen-devel mailing list Xen

Re: [Xen-devel] [PATCH v2 4/5] libxl: change xs path for pv qemu

On Thu, Jun 04, 2015 at 12:28:18PM +0100, Stefano Stabellini wrote: > If QEMU is ran just to provide PV backends, change the xenstore path to > /local/domain/0/device-model/$DOMID/pv. > > Add a parameter to libxl__device_model_xs_path to distinguish the device > model from the pv backends provider

Re: [Xen-devel] [OSSTEST Nested PATCH v11 4/7] Changes on test step of Debian hvm guest install

On Tue, 2015-05-26 at 17:08 +0800, longtao.pang wrote: > 1. The default disk size for guest is '1M' which is not sufficient > for nested HVM guest, using larger disk size for nested guest > to accommodate to nested test requirement, the specific disk_size is > defined by make-flight. > 2. In L1

Re: [Xen-devel] [PATCH] Osstest: stop testing SEDF, start testing RTDS

On Fri, 2015-05-22 at 11:55 +0200, Dario Faggioli wrote: > the SEDF scheduler is about to be deprecated and go > away (see [1]). OTOH, the RTDS scheduler is here to > stay. > > It therefore makes sense to stop smoke testing the > former in favour of the latter. Note that the > -sedf-pin jobs where

Re: [Xen-devel] [PATCH] osstest: reduce FreeBSD install timeouts

On Fri, 2015-05-29 at 11:38 +0100, Roger Pau Monne wrote: > Only the first block is expected to take longer (because it decompresses > the image and writes it to a LVM volume), the remaining commands should > execute much faster, so reduce the timeout. > > Signed-off-by: Roger Pau Monné > Cc: Ian

Re: [Xen-devel] [PATCH v2 4/5] libxl: change xs path for pv qemu

On 08/06/15 11:25, Wei Liu wrote: > On Thu, Jun 04, 2015 at 12:28:18PM +0100, Stefano Stabellini wrote: >> If QEMU is ran just to provide PV backends, change the xenstore path to >> /local/domain/0/device-model/$DOMID/pv. >> >> Add a parameter to libxl__device_model_xs_path to distinguish the devic

Re: [Xen-devel] Backport request "libxl: In libxl_set_vcpuonline check for maximum number of VCPUs against the cpumap." (Was: Re: [Bug report] Security issue in "xl vcpu-set")

Luwei Cheng writes ("Re: Backport request "libxl: In libxl_set_vcpuonline check for maximum number of VCPUs against the cpumap." (Was: Re: [Bug report] Security issue in "xl vcpu-set")"): > Some third-part management tools might be built directly above xl. > Perhaps they can not rely on "Ctrl-C".

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

>>> On 08.06.15 at 11:30, wrote: > On Mon, Jun 08, 2015 at 08:42:57AM +0100, Jan Beulich wrote: >> Otoh the respective root port also has >> - Received Master Abort set in its Secondary Status register (but >> that's also already the case in the log that we have before the UR >> occurs, i.e. t

Re: [Xen-devel] [PATCH v6 COLO 04/15] libxc/restore: support COLO restore

On 08/06/15 04:45, Yang Hongyang wrote: > call the callbacks resume/checkpoint/suspend while secondary vm > status is consistent with primary. > > Signed-off-by: Yang Hongyang > Signed-off-by: Wen Congyang > CC: Andrew Cooper > --- > tools/libxc/xc_sr_common.h | 11 +-- > tools/lib

Re: [Xen-devel] [Formal Vote] Changes to Xen Project Security Vulnerability Process - Open until June 8th, 2015

Ian Campbell writes ("Re: [Formal Vote] Changes to Xen Project Security Vulnerability Process - Open until June 8th, 2015"): > On Mon, 2015-06-01 at 10:36 +0100, Lars Kurth wrote: > > In the event that we do not have a patch available two working weeks > > before the disclosure date, we aim to sen

Re: [Xen-devel] [PATCH OSSTEST] Stubdom test case

On Mon, 2015-06-01 at 16:21 +0100, Wei Liu wrote: > Currently only QEMU traditional supports stubdom, so we only create > > test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64 > test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm > > Note that stubdom only supports serial='pty'. Piping serial

Re: [Xen-devel] Backport request "libxl: In libxl_set_vcpuonline check for maximum number of VCPUs against the cpumap." (Was: Re: [Bug report] Security issue in "xl vcpu-set")

On Mon, 2015-06-08 at 11:35 +0100, Ian Jackson wrote: > Luwei Cheng writes ("Re: Backport request "libxl: In libxl_set_vcpuonline > check for maximum number of VCPUs against the cpumap." (Was: Re: [Bug report] > Security issue in "xl vcpu-set")"): > > Some third-part management tools might be bui

[Xen-devel] [linux-3.4 test] 58137: regressions - FAIL

flight 58137 linux-3.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/58137/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 debian-install fail REGR. vs. 52209-bisect test-amd64-amd64-pair

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

>>> On 08.06.15 at 11:36, wrote: > On Mon, Jun 08, 2015 at 10:03:18AM +0100, Jan Beulich wrote: >> >>> On 08.06.15 at 10:09, wrote: >> > I believe the correct behaviour is happening but a PCIE completion timeout >> > is occurring instead of a >> > unsupported request. >> >> Might it be that wit

[Xen-devel] Analysis of PV(H) build times

Hello, I've done a small analysis of PV and PVH build and launch times using both xl and a custom builder [1] based on init-xenstore-domain. The purpose of this analysis is to measure the build time of PV(H) guests. In order to do this rdtsc calls have been added to the start of the main xl funct

[Xen-devel] Clarifying the state of ARINC653 scheduler (and other components) in Xen 4.5 and beyond

Hi, I wanted to point out that there is some discrepancy on the supported state of the ARINC653 scheduler * http://wiki.xenproject.org/wiki/Xen_Project_Release_Features not listed at all * http://wiki.xenproject.org/wiki/Xen_Project_

[Xen-devel] 答复： Re: [PATCH V3 3/6] libxl: add pvusb API

>>> 在 2:16 的 2015/5/20 上，在讯息 中，George Dunlap 写入： > On Sun, Apr 19, 2015 at 4:50 AM, Chunyan Liu wrote: > > +int libxl_device_usb_getinfo(libxl_ctx *ctx, char *busid, libxl_usbinfo > *usbinfo) > > +{ > > Sorry, missed something. This function is wrong. It gives you > information about a *ho

Re: [Xen-devel] [PATCH] libxl: refactor toolstack save restore code

On Fri, Jun 5, 2015 at 7:15 PM, Wei Liu wrote: > On Fri, Jun 05, 2015 at 06:46:35PM +0100, Andrew Cooper wrote: >> On 05/06/15 18:01, Wei Liu wrote: >> > This patch does following things: >> > 1. Document v1 format. >> > 2. Factor out function to handle QEMU restore data and function to >> >ha

[Xen-devel] xen-unstable build fails with XEN_DUMP_DIR undeclader in xl_cmdimpl.c

I saw that config/Paths.mk contains: XEN_DUMP_DIR := /var/lib/xen/dump But build fails with: xl_cmdimpl.c: In function âhandle_domain_deathâ: xl_cmdimpl.c:2330:33: error: âXEN_DUMP_DIRâ undeclared (first use in this function) xl_cmdimpl.c:2330:33: note: each undeclared identifier is

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

On Mon, Jun 08, 2015 at 11:55:22AM +0100, Jan Beulich wrote: > >>> On 08.06.15 at 11:36, wrote: > > On Mon, Jun 08, 2015 at 10:03:18AM +0100, Jan Beulich wrote: > >> >>> On 08.06.15 at 10:09, wrote: > >> > I believe the correct behaviour is happening but a PCIE completion > >> > timeout > >> >

Re: [Xen-devel] xen-unstable build fails with XEN_DUMP_DIR undeclader in xl_cmdimpl.c

On Mon, Jun 08, 2015 at 01:25:05PM +0200, Fabio Fantoni wrote: > I saw that config/Paths.mk contains: > XEN_DUMP_DIR := /var/lib/xen/dump > > But build fails with: > >xl_cmdimpl.c: In function âhandle_domain_deathâ: > >xl_cmdimpl.c:2330:33: error: âXEN_DUMP_DIRâ undeclared (first use i

Re: [Xen-devel] [PATCH] xen/pass-through: ROM BAR handling adjustments

On Mon, 8 Jun 2015, Jan Beulich wrote: > >>> On 05.06.15 at 18:41, wrote: > > On Fri, 5 Jun 2015, Jan Beulich wrote: > >> >>> On 05.06.15 at 13:32, wrote: > >> >> --- a/hw/xen/xen_pt.c > >> >> +++ b/hw/xen/xen_pt.c > >> >> @@ -248,7 +248,9 @@ static void xen_pt_pci_write_config(PCID > >> >> > >

Re: [Xen-devel] QEMU bumping memory bug analysis

On Fri, 5 Jun 2015, Wei Liu wrote: > On Fri, Jun 05, 2015 at 06:10:17PM +0100, Stefano Stabellini wrote: > > On Fri, 5 Jun 2015, Wei Liu wrote: > > > Hi all > > > > > > This bug is now considered a blocker for 4.6 release. > > > > > > The premises of the problem remain the same (George's translat

Re: [Xen-devel] QEMU bumping memory bug analysis

On Fri, 5 Jun 2015, Ian Campbell wrote: > On Fri, 2015-06-05 at 18:10 +0100, Stefano Stabellini wrote: > > On Fri, 5 Jun 2015, Wei Liu wrote: > > > Hi all > > > > > > This bug is now considered a blocker for 4.6 release. > > > > > > The premises of the problem remain the same (George's translated

Re: [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register

>>> On 08.06.15 at 13:28, wrote: > On Mon, Jun 08, 2015 at 11:55:22AM +0100, Jan Beulich wrote: >> But you asking this made me look more closely at the >> memory ranges dumped out to the ITP log: The root port has >> >> 0x20: Memory Base = 0xca40 >> 0x22: Memory Limit = 0

[Xen-devel] [PATCH] Modified RTDS scheduler to use an event-driven model instead of polling.

To do this, we create a new list that holds, for each vcpu, the time least into the future that it may need to be rescheduled. The scheduler chooses the lowest time off of this list and waits until the specified time instead of running every 1 ms as it did before. Signed-off-by: Dagaen Golomb Sig

Re: [Xen-devel] [qemu-mainline test] 57925: regressions - FAIL

On Mon, 8 Jun 2015, Fabio Fantoni wrote: > Il 08/06/2015 11:16, Ian Campbell ha scritto: > > On Sun, 2015-06-07 at 11:28 +, osstest service user wrote: > > > flight 57925 qemu-mainline real [real] > > > http://logs.test-lab.xenproject.org/osstest/logs/57925/ > > > > > > Regressions :-( > > > >

[Xen-devel] How to debug when vcpu state become to "Paused"

Hi, all: My HVM DomU become to "Hanging" after I modified driver in GuestOS. The "xl vcpu-list" shows that one of the vcpus of DomU has become to "Paused" state. I am wondering how can I debug this type of problem? I have tried tools/commands including ”xl debug-keys", "xen-hvmctx", et

Re: [Xen-devel] Clarifying the state of ARINC653 scheduler (and other components) in Xen 4.5 and beyond

>>> On 08.06.15 at 12:43, wrote: > b) Do we actually have or should have a definition of > experimental/preview/supported/deprecated. I don't think this was ever > written down and was defined before I joined. Also, there are no real > conventions related to changing the state. > > c) How doe

[Xen-devel] [Patch V4 05/16] xen: move static e820 map to global scope

Instead of using a function local static e820 map in xen_memory_setup() and calling various functions in the same source with the map as a parameter use a map directly accessible by all functions in the source. Signed-off-by: Juergen Gross Reviewed-by: David Vrabel --- arch/x86/xen/setup.c | 96

[Xen-devel] [Patch V4 16/16] xen: remove no longer needed p2m.h

Cleanup by removing arch/x86/xen/p2m.h as it isn't needed any more. Most definitions in this file are used in p2m.c only. Move those into p2m.c. set_phys_range_identity() is already declared in arch/x86/include/asm/xen/page.h, add __init annotation there. MAX_REMAP_RANGES isn't used at all, just

[Xen-devel] [Patch V4 04/16] xen: eliminate scalability issues from initial mapping setup

Direct Xen to place the initial P->M table outside of the initial mapping, as otherwise the 1G (implementation) / 2G (theoretical) restriction on the size of the initial mapping limits the amount of memory a domain can be handed initially. As the initial P->M table is copied rather early during bo

[Xen-devel] [Patch V4 08/16] xen: find unused contiguous memory area

For being able to relocate pre-allocated data areas like initrd or p2m list it is mandatory to find a contiguous memory area which is not yet in use and doesn't conflict with the memory map we want to be in effect. In case such an area is found reserve it at once as this will be required to be don

[Xen-devel] [Patch V4 06/16] xen: split counting of extra memory pages from remapping

Memory pages in the initial memory setup done by the Xen hypervisor conflicting with the target E820 map are remapped. In order to do this those pages are counted and remapped in xen_set_identity_and_remap(). Split the counting from the remapping operation to be able to setup the needed memory siz

[Xen-devel] [Patch V4 12/16] mm: provide early_memremap_ro to establish read-only mapping

During early boot as Xen pv domain the kernel needs to map some page tables supplied by the hypervisor read only. This is needed to be able to relocate some data structures conflicting with the physical memory map especially on systems with huge RAM (above 512GB). Provide the function early_memrem

[Xen-devel] [Patch V4 11/16] xen: check for initrd conflicting with e820 map

Check whether the initrd is placed at a location which is conflicting with the target E820 map. If this is the case relocate it to a new area unused up to now and compliant to the E820 map. Signed-off-by: Juergen Gross Reviewed-by: David Vrabel --- arch/x86/xen/setup.c | 51

[Xen-devel] [Patch V4 01/16] xen: sync with xen headers

Use the newest headers from the xen tree to get some new structure layouts. Signed-off-by: Juergen Gross Reviewed-by: David Vrabel --- arch/x86/include/asm/xen/interface.h | 96 include/xen/interface/xen.h | 10 ++-- 2 files changed, 93 insertions(+

[Xen-devel] [Patch V4 15/16] xen: allow more than 512 GB of RAM for 64 bit pv-domains

64 bit pv-domains under Xen are limited to 512 GB of RAM today. The main reason has been the 3 level p2m tree, which was replaced by the virtual mapped linear p2m list. Parallel to the p2m list which is being used by the kernel itself there is a 3 level mfn tree for usage by the Xen tools and event

[Xen-devel] [Patch V4 14/16] xen: move p2m list if conflicting with e820 map

Check whether the hypervisor supplied p2m list is placed at a location which is conflicting with the target E820 map. If this is the case relocate it to a new area unused up to now and compliant to the E820 map. As the p2m list might by huge (up to several GB) and is required to be mapped virtuall

[Xen-devel] [Patch V4 13/16] xen: add explicit memblock_reserve() calls for special pages

Some special pages containing interfaces to xen are being reserved implicitly only today. The memblock_reserve() call to reserve them is meant to reserve the p2m list supplied by xen. It is just reserving not only the p2m list itself, but some more pages up to the start of the xen built page tables

[Xen-devel] [Patch V4 02/16] xen: save linear p2m list address in shared info structure

The virtual address of the linear p2m list should be stored in the shared info structure read by the Xen tools to be able to support 64 bit pv-domains larger than 512 GB. Additionally the linear p2m list interface includes a generation count which is changed prior to and after each mapping change o

[Xen-devel] [Patch V4 00/16] xen: support pv-domains larger than 512GB

Support 64 bit pv-domains with more than 512GB of memory. Tested with 64 bit dom0 on machines with 8GB and 1TB and 32 bit dom0 on a 8GB machine. Conflicts between E820 map and different hypervisor populated memory areas have been tested via a fake E820 map reserved area on the 8GB machine. Change

[Xen-devel] [Patch V4 03/16] xen: don't build mfn tree if tools don't need it

In case the Xen tools indicate they don't need the p2m 3 level tree as they support the virtual mapped linear p2m list, just omit building the tree. Signed-off-by: Juergen Gross Reviewed-by: David Vrabel --- arch/x86/xen/p2m.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) di

[Xen-devel] [Patch V4 10/16] xen: check pre-allocated page tables for conflict with memory map

Check whether the page tables built by the domain builder are at memory addresses which are in conflict with the target memory map. If this is the case just panic instead of running into problems later. Signed-off-by: Juergen Gross --- arch/x86/xen/mmu.c | 19 --- arch/x86/xe

[Xen-devel] [Patch V4 07/16] xen: check memory area against e820 map

Provide a service routine to check a physical memory area against the E820 map. The routine will return false if the complete area is RAM according to the E820 map and true otherwise. Signed-off-by: Juergen Gross Reviewed-by: David Vrabel --- arch/x86/xen/setup.c | 23 +++

[Xen-devel] [Patch V4 09/16] xen: check for kernel memory conflicting with memory layout

Checks whether the pre-allocated memory of the loaded kernel is in conflict with the target memory map. If this is the case, just panic instead of run into problems later, as there is nothing we can do to repair this situation. Signed-off-by: Juergen Gross Reviewed-by: David Vrabel --- arch/x86

Re: [Xen-devel] [PATCH 5/5] x86/boot: Move/copy sections more efficiently

>>> On 05.06.15 at 15:31, wrote: > Both the trampoline copy and BSS initialise can be performed more efficiently > by using 4-byte varients of the string operations. On second thought I'm actually not convinced of this: With X86_FEATURE_ERMS using byte MOVS/STOS is supposedly preferred. > --- a/

Re: [Xen-devel] QEMU bumping memory bug analysis

On Mon, 2015-06-08 at 12:40 +0100, Stefano Stabellini wrote: > > > I disagree that libxl should be the arbitrator of a property that is > > > stored, maintained and enforced by Xen. Xen should be the arbitrator. > > > > That's not what "arbitrator" means, an arbitrator decides what the value > >

  1   2   3   >