[Xen-devel] [rumpuserxen test] 59131: regressions - FAIL

flight 59131 rumpuserxen real [real] http://logs.test-lab.xenproject.org/osstest/logs/59131/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866 build-i386-rumpuserxe

[Xen-devel] Coding style (was Re: [PATCH v3 05/13] x86/altp2m: basic data structures and support routines.)

>>> On 06.07.15 at 18:50, wrote: > Ed White writes ("Re: [PATCH v3 05/13] x86/altp2m: basic data structures and > support routines."): > ... >> In every case, this is because I wrote the code to conform with the style >> of the surrounding code. I'll fix them all, but I think the maintainers >> n

Re: [Xen-devel] [v4][PATCH 04/19] xen/passthrough: extend hypercall to support rdm reservation policy

Just please go to review the new revision directly. Thanks Tiejun On 2015/7/6 22:55, Chen, Tiejun wrote: * for dt devices: - Ignore this flag entirely But we still a flag to assign_device() like this, diff --git a/xen/drivers/passthrough/device_tree.c b/xen/drivers/passthrough/device_tree.

Re: [Xen-devel] [v4][PATCH 04/19] xen/passthrough: extend hypercall to support rdm reservation policy

Just please go to review the new revision directly. Thanks Tiejun On 2015/7/6 22:52, Chen, Tiejun wrote: Any comment to this? Thanks Tiejun On 2015/7/2 16:49, Chen, Tiejun wrote: @@ -1898,7 +1899,13 @@ static int intel_iommu_add_device(u8 devfn, struct pci_dev *pdev) PCI_BUS(b

Re: [Xen-devel] [PATCH v3 05/13] x86/altp2m: basic data structures and support routines.

>>> On 06.07.15 at 18:40, wrote: > On 07/03/2015 09:22 AM, Andrew Cooper wrote: >> On 01/07/15 19:09, Ed White wrote: >>> Add the basic data structures needed to support alternate p2m's and >>> the functions to initialise them and tear them down. >>> >>> Although Intel hardware can handle 512 EPTP

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On 07/07/2015 09:20 AM, Jan Beulich wrote: On 06.07.15 at 19:03, wrote: >> I don't mind just having the comment for now, so for what it's worth I >> stand by my ack. >> >> Having said that (and with the understading that it is beyond the scope >> of this patch), a way to validate things like

[Xen-devel] [v5][PATCH 10/16] tools: introduce some new parameters to set rdm policy

This patch introduces user configurable parameters to specify RDM resource and according policies, Global RDM parameter: rdm = "type=none/host,reserve=strict/relaxed" Per-device RDM parameter: pci = [ 'sbdf, rdm_reserve=strict/relaxed' ] Global RDM parameter, "type", allows user to specif

[Xen-devel] [v5][PATCH 15/16] xen/vtd: prevent from assign the device with shared rmrr

Currently we're intending to cover this kind of devices with shared RMRR simply since the case of shared RMRR is a rare case according to our previous experiences. But late we can group these devices which shared rmrr, and then allow all devices within a group to be assigned to same domain. CC: Ya

[Xen-devel] [v5][PATCH 00/16] Fix RMRR

v5: * Fold our original patch #2 and #3 as this new, and here introduce a new, clear_identity_p2m_entry, which can wrapper guest_physmap_remove_page(). And we use this to clean our identity mapping. * Just leave one bit XEN_DOMCTL_DEV_RDM_RELAXED as our policy flag, so now "0" means "str

[Xen-devel] [v5][PATCH 14/16] xen/vtd: enable USB device assignment

USB RMRR may conflict with guest BIOS region. In such case, identity mapping setup is simply skipped in previous implementation. Now we can handle this scenario cleanly with new policy mechanism so previous hack code can be removed now. CC: Yang Zhang CC: Kevin Tian Signed-off-by: Tiejun Chen A

[Xen-devel] [v5][PATCH 08/16] tools/libxc: Expose new hypercall xc_reserved_device_memory_map

We will introduce the hypercall xc_reserved_device_memory_map approach to libxc. This helps us get rdm entry info according to different parameters. If flag == PCI_DEV_RDM_ALL, all entries should be exposed. Or we just expose that rdm entry specific to a SBDF. CC: Ian Jackson CC: Stefano Stabelli

[Xen-devel] [v5][PATCH 09/16] tools: extend xc_assign_device() to support rdm reservation policy

This patch passes rdm reservation policy to xc_assign_device() so the policy is checked when assigning devices to a VM. Note this also bring some fallout to python usage of xc_assign_device(). CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu CC: David Scott Acked-by: Wei L

[Xen-devel] [v5][PATCH 04/16] xen: enable XENMEM_memory_map in hvm

This patch enables XENMEM_memory_map in hvm. So hvmloader can use it to setup the e820 mappings. CC: Keir Fraser CC: Jan Beulich CC: Andrew Cooper Signed-off-by: Tiejun Chen Reviewed-by: Tim Deegan Reviewed-by: Kevin Tian Acked-by: Jan Beulich Acked-by: George Dunlap --- v5: * Nothing is

[Xen-devel] [v5][PATCH 16/16] tools: parse to enable new rdm policy parameters

This patch parses to enable user configurable parameters to specify RDM resource and according policies, Global RDM parameter: rdm = "type=none/host,reserve=strict/relaxed" Per-device RDM parameter: pci = [ 'sbdf, rdm_reserve=strict/relaxed' ] Default per-device RDM policy is 'strict', wh

[Xen-devel] [v5][PATCH 02/16] xen/vtd: create RMRR mapping

RMRR reserved regions must be setup in the pfn space with an identity mapping to reported mfn. However existing code has problem to setup correct mapping when VT-d shares EPT page table, so lead to problem when assigning devices (e.g GPU) with RMRR reported. So instead, this patch aims to setup ide

[Xen-devel] [v5][PATCH 12/16] tools: introduce a new parameter to set a predefined rdm boundary

Previously we always fix that predefined boundary as 2G to handle conflict between memory and rdm, but now this predefined boundar can be changes with the parameter "rdm_mem_boundary" in .cfg file. CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu Signed-off-by: Tiejun Chen

[Xen-devel] [v5][PATCH 01/16] xen: introduce XENMEM_reserved_device_memory_map

From: Jan Beulich This is a prerequisite for punching holes into HVM and PVH guests' P2M to allow passing through devices that are associated with (on VT-d) RMRRs. CC: Jan Beulich CC: Yang Zhang CC: Kevin Tian Signed-off-by: Jan Beulich Signed-off-by: Tiejun Chen Acked-by: Kevin Tian --- v

[Xen-devel] [v5][PATCH 07/16] hvmloader/e820: construct guest e820 table

Now we can use that memory map to build our final e820 table but it may need to reorder all e820 entries. CC: Keir Fraser CC: Jan Beulich CC: Andrew Cooper CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu Signed-off-by: Tiejun Chen --- v5: * Nothing is changed. v4: *

[Xen-devel] [v5][PATCH 05/16] hvmloader: get guest memory map into memory_map[]

Now we get this map layout by call XENMEM_memory_map then save them into one global variable memory_map[]. It should include lowmem range, rdm range and highmem range. Note rdm range and highmem range may not exist in some cases. And here we need to check if any reserved memory conflicts with [RES

[Xen-devel] [v5][PATCH 11/16] tools/libxl: detect and avoid conflicts with RDM

While building a VM, HVM domain builder provides struct hvm_info_table{} to help hvmloader. Currently it includes two fields to construct guest e820 table by hvmloader, low_mem_pgend and high_mem_pgend. So we should check them to fix any conflict with RDM. RMRR can reside in address space beyond 4

[Xen-devel] [v5][PATCH 03/16] xen/passthrough: extend hypercall to support rdm reservation policy

This patch extends the existing hypercall to support rdm reservation policy. We return error or just throw out a warning message depending on whether the policy is "strict" or "relaxed" when reserving RDM regions in pfn space. Note in some special cases, e.g. add a device to hwdomain, and remove a

[Xen-devel] [v5][PATCH 13/16] libxl: construct e820 map with RDM information for HVM guest

Here we'll construct a basic guest e820 table via XENMEM_set_memory_map. This table includes lowmem, highmem and RDMs if they exist, and hvmloader would need this info later. Note this guest e820 table would be same as before if the platform has no any RDM or we disable RDM (by default). CC: Ian

[Xen-devel] [v5][PATCH 06/16] hvmloader/pci: skip reserved ranges

When allocating mmio address for PCI bars, we need to make sure they don't overlap with reserved regions. CC: Keir Fraser CC: Jan Beulich CC: Andrew Cooper CC: Ian Jackson CC: Stefano Stabellini CC: Ian Campbell CC: Wei Liu Signed-off-by: Tiejun Chen --- v5: * Rename that field, is_64bar,

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

>>> On 06.07.15 at 19:03, wrote: > I don't mind just having the comment for now, so for what it's worth I > stand by my ack. > > Having said that (and with the understading that it is beyond the scope > of this patch), a way to validate things like these is a good idea. I > wonder if, in a future

[Xen-devel] [linux-next test] 59099: regressions - FAIL

flight 59099 linux-next real [real] http://logs.test-lab.xenproject.org/osstest/logs/59099/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail REGR. vs. 59036 Regre

Re: [Xen-devel] [PATCH] x86/monitor: add get_capabilities to monitor_op domctl

On 07/07/2015 03:43 AM, Tamas K Lengyel wrote: > Add option to monitor_op domctl to determine the monitor capabilities of the > system. > > Signed-off-by: Tamas K Lengyel > --- > tools/libxc/include/xenctrl.h | 6 ++ > tools/libxc/xc_monitor.c | 21 + > xen/arch/x86

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

[I agree with most of Dario's comment and only reply on the comments that I didn't quite understand/agree.] >> > @@ -411,15 +422,77 @@ __runq_insert(const struct scheduler *ops, struct >> > rt_vcpu *svc) >> > struct rt_vcpu * iter_svc = __q_elem(iter); >> > if ( svc->cur

Re: [Xen-devel] [RFC PATCH v3 17/18] xen/arm: ITS: Generate ITS node for Dom0

On Mon, Jun 29, 2015 at 6:36 PM, Ian Campbell wrote: > On Mon, 2015-06-22 at 17:31 +0530, vijay.kil...@gmail.com wrote: >> >> +int its_make_dt_node(const struct domain *d, >> + const struct dt_device_node *node, void *fdt) >> +{ >> +struct its_node *its; >> +const stru

[Xen-devel] [PATCH 2/6] xen/x86: Remove unnecessary memset() call

Since ctxt is kzalloc'd there is no need to call a memset for ctxt->fpu_ctxt. Signed-off-by: Boris Ostrovsky --- arch/x86/xen/smp.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c index ca7ee1f..7cf0765 100644 --- a/arch/x86/xen/smp.c +++ b/arch/x86/xen

[Xen-devel] [PATCH 0/6] 32-bit PVH domU support

A set of PVH-related patches. The first patch is x86-64 ABI fix for PVH guests. The second is a small update that removes redundant memset (both on PV and PVH code paths) The rest is to enable non-privileged 32-bit PVH guests. This requires hypervisor patches from http://lists.xenproject.org/arc

[Xen-devel] [PATCH 6/6] xen/x86/pvh: Allow building 32-bit PVH guests

Signed-off-by: Boris Ostrovsky --- arch/x86/xen/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig index e88fda8..891031e 100644 --- a/arch/x86/xen/Kconfig +++ b/arch/x86/xen/Kconfig @@ -48,5 +48,5 @@ config XEN_DEBUG_FS conf

[Xen-devel] [PATCH 3/6] xen/x86/pvh: Properly set page tables for 32-bit PVH guests

32-bit PVH guests don't want to write-protect/pin page tables. Signed-off-by: Boris Ostrovsky --- arch/x86/xen/mmu.c | 22 +- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/arch/x86/xen/mmu.c b/arch/x86/xen/mmu.c index dd151b2..b473df8 100644 --- a/arch/x86/xe

[Xen-devel] [PATCH 4/6] xen/x86/pvh: Set up descriptors for 32-bit PVH guests

Signed-off-by: Boris Ostrovsky --- arch/x86/xen/enlighten.c | 16 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 0b95c9b..7953e68 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -136

[Xen-devel] [PATCH 5/6] xen/x86/pvh: Add 32-bit PVH initialization code

Signed-off-by: Boris Ostrovsky --- arch/x86/xen/enlighten.c | 4 arch/x86/xen/smp.c | 17 ++--- arch/x86/xen/xen-head.S | 17 +++-- 3 files changed, 25 insertions(+), 13 deletions(-) diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 7953e

[Xen-devel] [PATCH 1/6] xen/x86/pvh: Save %rbx in xen_pvh_early_cpu_init()

x86-64 ABI requires that functions preserve %rbx. When xen_pvh_early_cpu_init() is executed on boot cpu it is invoked as a function and 'cpuid' instruction will clobber %rbx. (This is not a concern on secondary processors since there xen_pvh_early_cpu_init() is the entry point and thus does not nee

Re: [Xen-devel] [Intel-gfx] [Announcement] 2015-Q2 release of XenGT - a Mediated Graphics Passthrough Solution from Intel

Hi all, We're pleased to announce a public update to Intel Graphics Virtualization Technology(Intel GVT-g, formerly known as XenGT). Intel GVT-g is a full GPU virtualization solution with mediated pass-through, starting from 4th generation Intel Core(TM) processors with Intel Graphics process

Re: [Xen-devel] [PATCH 0/6] add xsaves/xrstors support

OK，I will add thest.Thanks. -Original Message- From: Andrew Cooper [mailto:andrew.coop...@citrix.com] Sent: Thursday, July 2, 2015 10:09 PM To: Ruan, Shuai; xen-devel@lists.xen.org Cc: ian.jack...@eu.citrix.com; ian.campb...@citrix.com; stefano.stabell...@eu.citrix.com; wei.l...@citrix.c

Re: [Xen-devel] [PATCH V5 3/7] libxl: add pvusb API

Any comments on the implementation? If there is anything improper, I can update. Thanks, Chunyan >>> On 6/25/2015 at 06:07 PM, in message <1435226838-3067-4-git-send-email-cy...@suse.com>, Chunyan Liu wrote: > Add pvusb APIs, including: > - attach/detach (create/destroy) virtual usb controlle

[Xen-devel] [PATCH] x86/monitor: add get_capabilities to monitor_op domctl

Add option to monitor_op domctl to determine the monitor capabilities of the system. Signed-off-by: Tamas K Lengyel --- tools/libxc/include/xenctrl.h | 6 ++ tools/libxc/xc_monitor.c | 21 + xen/arch/x86/hvm/hvm.c| 5 + xen/arch/x86/monitor.c| 2

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

flight 59086 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/59086/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 11 guest-start fail REGR. vs. 58981 test-amd64-i386-libvirt 1

[Xen-devel] [PATCH]xen new latest version mp_register_lapic can't register disabled CPU, patch attempt to fix

Hi all, I have found a minor problem in Xen 4.6 unstable When xen booted up and parsed all cpus by acpi_parse_x2apic, if the number of "Processor Local x2APIC Structure"(struct acpi_madt_local_x2apic) parsed from acpi table bigger than the number of host cpu. for all extra acpi_madt_local_x2ap

Re: [Xen-devel] [PATCH v3 11/13] x86/altp2m: define and implement alternate p2m HVMOP types.

> I believe, unless Tamas says otherwise, that we agreed the > HVMOP's in question and their implementations are sufficiently > different that we should not merge them. I'm still not entirely convinced of this being the case but considering altp2m will be an experimental feature I'm not going to

Re: [Xen-devel] [PATCH] libxl: support dom0

On 07/06/2015 03:46 PM, Jim Fehlig wrote: In Xen, dom0 is really just another domain that supports ballooning, adding/removing devices, changing vcpu configuration, etc. This patch adds support to the libxl driver for managing dom0. Note that the legacy xend driver has long supported managing dom

Re: [Xen-devel] [PATCH v3 12/13] x86/altp2m: Add altp2mhvm HVM domain parameter.

On 07/06/2015 11:18 AM, Wei Liu wrote: > On Mon, Jul 06, 2015 at 11:01:27AM -0700, Ed White wrote: >> On 07/06/2015 10:49 AM, Wei Liu wrote: diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl index 23f27d4..66a89cf 100644 --- a/tools/libxl/libxl_types.idl +++

[Xen-devel] [ovmf test] 59082: tolerable FAIL - PUSHED

flight 59082 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/59082/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 59055 test-amd64-i386-xl-qemuu-win7-amd64 1

[Xen-devel] [PATCH] libxl: support dom0

In Xen, dom0 is really just another domain that supports ballooning, adding/removing devices, changing vcpu configuration, etc. This patch adds support to the libxl driver for managing dom0. Note that the legacy xend driver has long supported managing dom0. Operations that are not supported on dom

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

flight 59088 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/59088/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-libvirt-xsm 11 guest-start fail REGR. vs. 58842 test-armhf-armhf-libvirt

[Xen-devel] [RFC v3] xSplice design

Since RFC v2 [http://lists.xen.org/archives/html/xen-devel/2015-05/msg02142.html] - Ingested every review comment in. For those who prefer an diff of what changed between v2 and this I am attaching an diff to help easy reviewing. Please see inline the RFC v3 which in general: - Ditches the att

[Xen-devel] [linux-3.18 test] 59075: regressions - FAIL

flight 59075 linux-3.18 real [real] http://logs.test-lab.xenproject.org/osstest/logs/59075/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 58581 Tests which are failin

Re: [Xen-devel] [PATCH v3 07/13] VMX: add VMFUNC leaf 0 (EPTP switching) to emulator.

-Original Message- From: Andrew Cooper [mailto:andrew.coop...@citrix.com] Sent: Friday, July 03, 2015 9:40 AM To: White, Edmund H; xen-devel@lists.xen.org Cc: Ian Jackson; Jan Beulich; Tim Deegan; Daniel De Graaf; Sahita, Ravi; Wei Liu; tleng...@novetta.com; George Dunlap Subject: Re: [

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

On Fri, Jun 12, 2015 at 12:09:24PM -0400, Konrad Rzeszutek Wilk wrote: > On Fri, Jun 12, 2015 at 04:31:12PM +0200, Martin Pohlack wrote: > > On 12.06.2015 16:03, Konrad Rzeszutek Wilk wrote: > > > On Fri, Jun 12, 2015 at 01:39:05PM +0200, Martin Pohlack wrote: > > >> On 15.05.2015 21:44, Konrad Rze

Re: [Xen-devel] [PATCH v2 07/12] x86/altp2m: add control of suppress_ve.

On 07/06/2015 11:29 AM, George Dunlap wrote: > On 07/06/2015 06:35 PM, Ed White wrote: >> On 07/06/2015 10:12 AM, George Dunlap wrote: >>> On Fri, Jun 26, 2015 at 5:27 PM, Ed White wrote: On 06/25/2015 11:04 PM, Jan Beulich wrote: On 25.06.15 at 18:36, wrote: >> On 06/25/2015 01

Re: [Xen-devel] [PATCH V3 1/3] xen/mem_access: Support for memory-content hiding

> > If you'd prefer that I do some ground work for the future (i.e. rename > MEM_ACCESS constants, etc.), please let me know. Yeap, that sounds reasonable to me. Thanks, Tamas ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-

Re: [Xen-devel] [PATCH v2 07/12] x86/altp2m: add control of suppress_ve.

On 07/06/2015 06:35 PM, Ed White wrote: > On 07/06/2015 10:12 AM, George Dunlap wrote: >> On Fri, Jun 26, 2015 at 5:27 PM, Ed White wrote: >>> On 06/25/2015 11:04 PM, Jan Beulich wrote: >>> On 25.06.15 at 18:36, wrote: > On 06/25/2015 01:12 AM, Jan Beulich wrote: > On 24.06.15 at

Re: [Xen-devel] [PATCH V3 1/3] xen/mem_access: Support for memory-content hiding

On 07/06/2015 07:50 PM, Lengyel, Tamas wrote: > Handy feature, thanks for doing it! You're very welcome, I'm quite happy you find it useful. > @@ -1466,6 +1466,10 @@ void p2m_mem_access_emulate_check(struct vcpu *v, > } > > v->arch.vm_event.emulate_flags = violation

Re: [Xen-devel] [PATCH v3 11/13] x86/altp2m: define and implement alternate p2m HVMOP types.

On 07/06/2015 10:08 AM, Ian Jackson wrote: > Ed White writes ("Re: [Xen-devel] [PATCH v3 11/13] x86/altp2m: define and > implement alternate p2m HVMOP types."): >> On 07/06/2015 03:09 AM, Andrew Cooper wrote: >>> I am still very much unconvinced by the argument against having a single >>> HVMOP_al

Re: [Xen-devel] [PATCH v3 12/13] x86/altp2m: Add altp2mhvm HVM domain parameter.

On Mon, Jul 06, 2015 at 11:01:27AM -0700, Ed White wrote: > On 07/06/2015 10:49 AM, Wei Liu wrote: > >> diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl > >> index 23f27d4..66a89cf 100644 > >> --- a/tools/libxl/libxl_types.idl > >> +++ b/tools/libxl/libxl_types.idl > >> @@ -43

Re: [Xen-devel] [ovmf test] 58956: regressions - FAIL

On Wed, Jul 01, 2015 at 09:55:27AM +0100, Ian Campbell wrote: > On Tue, 2015-06-30 at 17:53 +0100, Anthony PERARD wrote: > > On Mon, Jun 29, 2015 at 10:32:43AM +0100, Ian Campbell wrote: > > > On Sun, 2015-06-28 at 22:32 +, osstest service user wrote: > > > > flight 58956 ovmf real [real] > > >

Re: [Xen-devel] [PATCH v3 12/13] x86/altp2m: Add altp2mhvm HVM domain parameter.

On 07/06/2015 10:49 AM, Wei Liu wrote: >> diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl >> index 23f27d4..66a89cf 100644 >> --- a/tools/libxl/libxl_types.idl >> +++ b/tools/libxl/libxl_types.idl >> @@ -437,6 +437,7 @@ libxl_domain_build_info = Struct("domain_build_info",[ >

Re: [Xen-devel] [PATCH V3 2/3] xen/vm_event: Support for guest-requested events

On Mon, Jul 06, 2015 at 06:51:12PM +0300, Razvan Cojocaru wrote: > Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST, > sent via HVMOP_request_vm_event. The guest can request that a > generic vm_event (containing only the vm_event-filled guest registers > as information) be sent t

Re: [Xen-devel] [PATCH v3 12/13] x86/altp2m: Add altp2mhvm HVM domain parameter.

On Wed, Jul 01, 2015 at 11:09:36AM -0700, Ed White wrote: > The altp2mhvm and nestedhvm parameters are mutually > exclusive and cannot be set together. > > Signed-off-by: Ed White > --- > docs/man/xl.cfg.pod.5 | 12 > tools/libxl/libxl_create.c | 1 + > tools/libxl/l

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On 06/07/15 18:36, Lengyel, Tamas wrote: > > > On Mon, Jul 6, 2015 at 1:29 PM, Razvan Cojocaru > mailto:rcojoc...@bitdefender.com>> wrote: > > On 07/06/2015 08:17 PM, Andrew Cooper wrote: > > On 06/07/15 18:08, Lengyel, Tamas wrote: > >> > >> Having said that (and with the under

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On 06/07/15 18:29, Razvan Cojocaru wrote: > On 07/06/2015 08:17 PM, Andrew Cooper wrote: >> On 06/07/15 18:08, Lengyel, Tamas wrote: >>> Having said that (and with the understading that it is beyond the >>> scope >>> of this patch), a way to validate things like these is a good idea. I

Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the SEDF scheduler

On Mon, 2015-07-06 at 17:26 +0100, Ian Jackson wrote: > George Dunlap writes ("Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the > SEDF scheduler"): > > On 07/06/2015 05:17 PM, Dario Faggioli wrote: > > I probably wouldn't even have bothered saying anything if I hadn't > > already been replyin

Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the SEDF scheduler

On Mon, 2015-07-06 at 17:22 +0100, George Dunlap wrote: > On 07/06/2015 05:17 PM, Dario Faggioli wrote: > > On Mon, 2015-07-06 at 16:40 +0100, George Dunlap wrote: > >> On 07/06/2015 04:30 PM, Dario Faggioli wrote: > >>> only the interface is left in place, for backward > >>> compile-time compatibi

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

On Sun, 2015-06-28 at 16:17 -0400, Dagaen Golomb wrote: > It does take some thinking as to whether this will occur or not. I > also am not sure > if Xen will let the timer handlers preempt each other and, if so, if > this is even a > problem. > I was about to tell you... But, really, if you want t

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

On Sun, 2015-06-28 at 13:45 -0700, Meng Xu wrote: > 2015-06-28 13:17 GMT-07:00 Dagaen Golomb : > > > The scenario in my mind that will potentially invoke one more rt_schedule > > > is: > > > VCPU j currently runs out of budget and will have top priority once it > > > get budget replenishment. >

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On Mon, Jul 6, 2015 at 1:29 PM, Razvan Cojocaru wrote: > On 07/06/2015 08:17 PM, Andrew Cooper wrote: > > On 06/07/15 18:08, Lengyel, Tamas wrote: > >> > >> Having said that (and with the understading that it is beyond the > >> scope > >> of this patch), a way to validate things like

Re: [Xen-devel] BUG: unable to handle kernel NULL pointer in __netdev_pick_tx()

On Mon, 2015-07-06 at 19:13 +0800, Bob Liu wrote: > > Thank you for the quick fix! > Tested by rebooting several times and didn't hit this panic any more. Thanks Bob, I will submit an official patch then ;) ___ Xen-devel mailing list Xen-devel@lists

Re: [Xen-devel] [PATCH v2 07/12] x86/altp2m: add control of suppress_ve.

On 07/06/2015 10:12 AM, George Dunlap wrote: > On Fri, Jun 26, 2015 at 5:27 PM, Ed White wrote: >> On 06/25/2015 11:04 PM, Jan Beulich wrote: >> On 25.06.15 at 18:36, wrote: On 06/25/2015 01:12 AM, Jan Beulich wrote: On 24.06.15 at 19:53, wrote: >> On 06/24/2015 07:38 AM, J

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On 07/06/2015 08:17 PM, Andrew Cooper wrote: > On 06/07/15 18:08, Lengyel, Tamas wrote: >> >> Having said that (and with the understading that it is beyond the >> scope >> of this patch), a way to validate things like these is a good idea. I >> wonder if, in a future patch, we could

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

On Sun, 2015-06-28 at 00:06 -0700, Meng Xu wrote: > [Adding Dario into the cc list...] > > Dario, this patch has some coding issues and some other minor issues. > I tried to point out some in this email. IMHO, the main purpose of > this patch is to confirm that the implementation fully reflects w

Re: [Xen-devel] [PATCH v3 03/13] VMX: implement suppress #VE.

On Wed, Jul 1, 2015 at 7:09 PM, Ed White wrote: > In preparation for selectively enabling #VE in a later patch, set > suppress #VE on all EPTE's. > > Suppress #VE should always be the default condition for two reasons: > it is generally not safe to deliver #VE into a guest unless that guest > has

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On 06/07/15 18:08, Lengyel, Tamas wrote: > > Having said that (and with the understading that it is beyond the > scope > of this patch), a way to validate things like these is a good idea. I > wonder if, in a future patch, we could not have ./configure detect > these > thing

Re: [Xen-devel] [v4][PATCH 11/19] tools: introduce some new parameters to set rdm policy

On Mon, Jul 06, 2015 at 10:46:06PM +0800, Chen, Tiejun wrote: > On 2015/7/6 22:34, Jan Beulich wrote: > On 06.07.15 at 16:29, wrote: > >>It sounds like part of the problem here is a matter of domains. > >> > >>Jan cares mostly about what happens in the hypervisor. At the > >>hypervisor level,

Re: [Xen-devel] [PATCH V3 3/3] xen/vm_event: Deny register writes if refused by vm_event reply

On 07/06/2015 08:05 PM, Lengyel, Tamas wrote: > @@ -410,6 +414,8 @@ void vm_event_resume(struct domain *d, struct > vm_event_domain *ved) > > > #ifdef HAS_MEM_ACCESS > case VM_EVENT_REASON_MEM_ACCESS: > +case VM_EVENT_REASON_MOV_TO_MSR: > +case VM_EVENT_R

Re: [Xen-devel] [PATCH v3 02/13] VMX: VMFUNC and #VE definitions and detection.

On Wed, Jul 1, 2015 at 7:09 PM, Ed White wrote: > Currently, neither is enabled globally but may be enabled on a per-VCPU > basis by the altp2m code. > > Remove the check for EPTE bit 63 == zero in ept_split_super_page(), as > that bit is now hardware-defined. > > Signed-off-by: Ed White > > Revi

Re: [Xen-devel] [PATCH v2 07/12] x86/altp2m: add control of suppress_ve.

On Fri, Jun 26, 2015 at 5:27 PM, Ed White wrote: > On 06/25/2015 11:04 PM, Jan Beulich wrote: > On 25.06.15 at 18:36, wrote: >>> On 06/25/2015 01:12 AM, Jan Beulich wrote: >>> On 24.06.15 at 19:53, wrote: > On 06/24/2015 07:38 AM, Jan Beulich wrote: > On 22.06.15 at 20:56, w

Re: [Xen-devel] [CALL-FOR-AGENDA] Monthly Xen.org Technical Call (2015-07-08)

- ian.campb...@citrix.com wrote: > On Fri, 2015-07-03 at 13:55 +0100, Ian Campbell wrote: > > On Thu, 2015-07-02 at 16:16 +0100, Ian Jackson wrote: > > > Ian Campbell writes ("Re: [Xen-devel] [CALL-FOR-AGENDA] Monthly > Xen.org Technical Call (2015-07-08)"): > > > > On Thu, 2015-07-02 at 09:4

Re: [Xen-devel] [PATCH v3 11/13] x86/altp2m: define and implement alternate p2m HVMOP types.

Ed White writes ("Re: [Xen-devel] [PATCH v3 11/13] x86/altp2m: define and implement alternate p2m HVMOP types."): > On 07/06/2015 03:09 AM, Andrew Cooper wrote: > > I am still very much unconvinced by the argument against having a single > > HVMOP_altp2m and a set of subops. do_domctl() and do_sy

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

> Having said that (and with the understading that it is beyond the scope > of this patch), a way to validate things like these is a good idea. I > wonder if, in a future patch, we could not have ./configure detect these > things and simply disable the relevant VM_EVENT_FLAG constants with > #if(n)

Re: [Xen-devel] [PATCH V3 3/3] xen/vm_event: Deny register writes if refused by vm_event reply

@@ -410,6 +414,8 @@ void vm_event_resume(struct domain *d, struct vm_event_domain *ved) > > #ifdef HAS_MEM_ACCESS > case VM_EVENT_REASON_MEM_ACCESS: > +case VM_EVENT_REASON_MOV_TO_MSR: > +case VM_EVENT_REASON_WRITE_CTRLREG: > This doesn't really make much sense to be ass

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On 07/06/2015 07:26 PM, Lengyel, Tamas wrote: > > > On Mon, Jul 6, 2015 at 11:54 AM, Jan Beulich > wrote: > > >>> On 06.07.15 at 17:35, > wrote: > > On Mon, Jul 6, 2015 at 11:26 AM, Jan Beulich >

Re: [Xen-devel] [PATCH V3 2/3] xen/vm_event: Support for guest-requested events

On Mon, Jul 6, 2015 at 11:51 AM, Razvan Cojocaru wrote: > Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST, > sent via HVMOP_request_vm_event. The guest can request that a > generic vm_event (containing only the vm_event-filled guest registers > as information) be sent to users

Re: [Xen-devel] [PATCH v3 05/13] x86/altp2m: basic data structures and support routines.

On 07/06/2015 02:56 AM, Jan Beulich wrote: On 03.07.15 at 18:22, wrote: >> On 01/07/15 19:09, Ed White wrote: >>> Add the basic data structures needed to support alternate p2m's and >>> the functions to initialise them and tear them down. >>> >>> Although Intel hardware can handle 512 EPTP's

Re: [Xen-devel] [PATCH v3 05/13] x86/altp2m: basic data structures and support routines.

Ed White writes ("Re: [PATCH v3 05/13] x86/altp2m: basic data structures and support routines."): ... > In every case, this is because I wrote the code to conform with the style > of the surrounding code. I'll fix them all, but I think the maintainers > need to be clear about which is more importa

Re: [Xen-devel] [PATCH V3 1/3] xen/mem_access: Support for memory-content hiding

Handy feature, thanks for doing it! @@ -1466,6 +1466,10 @@ void p2m_mem_access_emulate_check(struct vcpu *v, > } > > v->arch.vm_event.emulate_flags = violation ? rsp->flags : 0; > + > +if ( rsp->flags & MEM_ACCESS_SET_EMUL_READ_DATA && > So one of the use-cases for this

Re: [Xen-devel] [PATCH v3 11/13] x86/altp2m: define and implement alternate p2m HVMOP types.

On 07/06/2015 03:09 AM, Andrew Cooper wrote: > On 01/07/15 19:09, Ed White wrote: >> Signed-off-by: Ed White > > I am still very much unconvinced by the argument against having a single > HVMOP_altp2m and a set of subops. do_domctl() and do_sysctl() are > examples of a subop style hypercall with

Re: [Xen-devel] [PATCH OSSTEST v7 12/15] Add testing of non-LVM/phy disk backends.

On Mon, 2015-07-06 at 17:26 +0100, Ian Campbell wrote: > On Mon, 2015-07-06 at 17:01 +0100, Ian Jackson wrote: > > Ian Campbell writes ("Re: [PATCH OSSTEST v7 12/15] Add testing of > > non-LVM/phy disk backends."): > > > On Mon, 2015-07-06 at 16:21 +0100, Ian Jackson wrote: > > > > Are some of the

Re: [Xen-devel] [PATCH v3 05/13] x86/altp2m: basic data structures and support routines.

On 07/03/2015 09:22 AM, Andrew Cooper wrote: > On 01/07/15 19:09, Ed White wrote: >> Add the basic data structures needed to support alternate p2m's and >> the functions to initialise them and tear them down. >> >> Although Intel hardware can handle 512 EPTP's per hardware thread >> concurrently, o

Re: [Xen-devel] [PATCH v2] x86/vm_event: toggle singlestep from vm_event response

On Mon, Jul 6, 2015 at 11:54 AM, Jan Beulich wrote: > >>> On 06.07.15 at 17:35, wrote: > > On Mon, Jul 6, 2015 at 11:26 AM, Jan Beulich wrote: > > > >> >>> On 30.06.15 at 16:40, wrote: > >> > On Tue, Jun 30, 2015 at 10:18 AM, Andrew Cooper < > >> andrew.coop...@citrix.com> > >> > wrote: > >> >

Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the SEDF scheduler

George Dunlap writes ("Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the SEDF scheduler"): > On 07/06/2015 05:17 PM, Dario Faggioli wrote: > >>> Chenges from v2: > >>> - introduce and use ERROR_FEATURE_REMOVED, as requested > >>>during review; > >>> - mark the SEDF only parameter as depre

Re: [Xen-devel] [PATCH OSSTEST v7 12/15] Add testing of non-LVM/phy disk backends.

On Mon, 2015-07-06 at 17:01 +0100, Ian Jackson wrote: > Ian Campbell writes ("Re: [PATCH OSSTEST v7 12/15] Add testing of non-LVM/phy > disk backends."): > > On Mon, 2015-07-06 at 16:21 +0100, Ian Jackson wrote: > > > Are some of these jobs not very similar to existing ones ? > > > > They differ

Re: [Xen-devel] [PATCH OSSTEST v7 01/15] TestSupport: Add helper to fetch a URL on a host

On Mon, 2015-07-06 at 16:59 +0100, Ian Jackson wrote: > Ian Campbell writes ("Re: [PATCH OSSTEST v7 01/15] TestSupport: Add helper to > fetch a URL on a host"): > > On Mon, 2015-07-06 at 15:48 +0100, Ian Jackson wrote: > > > Ian Campbell writes ("[PATCH OSSTEST v7 01/15] TestSupport: Add helper to

Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the SEDF scheduler

On 07/06/2015 05:17 PM, Dario Faggioli wrote: > On Mon, 2015-07-06 at 16:40 +0100, George Dunlap wrote: >> On 07/06/2015 04:30 PM, Dario Faggioli wrote: >>> only the interface is left in place, for backward >>> compile-time compatibility, but every attempt to >>> use it would throw an error. >>> >>

Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the SEDF scheduler

On Mon, 2015-07-06 at 16:40 +0100, George Dunlap wrote: > On 07/06/2015 04:30 PM, Dario Faggioli wrote: > > only the interface is left in place, for backward > > compile-time compatibility, but every attempt to > > use it would throw an error. > > > > Signed-off-by: Dario Faggioli > > Reviewed-by

Re: [Xen-devel] [PATCH OSSTEST v7 12/15] Add testing of non-LVM/phy disk backends.

Ian Campbell writes ("Re: [PATCH OSSTEST v7 12/15] Add testing of non-LVM/phy disk backends."): > On Mon, 2015-07-06 at 16:21 +0100, Ian Jackson wrote: > > Are some of these jobs not very similar to existing ones ? > > They differ in the backing store used for the guest's disks, but > otherwise t

Re: [Xen-devel] [PATCH v2 0/3] gnttab: misc adjustments

On Mon, 2015-06-22 at 12:39 +0100, Jan Beulich wrote: > Patch 1 is a plain resend. Patches 2 and 3 are the split result of a > previously sent patch. > > 1: fix out of range shift count > 2: don't silently truncate frame numbers in gnttab_set_version() > 3: clean up gnttab_set_version() > > Signe

Re: [Xen-devel] [PATCH OSSTEST v7 01/15] TestSupport: Add helper to fetch a URL on a host

Ian Campbell writes ("Re: [PATCH OSSTEST v7 01/15] TestSupport: Add helper to fetch a URL on a host"): > On Mon, 2015-07-06 at 15:48 +0100, Ian Jackson wrote: > > Ian Campbell writes ("[PATCH OSSTEST v7 01/15] TestSupport: Add helper to > > fetch a URL on a host"): > > > +$useproxy wget --pro

Re: [Xen-devel] [PATCH 2/3] x86: drop is_pv_32on64_domain()

On Tue, 2015-06-23 at 16:19 +0100, Jan Beulich wrote: > ... as being identical to is_pv_32bit_domain() after the x86-32 > removal. > > In a few cases this includes no longer open-coding is_pv_32bit_vcpu(). > > Signed-off-by: Jan Beulich Given that the common impact is effectively x86-only due t

  1   2   3   >