Re: [Xen-devel] [PATCH v4 10/21] acpi/table: Introduce acpi_table_get_entry_madt to get specified entry

On 2016/1/25 23:02, Jan Beulich wrote: On 23.01.16 at 10:20, wrote: >> > From: Shannon Zhao >> > >> > This function could get the specified index entry of MADT table. This >> > would be useful when it needs to get the contens of the entry. >> > >> > Cc: Jan Beulich >> > Signed-off-by: S

Re: [Xen-devel] [vfio-users] [PATCH v3 00/11] igd passthrough chipset tweaks

Hi, > 1) The OpRegion MemoryRegion is mapped into system_memory through > programming of the 0xFC config space register. > a) vfio-pci could pick an address to do this as it is realized. > b) SeaBIOS/OVMF could program this. > > Discussion: 1.a) Avoids any BIOS dependency, but vfio-pci would

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On 01/29/2016 08:52 AM, Razvan Cojocaru wrote: > On 01/28/2016 11:47 PM, Tamas K Lengyel wrote: >> >> >> On Thu, Jan 28, 2016 at 2:05 PM, Razvan Cojocaru >> mailto:rcojoc...@bitdefender.com>> wrote: >> >> On 01/28/2016 10:09 PM, Tamas K Lengyel wrote: >> > On Thu, Jan 28, 2016 at 6:52 AM, R

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On 01/28/2016 11:47 PM, Tamas K Lengyel wrote: > > > On Thu, Jan 28, 2016 at 2:05 PM, Razvan Cojocaru > mailto:rcojoc...@bitdefender.com>> wrote: > > On 01/28/2016 10:09 PM, Tamas K Lengyel wrote: > > On Thu, Jan 28, 2016 at 6:52 AM, Razvan Cojocaru > > mailto:rcojoc...@bitdefender.c

[Xen-devel] [qemu-mainline test] 79366: tolerable FAIL - PUSHED

flight 79366 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/79366/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 11 guest-start fail REGR. vs. 79323 Tests which did not succeed,

Re: [Xen-devel] [iGVT-g] [vfio-users] [PATCH v3 00/11] igd passthrough chipset tweaks

On 01/29/2016 10:54 AM, Alex Williamson wrote: > On Fri, 2016-01-29 at 02:22 +, Kay, Allen M wrote: >> >>> -Original Message- >>> From: iGVT-g [mailto:igvt-g-boun...@lists.01.org] On Behalf Of Alex >>> Williamson >>> Sent: Thursday, January 28, 2016 11:36 AM >>> To: Gerd Hoffmann; qem

[Xen-devel] [PATCH v7 09/18] tools/libxl: introduce libxl__domain_common_switch_qemu_logdirty()

Secondary vm is running in COLO mode, we need to send secondary vm's dirty page information to primary host at checkpoint, so we have to enable qemu logdirty on secondary. libxl__domain_suspend_common_switch_qemu_logdirty() is to enable qemu logdirty. But it uses libxl__domain_save_state, and call

[Xen-devel] [PATCH v7 16/18] tools/libxl: store remus_ops in checkpoint device state

Checkpoint device is an abstract layer to do checkpoint. COLO can also use it to do checkpoint. But there are still some codes in checkpoint device which touch remus. This patch and: tools/libxl: move remus state into a seperate structure tools/libxl: seperate device init/cleanup from checkpoint

[Xen-devel] [PATCH v7 11/18] tools/libxl: Add back channel to allow migration target send data back

In COLO mode, secondary needs to send the following data to primary: 1. In libxl Secondary sends the following CHECKPOINT_CONTEXT to primary: CHECKPOINT_SVM_SUSPENDED, CHECKPOINT_SVM_READY and CHECKPOINT_SVM_RESUMED 2. In libxc Secondary sends the dirty pfn list to primary But the io_fd o

[Xen-devel] [PATCH v7 18/18] tools/libxl: seperate device init/cleanup from checkpoint device layer

we call (init|cleanup)_subkind_nic and (init|cleanup)_subkind_drbd_disk directly in checkpoint device. Move them to libxl_remus.c, Call them before calling libxl__checkpoint_devices_setup() or after calling libxl__checkpoint_devices_teardown(). it is pure refactoring and no functional changes. Sig

[Xen-devel] [PATCH v7 07/18] migration/save: pass checkpointed_stream from libxl to libxc

Pass checkpointed_stream from libxl to libxc. It won't affact legacy migration because legacy migration won't use this param. Signed-off-by: Yang Hongyang Signed-off-by: Wen Congyang CC: Ian Campbell CC: Ian Jackson CC: Wei Liu CC: Andrew Cooper --- tools/libxc/include/xenguest.h | 6 +++

[Xen-devel] [PATCH v7 03/18] tools/libxl: move save/restore code into libxl_dom_save.c

This is purely code motion. Signed-off-by: Yang Hongyang Signed-off-by: Wen Congyang CC: Ian Jackson CC: Wei Liu Acked-by: Ian Campbell --- tools/libxl/Makefile | 2 +- tools/libxl/libxl_dom.c | 514 tools/libxl/libxl_dom_save.c | 543 +

[Xen-devel] [PATCH v7 00/18] Prerequisite patches for COLO

This patchset is Prerequisite for COLO feature. Refer to: http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping Patch status: 1. Acked patches: patch 2, 3, 4, 9, 10, 15, 16, 18 2. Reviewd patches: patch 1, 10, 13, 15, 16, 17, 18 3. New patches: none Note: patch 4 is updated to fix a bug You

[Xen-devel] [PATCH v7 08/18] tools/libxl: introduce libxl__domain_restore_device_model to load qemu state

In normal migration, the qemu state is passed to qemu as a parameter. With COLO, secondary vm is running. So we will do the following steps at every checkpoint: 1. suspend both primary vm and secondary vm 2. sync the state 3. resume both primary vm and secondary vm Primary will send qemu's state in

[Xen-devel] [PATCH v7 13/18] tools/libxl: rename remus device to checkpoint device

This patch is auto generated by the following commands: 1. git mv tools/libxl/libxl_remus_device.c tools/libxl/libxl_checkpoint_device.c 2. perl -pi -e 's/libxl_remus_device/libxl_checkpoint_device/g' tools/libxl/Makefile 3. perl -pi -e 's/\blibxl__remus_devices/libxl__checkpoint_devices/g' t

[Xen-devel] [PATCH v7 12/18] tools/libx{l, c}: add back channel to libxc

In COLO mode, both VMs are running, and are considered in sync if the visible network traffic is identical. After some time, they fall out of sync. At this point, the two VMs have definitely diverged. Lets call the primary dirty bitmap set A, while the secondary dirty bitmap set B. Sets A and B

[Xen-devel] [PATCH v7 10/18] tools/libxl: export logdirty_init

We need to enable logdirty on secondary, so we export logdirty_init for internal use. Rename it to libxl__logdirty_init. Signed-off-by: Yang Hongyang Signed-off-by: Wen Congyang Acked-by: Ian Campbell Reviewed-by: Konrad Rzeszutek Wilk --- tools/libxl/libxl_dom_save.c | 4 ++-- tools/libxl/li

[Xen-devel] [PATCH v7 14/18] tools/libxl: fix backword compatibility after the automatic renaming

The error code ERROR_REMUS_XXX was introduced in Xen 4.5, and changed to ERROR_CHECKPOINT_XXX after previous renaming. The patch fix the backword compatibility. Signed-off-by: Yang Hongyang Signed-off-by: Wen Congyang --- tools/libxl/libxl.h | 12 1 file changed, 12 insertions(+)

[Xen-devel] [PATCH v7 01/18] libxl/remus: init checkpoint_callback in Remus setup callback

init stream {read/write} state checkpoint_callback in Remus setup callback. There's no functional change, it's just refactoring so that we can move all remus code into one file. Signed-off-by: Yang Hongyang Signed-off-by: Wen Congyang CC: Andrew Cooper CC: Ian Campbell CC: Ian Jackson CC: Wei

[Xen-devel] [PATCH v7 15/18] tools/libxl: adjust the indentation

This is just tidying up after the "tools/libxl: rename remus device to checkpoint device" patch automatic renaming. Signed-off-by: Yang Hongyang Signed-off-by: Wen Congyang Acked-by: Ian Campbell Reviewed-by: Konrad Rzeszutek Wilk --- tools/libxl/libxl_checkpoint_device.c | 21 +++

[Xen-devel] [PATCH v7 17/18] tools/libxl: move remus state into a seperate structure

Add a new structure remus state, and move concrete layer's private member to remus state. it is pure refactoring and no functional changes. Init interval in libxl__remus_setup(). It is safe to move this initialisation, because this value is only used for remus, and remus will use this value after l

[Xen-devel] [PATCH v7 05/18] tools/libxc: support to resume uncooperative HVM guests

Before this patch: 1. suspend a. PVHVM and PV: we use the same way to suspend the guest (send the suspend request to the guest). If the guest doesn't support evtchn, the xenstore variant will be used, suspending the guest via XenBus control node. b. pure HVM: we call xc_domain_shutdown(..., S

[Xen-devel] [PATCH v7 06/18] tools/libxl: introduce enum type libxl_checkpointed_stream

Introduce enum type libxl_checkpointed_stream in IDL. rename the last argument of migrate_receive from "remus" to "checkpointed" since the semantics of this parameter has changed. NOTE: libxl_domain_restore_params and domain_create aren't changed here, checkpointed_stream is still an int. Becaus

[Xen-devel] [PATCH v7 04/18] libxl/save: Refactor libxl__domain_suspend_state

Currently struct libxl__domain_suspend_state contains 2 type of states, one is save state, another is suspend state. This patch separates those two out. The motivation of this is that COLO will need to do suspend/resume continuously, we need a more common suspend state. After this change, dss stan

[Xen-devel] [PATCH v7 02/18] tools/libxl: move remus code into libxl_remus.c

After previous refactoring, we are now able to move all remus code into a separate file libxl_remus.c. Export following functions for internal use: - Remus callbacks * libxl__remus_domain_suspend_callback * libxl__remus_domain_resume_callback * libxl__remus_domain_save_checkpoint_callback

[Xen-devel] [linux-4.1 test] 79329: regressions - trouble: blocked/broken/fail/pass

flight 79329 linux-4.1 real [real] http://logs.test-lab.xenproject.org/osstest/logs/79329/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 66399 build-i386-rumpuserxen

Re: [Xen-devel] schedulers and topology exposing questions

On Thu, Jan 28, 2016 at 03:10:57PM +, Dario Faggioli wrote: > On Wed, 2016-01-27 at 10:27 -0500, Konrad Rzeszutek Wilk wrote: > > On Wed, Jan 27, 2016 at 03:10:01PM +, George Dunlap wrote: > > >  > > > I'm not sure I understand the situation right, but it sounds a bit > > > like > > > what

[Xen-devel] [qemu-mainline baseline-only test] 38711: regressions - FAIL

This run is configured for baseline tests only. flight 38711 qemu-mainline real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38711/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm

Re: [Xen-devel] [iGVT-g] [vfio-users] [PATCH v3 00/11] igd passthrough chipset tweaks

On Fri, 2016-01-29 at 02:22 +, Kay, Allen M wrote: >  > > -Original Message- > > From: iGVT-g [mailto:igvt-g-boun...@lists.01.org] On Behalf Of Alex > > Williamson > > Sent: Thursday, January 28, 2016 11:36 AM > > To: Gerd Hoffmann; qemu-de...@nongnu.org > > Cc: igv...@ml01.01.org; xen-

[Xen-devel] [PATCH v5 05/10] virtio_ring: Support DMA APIs

virtio_ring currently sends the device (usually a hypervisor) physical addresses of its I/O buffers. This is okay when DMA addresses and physical addresses are the same thing, but this isn't always the case. For example, this never works on Xen guests, and it is likely to fail if a physical "virt

[Xen-devel] [PATCH v5 02/10] alpha/dma: use common noop dma ops

From: Christian Borntraeger Some of the alpha pci noop dma ops are identical to the common ones. Use them. Signed-off-by: Christian Borntraeger Reviewed-by: Joerg Roedel --- arch/alpha/kernel/pci-noop.c | 46 1 file changed, 4 insertions(+), 42 del

[Xen-devel] [PATCH v5 03/10] s390/dma: Allow per device dma ops

From: Christian Borntraeger As virtio-ccw will have dma ops, we can no longer default to the zPCI ones. Make use of dev_archdata to keep the dma_ops per device. The pci devices now use that to override the default, and the default is changed to use the noop ops for everything that does not specif

[Xen-devel] [PATCH v5 07/10] virtio_mmio: Use the DMA API if enabled

This switches to vring_create_virtqueue, simplifying the driver and adding DMA API support. Signed-off-by: Andy Lutomirski --- drivers/virtio/virtio_mmio.c | 67 ++-- 1 file changed, 15 insertions(+), 52 deletions(-) diff --git a/drivers/virtio/virtio_mmi

[Xen-devel] [PATCH v5 09/10] vring: Use the DMA API on Xen

Signed-off-by: Andy Lutomirski --- drivers/virtio/virtio_ring.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index c169c6444637..305c05cc249a 100644 --- a/drivers/virtio/virtio_ring.c +++ b/drivers/virtio/virtio_ring

[Xen-devel] [PATCH v5 00/10] virtio DMA API, yet again

This switches virtio to use the DMA API on Xen and if requested by module option. This fixes virtio on Xen, and it should break anything because it's off by default on everything except Xen PV on x86. To the Xen people: is this okay? If it doesn't work on other Xen variants (PVH? HVM?), can you

[Xen-devel] [PATCH v5 08/10] virtio_pci: Use the DMA API if enabled

This switches to vring_create_virtqueue, simplifying the driver and adding DMA API support. This fixes virtio-pci on platforms and busses that have IOMMUs. This will break the experimental QEMU Q35 IOMMU support until QEMU is fixed. In exchange, it fixes physical virtio hardware as well as virti

[Xen-devel] [PATCH v5 10/10] vring: Add a module parameter to force-enable the DMA API

This will be useful for testing. Signed-off-by: Andy Lutomirski --- drivers/virtio/virtio_ring.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index 305c05cc249a..46fb77d824e9 100644 --- a/drivers/virtio/virti

[Xen-devel] [PATCH v5 01/10] dma: Provide simple noop dma ops

From: Christian Borntraeger We are going to require dma_ops for several common drivers, even for systems that do have an identity mapping. Lets provide some minimal no-op dma_ops that can be used for that purpose. Signed-off-by: Christian Borntraeger Reviewed-by: Joerg Roedel --- include/linu

[Xen-devel] [PATCH v5 04/10] vring: Introduce vring_use_dma_api()

This is a kludge, but no one has come up with a a better idea yet. We'll introduce DMA API support guarded by vring_use_dma_api(). Eventually we may be able to return true on more and more systems, and hopefully we can get rid of vring_use_dma_api() entirely some day. Signed-off-by: Andy Lutomirsk

[Xen-devel] [PATCH v5 06/10] virtio: Add improved queue allocation API

This leaves vring_new_virtqueue alone for compatbility, but it adds two new improved APIs: vring_create_virtqueue: Creates a virtqueue backed by automatically allocated coherent memory. (Some day it this could be extended to support non-coherent memory, too, if there ends up being a platform on w

Re: [Xen-devel] [iGVT-g] [vfio-users] [PATCH v3 00/11] igd passthrough chipset tweaks

> -Original Message- > From: iGVT-g [mailto:igvt-g-boun...@lists.01.org] On Behalf Of Alex > Williamson > Sent: Thursday, January 28, 2016 11:36 AM > To: Gerd Hoffmann; qemu-de...@nongnu.org > Cc: igv...@ml01.01.org; xen-de...@lists.xensource.com; Eduardo Habkost; > Stefano Stabellini; Ca

Re: [Xen-devel] [PATCH v11 1/2] vmx: VT-d posted-interrupt core logic handling

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Friday, January 29, 2016 12:38 AM > To: Wu, Feng > Cc: Andrew Cooper ; Dario Faggioli > ; George Dunlap ; > Tian, Kevin ; xen-devel@lists.xen.org; Keir Fraser > > Subject: Re: [PATCH v11 1/2] vmx: VT-d posted-in

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

flight 79328 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/79328/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-rumpuserxen 5 rumpuserxen-build fail in 79178 REGR. vs. 79027 Tests which are fail

Re: [Xen-devel] build Xen tool fail

Thanks, I'll switch to staging and hope the fix will be merged to master soon. Thanks, -Xudong > -Original Message- > From: Ian Campbell [mailto:ian.campb...@citrix.com] > Sent: Thursday, January 28, 2016 5:23 PM > To: Hao, Xudong ; xen-devel@lists.xen.org > Subject: Re: build Xen tool f

Re: [Xen-devel] [PATCHv2 net] xen-netfront: request Tx response events more often

From: David Vrabel Date: Tue, 26 Jan 2016 17:12:44 + > From: Malcolm Crossley > > Trying to batch Tx response events results in poor performance because > this delays freeing the transmitted skbs. > > Instead use the standard RING_FINAL_CHECK_FOR_RESPONSES() macro to be > notified once the

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On Thu, Jan 28, 2016 at 2:05 PM, Razvan Cojocaru wrote: > On 01/28/2016 10:09 PM, Tamas K Lengyel wrote: > > On Thu, Jan 28, 2016 at 6:52 AM, Razvan Cojocaru > > mailto:rcojoc...@bitdefender.com>> wrote: > > > > This patch pauses the domain for all writes through the 'ad' > > pointer in m

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On 01/28/2016 10:09 PM, Tamas K Lengyel wrote: > On Thu, Jan 28, 2016 at 6:52 AM, Razvan Cojocaru > mailto:rcojoc...@bitdefender.com>> wrote: > > This patch pauses the domain for all writes through the 'ad' > pointer in monitor_domctl(), defers a domain_unpause() call until > after the

[Xen-devel] [ovmf test] 79324: regressions - FAIL

flight 79324 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/79324/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR. vs. 65543 test-amd64-i386-

[Xen-devel] [PATCH v2 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

Extend the existing get_mem_access memop to allow querying permissions in altp2m views as well. Signed-off-by: Tamas K Lengyel Cc: Ian Jackson Cc: Stefano Stabellini Cc: Ian Campbell Cc: Wei Liu Cc: Razvan Cojocaru Cc: Stefano Stabellini Cc: George Dunlap Cc: Keir Fraser Cc: Jan Beulich

[Xen-devel] [PATCH v2 1/2] altp2m: Merge p2m_set_altp2m_mem_access and p2m_set_mem_access

The altp2m subsystem in its current form uses its own HVMOP hypercall to set mem_access permissions, duplicating some of the code already present for setting regular mem_access permissions. In this patch we consolidate the two and update the corresponding tools. Signed-off-by: Tamas K Lengyel Cc:

[Xen-devel] [qemu-mainline test] 79323: tolerable FAIL - PUSHED

flight 79323 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/79323/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds15 guest-start/debian.repeat fail blocked in 79130 Tests which did not succeed,

[Xen-devel] [linux-3.16 test] 79322: regressions - FAIL

flight 79322 linux-3.16 real [real] http://logs.test-lab.xenproject.org/osstest/logs/79322/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-rumpuserxen6 xen-build fail REGR. vs. 77819 build-amd64-rumpuserxe

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On Thu, Jan 28, 2016 at 6:52 AM, Razvan Cojocaru wrote: > This patch pauses the domain for all writes through the 'ad' > pointer in monitor_domctl(), defers a domain_unpause() call until > after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG > case, and makes sure that the domain is paus

Re: [Xen-devel] [PATCH] documentation: Add disclaimer

Paul E. McKenney wrote: > Good point! Would you be willing to add a Signed-off-by so I > can take the combined change, assuming Peter and Will are good > with it? Sure! David ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xe

Re: [Xen-devel] [vfio-users] [PATCH v3 00/11] igd passthrough chipset tweaks

On Tue, 2016-01-05 at 12:41 +0100, Gerd Hoffmann wrote: >   Hi, >  > We have some code in our tree to support pci passthrough of intel > graphics devices (igd) on xen, which requires some chipset tweaks > for (a) the host bridge and (b) the lpc/isa-bridge to meat the > expectations of the guest dri

Re: [Xen-devel] Error booting Xen

Latest set looks good. No boot issues. No resets. Full log at http://paste2.org/NxHNW4vn Sorry I don't know much about source of last few lines. I was just tracing in xen when these came. I was unable to create them again. I will inform you if I get these again. Regards, Harmandeep On Wed, Jan 27

Re: [Xen-devel] schedulers and topology exposing questions

On Wed, Jan 27, 2016 at 02:01:35PM +, Dario Faggioli wrote: > On Fri, 2016-01-22 at 11:54 -0500, Elena Ufimtseva wrote: > > Hello all! > > > Hey, here I am again, > > > Konrad came up with a workaround that was setting the flag for domain > > scheduler in linux > > As the guest is not aware o

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On Thu, Jan 28, 2016 at 10:04 AM, Razvan Cojocaru wrote: > On 01/28/2016 06:40 PM, Lengyel, Tamas wrote: > > > > > > On Thu, Jan 28, 2016 at 9:32 AM, Razvan Cojocaru > > mailto:rcojoc...@bitdefender.com>> wrote: > > > > On 01/28/2016 05:58 PM, Lengyel, Tamas wrote: > > > > > > > >

Re: [Xen-devel] Revokable Grants Design (draft B)

>>> On 28.01.16 at 17:53, wrote: > On 28/01/16 15:38, Jan Beulich wrote: > On 25.01.16 at 18:20, wrote: >>> Grant Table Entry >>> - >>> >>> A new `GTF_revokable` flag is added. A grant reference with this bit >>> set may only be mapped with `GNTTABOP_map_revokable` or copied

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On 01/28/2016 06:40 PM, Lengyel, Tamas wrote: > > > On Thu, Jan 28, 2016 at 9:32 AM, Razvan Cojocaru > mailto:rcojoc...@bitdefender.com>> wrote: > > On 01/28/2016 05:58 PM, Lengyel, Tamas wrote: > > > > > > On Thu, Jan 28, 2016 at 8:20 AM, Razvan Cojocaru > > mailto:rcojoc...

Re: [Xen-devel] Revokable Grants Design (draft B)

On 28/01/16 15:38, Jan Beulich wrote: On 25.01.16 at 18:20, wrote: >> High Level Design >> = >> >> A revokable grant is indicated by an additional flag in the grant >> table entry. A domain may only map such a grant using a new sub-op >> (`GNTABOP_map_revokable`) and must sup

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On Thu, Jan 28, 2016 at 9:32 AM, Razvan Cojocaru wrote: > On 01/28/2016 05:58 PM, Lengyel, Tamas wrote: > > > > > > On Thu, Jan 28, 2016 at 8:20 AM, Razvan Cojocaru > > mailto:rcojoc...@bitdefender.com>> wrote: > > > > On 01/28/2016 05:12 PM, Lengyel, Tamas wrote: > > > > > > On Jan 2

Re: [Xen-devel] [PATCH v11 1/2] vmx: VT-d posted-interrupt core logic handling

>>> On 28.01.16 at 06:12, wrote: > --- a/xen/arch/x86/hvm/vmx/vmx.c > +++ b/xen/arch/x86/hvm/vmx/vmx.c > @@ -83,7 +83,140 @@ static int vmx_msr_write_intercept(unsigned int msr, > uint64_t msr_content); > static void vmx_invlpg_intercept(unsigned long vaddr); > static int vmx_vmfunc_intercept(s

[Xen-devel] [PATCH v2] arm: clean up build variables

This consolidates some of the different variables used for the ARM builds. This change was prompted by the Kconfig changes but looking back in time the CONFIG_ARM_{32,64} variables existed before Kconfig so this should just be a generic cleanup. Signed-off-by: Doug Goldstein Acked-by: Jan Beulich

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On 01/28/2016 05:58 PM, Lengyel, Tamas wrote: > > > On Thu, Jan 28, 2016 at 8:20 AM, Razvan Cojocaru > mailto:rcojoc...@bitdefender.com>> wrote: > > On 01/28/2016 05:12 PM, Lengyel, Tamas wrote: > > > > On Jan 28, 2016 8:02 AM, "Razvan Cojocaru" >

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On Thu, Jan 28, 2016 at 8:20 AM, Razvan Cojocaru wrote: > On 01/28/2016 05:12 PM, Lengyel, Tamas wrote: > > > > On Jan 28, 2016 8:02 AM, "Razvan Cojocaru" > > wrote: > >> > >> On 01/28/2016 04:42 PM, Lengyel, Tamas wrote: > >> > > >> > On Jan 28, 2016 6:38 AM, "

Re: [Xen-devel] Revokable Grants Design (draft B)

>>> On 25.01.16 at 18:20, wrote: > High Level Design > = > > A revokable grant is indicated by an additional flag in the grant > table entry. A domain may only map such a grant using a new sub-op > (`GNTABOP_map_revokable`) and must supply a local GFN. > > When the granting doma

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On 01/28/2016 05:12 PM, Lengyel, Tamas wrote: > > On Jan 28, 2016 8:02 AM, "Razvan Cojocaru" > wrote: >> >> On 01/28/2016 04:42 PM, Lengyel, Tamas wrote: >> > >> > On Jan 28, 2016 6:38 AM, "Jan Beulich" >> >

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On Jan 28, 2016 8:02 AM, "Razvan Cojocaru" wrote: > > On 01/28/2016 04:42 PM, Lengyel, Tamas wrote: > > > > On Jan 28, 2016 6:38 AM, "Jan Beulich" > > wrote: > >> > >> >>> On 27.01.16 at 21:06, > > wrote: > >> > --- a/xen/arch/x86/mm/p2m.c >

Re: [Xen-devel] schedulers and topology exposing questions

On Wed, 2016-01-27 at 10:27 -0500, Konrad Rzeszutek Wilk wrote: > On Wed, Jan 27, 2016 at 03:10:01PM +, George Dunlap wrote: > >  > > I'm not sure I understand the situation right, but it sounds a bit > > like > > what you're seeing is just a quirk of the fact that Linux doesn't > > always > >

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On 01/28/2016 04:42 PM, Lengyel, Tamas wrote: > > On Jan 28, 2016 6:38 AM, "Jan Beulich" > wrote: >> >> >>> On 27.01.16 at 21:06, > wrote: >> > --- a/xen/arch/x86/mm/p2m.c >> > +++ b/xen/arch/x86/mm/p2m.c >> > @@ -1572,7 +1572,9 @@ void p2m_

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On Jan 28, 2016 7:56 AM, "Jan Beulich" wrote: > > >>> On 28.01.16 at 15:42, wrote: > > On Jan 28, 2016 6:38 AM, "Jan Beulich" wrote: > >> >>> On 27.01.16 at 21:06, wrote: > >> > --- a/xen/arch/x86/mm/p2m.c > >> > +++ b/xen/arch/x86/mm/p2m.c > >> > @@ -1572,7 +1572,9 @@ void p2m_mem_access_emula

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

>>> On 28.01.16 at 15:42, wrote: > On Jan 28, 2016 6:38 AM, "Jan Beulich" wrote: >> >>> On 27.01.16 at 21:06, wrote: >> > --- a/xen/arch/x86/mm/p2m.c >> > +++ b/xen/arch/x86/mm/p2m.c >> > @@ -1572,7 +1572,9 @@ void p2m_mem_access_emulate_check(struct vcpu *v, >> > bool_t violation = 1;

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On 01/28/2016 04:10 PM, Andrew Cooper wrote: > On 28/01/16 13:52, Razvan Cojocaru wrote: >> This patch pauses the domain for all writes through the 'ad' >> pointer in monitor_domctl(), defers a domain_unpause() call until >> after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG >> case, and

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

On Jan 28, 2016 6:38 AM, "Jan Beulich" wrote: > > >>> On 27.01.16 at 21:06, wrote: > > --- a/xen/arch/x86/mm/p2m.c > > +++ b/xen/arch/x86/mm/p2m.c > > @@ -1572,7 +1572,9 @@ void p2m_mem_access_emulate_check(struct vcpu *v, > > bool_t violation = 1; > > const struct vm_event_mem_

Re: [Xen-devel] [PATCH v2] build: specify minimum versions of make and binutils

On 1/28/16 7:47 AM, Jan Beulich wrote: On 28.01.16 at 14:02, wrote: >> On Thu, 2016-01-28 at 05:49 -0700, Jan Beulich wrote: >> On 28.01.16 at 00:12, wrote: To help people avoid having to figure out what versions of make and binutils need to be supported document them explicitl

Re: [Xen-devel] [PATCH 1/2] altp2m: Merge p2m_set_altp2m_mem_access and p2m_set_mem_access

>>> On 28.01.16 at 15:34, wrote: > On Jan 28, 2016 6:18 AM, "Jan Beulich" wrote: >> >> >>> On 27.01.16 at 21:06, wrote: >> > --- a/xen/include/public/hvm/hvm_op.h >> > +++ b/xen/include/public/hvm/hvm_op.h >> > @@ -431,18 +431,6 @@ struct xen_hvm_altp2m_view { >> > typedef struct xen_hvm_altp2m

Re: [Xen-devel] [PATCH 1/2] altp2m: Merge p2m_set_altp2m_mem_access and p2m_set_mem_access

On Thu, Jan 28, 2016 at 07:30:31AM -0700, Lengyel, Tamas wrote: > On Jan 28, 2016 4:00 AM, "Wei Liu" wrote: > > > > On Thu, Jan 28, 2016 at 10:55:36AM +, Ian Campbell wrote: > > > --- a/tools/libxc/include/xenctrl.h > > > > > +++ b/tools/libxc/include/xenctrl.h > > > > > @@ -2027,9 +2027,6 @@

Re: [Xen-devel] [PATCH 1/2] altp2m: Merge p2m_set_altp2m_mem_access and p2m_set_mem_access

On Jan 28, 2016 6:18 AM, "Jan Beulich" wrote: > > >>> On 27.01.16 at 21:06, wrote: > > --- a/xen/include/public/hvm/hvm_op.h > > +++ b/xen/include/public/hvm/hvm_op.h > > @@ -431,18 +431,6 @@ struct xen_hvm_altp2m_view { > > typedef struct xen_hvm_altp2m_view xen_hvm_altp2m_view_t; > > DEFINE_X

Re: [Xen-devel] [PATCH 1/2] altp2m: Merge p2m_set_altp2m_mem_access and p2m_set_mem_access

On Jan 28, 2016 4:00 AM, "Wei Liu" wrote: > > On Thu, Jan 28, 2016 at 10:55:36AM +, Ian Campbell wrote: > > --- a/tools/libxc/include/xenctrl.h > > > > +++ b/tools/libxc/include/xenctrl.h > > > > @@ -2027,9 +2027,6 @@ int xc_altp2m_destroy_view(xc_interface *handle, > > > > domid_t domid, > >

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On 01/28/2016 04:10 PM, Andrew Cooper wrote: > On 28/01/16 13:52, Razvan Cojocaru wrote: >> This patch pauses the domain for all writes through the 'ad' >> pointer in monitor_domctl(), defers a domain_unpause() call until >> after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG >> case, and

Re: [Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

On 28/01/16 13:52, Razvan Cojocaru wrote: > This patch pauses the domain for all writes through the 'ad' > pointer in monitor_domctl(), defers a domain_unpause() call until > after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG > case, and makes sure that the domain is paused for both vm_e

Re: [Xen-devel] [PATCH] ARM: Support for guest-request vm-events

On 01/28/2016 03:03 PM, Ian Campbell wrote: > On Thu, 2016-01-28 at 14:57 +0200, Corneliu ZUZU wrote: >> >> >> Ok, great. I'll try it tonight and post a patch series ASAP. >> Concerning the CC list, Razvan actually noticed me earlier that he and >> Tamas should have >> been on it for this patch,

[Xen-devel] [PATCH] vm_event: make sure the domain is paused in key domctls

This patch pauses the domain for all writes through the 'ad' pointer in monitor_domctl(), defers a domain_unpause() call until after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG case, and makes sure that the domain is paused for both vm_event enable and disable cases in vm_event_domctl()

Re: [Xen-devel] [PATCH v2] build: specify minimum versions of make and binutils

>>> On 28.01.16 at 14:02, wrote: > On Thu, 2016-01-28 at 05:49 -0700, Jan Beulich wrote: >> > > > On 28.01.16 at 00:12, wrote: >> > To help people avoid having to figure out what versions of make and >> > binutils need to be supported document them explicitly. The version of >> > binutils that ha

Re: [Xen-devel] [PATCH 2/2] altp2m: Implement p2m_get_mem_access for altp2m views

>>> On 27.01.16 at 21:06, wrote: > --- a/xen/arch/x86/mm/p2m.c > +++ b/xen/arch/x86/mm/p2m.c > @@ -1572,7 +1572,9 @@ void p2m_mem_access_emulate_check(struct vcpu *v, > bool_t violation = 1; > const struct vm_event_mem_access *data = &rsp->u.mem_access; > > -if ( p2m_ge

[Xen-devel] [PATCH v2] Reset runstate_guest handles on soft reset

runstate_guest handles need to be reset to prevent update_runstate_area() corrupting guest's memory after we resume the guest. Signed-off-by: Vitaly Kuznetsov --- Changes since v1: - use set_xen_guest_handle() instead of raw memset() [Jan Beulich] --- xen/common/domain.c | 3 +++ 1 file changed,

Re: [Xen-devel] [PATCH 1/2] altp2m: Merge p2m_set_altp2m_mem_access and p2m_set_mem_access

>>> On 27.01.16 at 21:06, wrote: > --- a/xen/include/public/hvm/hvm_op.h > +++ b/xen/include/public/hvm/hvm_op.h > @@ -431,18 +431,6 @@ struct xen_hvm_altp2m_view { > typedef struct xen_hvm_altp2m_view xen_hvm_altp2m_view_t; > DEFINE_XEN_GUEST_HANDLE(xen_hvm_altp2m_view_t); > > -struct xen_hvm

Re: [Xen-devel] [PATCH] ARM: Support for guest-request vm-events

On Thu, 2016-01-28 at 14:57 +0200, Corneliu ZUZU wrote: >  > > Ok, great. I'll try it tonight and post a patch series ASAP. > Concerning the CC list, Razvan actually noticed me earlier that he and > Tamas should have > been on it for this patch, since it is vm-events related. He said the > probl

Re: [Xen-devel] [PATCH v2] build: specify minimum versions of make and binutils

On Thu, 2016-01-28 at 05:49 -0700, Jan Beulich wrote: > > > > On 28.01.16 at 00:12, wrote: > > To help people avoid having to figure out what versions of make and > > binutils need to be supported document them explicitly. The version of > > binutils that had to be supported was mentioned in > > h

Re: [Xen-devel] [PATCH v4 19/21] arm/acpi: Initialize serial port from ACPI SPCR table

>>> On 28.01.16 at 13:33, wrote: > On 2016/1/25 23:05, Jan Beulich wrote: > On 23.01.16 at 10:20, wrote: >>> --- a/xen/include/acpi/actbl2.h >>> +++ b/xen/include/acpi/actbl2.h >>> @@ -815,6 +815,15 @@ struct acpi_table_spcr { >>> >>> #define ACPI_SPCR_DO_NOT_DISABLE(1) >>> >>> +/* S

Re: [Xen-devel] [PATCH] ARM: Support for guest-request vm-events

On 1/28/2016 2:45 PM, Ian Campbell wrote: On Thu, 2016-01-28 at 14:36 +0200, CORNELIU ZUZU wrote: On 1/28/2016 1:23 PM, Ian Campbell wrote: On Thu, 2016-01-28 at 13:17 +0200, Corneliu ZUZU wrote: This patch implements ARM support for guest-request vm-events. The code has been ported from x86 s

Re: [Xen-devel] [PATCH v4 13/21] arm/gic-v2: Add ACPI boot support for GICv2

On Sat, 23 Jan 2016, Shannon Zhao wrote: > From: Parth Dixit > > ACPI on Xen hypervisor uses MADT table for proper GIC initialization. > First get the GIC version from GIC Distributor. Then parse GIC related > subtables, collect CPU interface and distributor addresses and call > driver initializa

Re: [Xen-devel] [PATCH] ARM: Support for guest-request vm-events

On 01/28/2016 02:45 PM, Ian Campbell wrote: > On Thu, 2016-01-28 at 14:36 +0200, CORNELIU ZUZU wrote: >> On 1/28/2016 1:23 PM, Ian Campbell wrote: >>> On Thu, 2016-01-28 at 13:17 +0200, Corneliu ZUZU wrote: This patch implements ARM support for guest-request vm-events. The code has been p

Re: [Xen-devel] [PATCH v2] build: specify minimum versions of make and binutils

>>> On 28.01.16 at 00:12, wrote: > To help people avoid having to figure out what versions of make and > binutils need to be supported document them explicitly. The version of > binutils that had to be supported was mentioned in > http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg0060

Re: [Xen-devel] [PATCH v4 12/21] arm/irq: Drop the DT prefix of the irq line type

On Sat, 23 Jan 2016, Shannon Zhao wrote: > From: Shannon Zhao > > Make these types generic to DT and ACPI. So they are can be used in ACPI > codes. > > Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini > xen/arch/arm/domain_build.c | 10 - > xen/arch/arm/gic-hip04.c

Re: [Xen-devel] [PATCH v4 11/21] arm: Introduce a generic way to use a device from acpi

On Sat, 23 Jan 2016, Shannon Zhao wrote: > From: Parth Dixit > > Add generic way to use device from acpi similar to the way it is > supported in device tree. > > Signed-off-by: Parth Dixit > Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini > V4: drop __attribute__ > --- > xen/arc

Re: [Xen-devel] [PATCH] ARM: Support for guest-request vm-events

On Thu, 2016-01-28 at 14:36 +0200, CORNELIU ZUZU wrote: > On 1/28/2016 1:23 PM, Ian Campbell wrote: > > On Thu, 2016-01-28 at 13:17 +0200, Corneliu ZUZU wrote: > > > This patch implements ARM support for guest-request vm-events. > > > The code has been ported from x86 side w/ minor adjustments. > >

Re: [Xen-devel] [PATCH] Reset runstate_guest handles on soft reset

>>> On 28.01.16 at 10:34, wrote: > --- a/xen/common/domain.c > +++ b/xen/common/domain.c > @@ -1074,7 +1074,10 @@ int domain_soft_reset(struct domain *d) > grant_table_warn_active_grants(d); > > for_each_vcpu ( d, v ) > +{ > +memset(&runstate_guest(v), 0, sizeof(runstate_gu

Re: [Xen-devel] [PATCH v4 05/21] arm/acpi: Add basic ACPI initialization

On Thu, 28 Jan 2016, Shannon Zhao wrote: > On 2016/1/28 19:27, Stefano Stabellini wrote: > > On Thu, 28 Jan 2016, Shannon Zhao wrote: > >> On 2016/1/28 18:44, Stefano Stabellini wrote: > >>> On Thu, 28 Jan 2016, Shannon Zhao wrote: > > On 2016/1/27 22:54, Stefano Stabellini wrote: > >>> On

  1   2   >