similar to: [PATCH][HVM] fix HVM hypercall preemption causing guest crash

Hi Steve, On 2019/12/17 22:40, Steven Price wrote: > On Tue, Dec 17, 2019 at 01:55:49PM +0000, yezengruan at huawei.com wrote: >> From: Zengruan Ye <yezengruan at huawei.com> >> >> Support the vcpu_is_preempted() functionality under KVM/arm64. This will >> enhance lock performance on overcommitted hosts (more runnable vcpus >> than physical cpus in the

2016-07-07 18:12 GMT+08:00 Wanpeng Li <kernellwp at gmail.com>: > 2016-07-07 17:42 GMT+08:00 Peter Zijlstra <peterz at infradead.org>: >> On Thu, Jul 07, 2016 at 04:48:05PM +0800, Wanpeng Li wrote: >>> 2016-07-06 20:28 GMT+08:00 Paolo Bonzini <pbonzini at redhat.com>: >>> > Hmm, you're right. We can use bit 0 of struct kvm_steal_time's flags

2016-07-07 18:12 GMT+08:00 Wanpeng Li <kernellwp at gmail.com>: > 2016-07-07 17:42 GMT+08:00 Peter Zijlstra <peterz at infradead.org>: >> On Thu, Jul 07, 2016 at 04:48:05PM +0800, Wanpeng Li wrote: >>> 2016-07-06 20:28 GMT+08:00 Paolo Bonzini <pbonzini at redhat.com>: >>> > Hmm, you're right. We can use bit 0 of struct kvm_steal_time's flags

For an SMP Linux HVM guest with PV drivers inserted, when we do save/restore (or LiveMigration) for the guest, it might panic after it''s restored. The panic point is inside ap_suspend(): .... while (info->do_spin) { cpu_relax(); read_lock(&suspend_lock); HYPERVISOR_yield(); ----> guest might panic on the invocation of this function.

Can anyone provide a code fragment of what a hypercall would look like under a HVM Windows domain? Or is the answer more complicated than the question assumes? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Fix the HVM save hypercall to avoid freeing an uninitalised pointer. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/restor purpose. It will be fine that

Hey all, I'm investigating LLVM for use for a future project of mine, and I was wondering whether something is possible. Specifically, I'm wondering if there's a way to force preemption of a green thread-style task - something like Erlang's "processes", where if a task executes for too long, it is preempted. [1] My main goal here is to avoid having to write my own

add a hypercall number for virtual device in unmodified guest There are 6 patches for para-driver support in vmx guest. This is the first one. Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> diff -r 287d36b46fa3 xen/arch/x86/x86_32/entry.S --- a/xen/arch/x86/x86_32/entry.S Tue Aug 30 20:36:49 2005 +++

CC''ing Tim and xen-devel On Mon, 18 Jul 2011, Jiageng Yu wrote: > 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > > On Fri, 15 Jul 2011, Jiageng Yu wrote: > >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: > >> > 2011/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > >> >> On Fri, 15 Jul 2011,

Hi, I would like to know about which threads will be preempted by which on my OpenSolaris machine. Therefore, I ran a multithreaded program "myprogram" with 32 threads on my 24-core Solaris machine. I make sure that each thread of my program has same priority (priority zero), so that we can reduce priority inversions (saving preemptions -- system overhead). However, I ran the following

On Thu, Jul 07, 2016 at 04:48:05PM +0800, Wanpeng Li wrote: > 2016-07-06 20:28 GMT+08:00 Paolo Bonzini <pbonzini at redhat.com>: > > Hmm, you're right. We can use bit 0 of struct kvm_steal_time's flags to > > indicate that pad[0] is a "VCPU preempted" field; if pad[0] is 1, the > > VCPU has been scheduled out since the last time the guest reset the

On Thu, Jul 07, 2016 at 04:48:05PM +0800, Wanpeng Li wrote: > 2016-07-06 20:28 GMT+08:00 Paolo Bonzini <pbonzini at redhat.com>: > > Hmm, you're right. We can use bit 0 of struct kvm_steal_time's flags to > > indicate that pad[0] is a "VCPU preempted" field; if pad[0] is 1, the > > VCPU has been scheduled out since the last time the guest reset the

hello, I would like to map (Read/Write) pages owned by a HVM guest from my Dom0 Linux kernel module. I have access to the "machine frame numbers" of these pages. 1. What is the right interface to do this? kmap needs ''struct page'' ptrs which I doubt exist for pages owned by a HVM guest. Is there a hypercall to do this then? 2. Do I need to modify the HVM behavior in

To make use of the new node aware memop hypercall, the xc_domain_memory_populate_physmap function is extended by a node parameter. Passing XENMEM_DEFAULT_NODE mimics the current behavior. Signed-off-by: Andre Przywara <andre.przywara@amd.com> -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 277-84917 ----to satisfy European Law for business

On 03/14/2014 04:30 AM, Peter Zijlstra wrote: > On Thu, Mar 13, 2014 at 04:05:19PM -0400, Waiman Long wrote: >> On 03/13/2014 11:15 AM, Peter Zijlstra wrote: >>> On Wed, Mar 12, 2014 at 02:54:52PM -0400, Waiman Long wrote: >>>> +static inline void arch_spin_lock(struct qspinlock *lock) >>>> +{ >>>> + if

Hello, I''m new to Xen and especially to the hypervisor code. I''m working off a 3.0.4.1 base and have the following questions regarding the memory management code for an x86, 32-bit platform (capable of supporting PAE). I''m doing some research into providing grant table hypercall support from a Windows 2003 HVM. I have made all the necessary changes to allow the

When I try to start hvm qemu-xen I get this error It seems that the path my be off. Can someone point me were in source code path to qemu pid is defined .It seems that qeum-xen points to loacation I don''t see were it is defined. xc: detail: elf_load_binary: phdr 0 at 0x0x7f71cac72000 -> 0x0x7f71cad079d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error:

Hi, I am currently working on hypercalls from HVM guests. I started with a set of Intel patches posted to xen-devel last September. I currently have code running for both 32-bit and 64-bit HVM guests running on a 64-bit hypervisor. I am curious why none of the original patches were accepted, and what I might need to do to make them acceptable. Is other work being done in this area that

On 03/17/2014 03:10 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 17, 2014 at 01:44:34PM -0400, Waiman Long wrote: >> On 03/14/2014 04:30 AM, Peter Zijlstra wrote: >>> On Thu, Mar 13, 2014 at 04:05:19PM -0400, Waiman Long wrote: >>>> On 03/13/2014 11:15 AM, Peter Zijlstra wrote: >>>>> On Wed, Mar 12, 2014 at 02:54:52PM -0400, Waiman Long wrote: