similar to: RE: hypercall_page

arm: implement exception and hypercall entries. xen/arch/arm/xen/Makefile | 3 + xen/arch/arm/xen/asm-offsets.c | 61 ++++++++ xen/arch/arm/xen/entry.S | 596 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ xen/arch/arm/xen/hypercalls.S | 67 +++++++++ xen/arch/arm/xen/physdev.c | 41 +++++ 5 files changed, 768 insertions(+), 0

Xen Developers, I noticed that my PV ops guests cause the hypervisor to invoke hypercall_page_initialise twice from traps.c (i.e. through wrmsr_hypervisor_regs), for different hypercall_page addresses. Looking at the code, I see hvmloader.c causing one of those, in its main. I read the HVM Loader Xen wiki page, Googled, spelunked the source, etc. but cannot find where / why the other hypercall

Hello, I am studing Xen hypercall now. I found that hypercall is invoked via hypercall_page, which is only filled with (in no-hypervisor-kernel-mode ): mov $i, %eax int $0x82 ret Why not invoked the hypercall directly by "int $0x82" ? What''s the advantage of using hypercall_page? Thanks, Wu _______________________________________________ Xen-devel mailing list

Keir, below/attached patch is necessary to allow SVM partitions to boot unmodified guests with xen-unstable.hg c/s 8961. c/s 8822 and 8828 (some necessary evtchn modifications) cause SVM partitions to fail with "lost interrupt" hda error during boot. We currently do not understand why these modifications are necessary and in fact, a race occurs with one part of the patch (added

hi, my friends: recently, i am reading the source codes about hypercall. First, i study a simple hypercall, for example, the "do_xen_version". In "xen-3.1.0-src\xen\common\kernel.c", the definition of "do_xen_version" is: DO(xen_version) (int cmd, XEN_GUEST_HANDLE(void) arg) { .... } according to the " #define DO(fn) long do_##fn ", the expanded form is

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 +++

I am learning xen's memory management recently. I find most docs is how to use the hypercall related memory management. Can somesome tell me where is the implementation of the them in the xen source. Or some docs explaining it will be ideal. 年少不惧江湖老，放歌四海任逍遥。未解前路多少事，欲与青天试比高。 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

On Sun, Oct 6, 2013 at 8:21 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > C:\Program Files (x86)\Microsoft Visual Studio > 11.0\VC\include\concrt.h(313): warning C4530: C++ exception handler used, > but unwind semantics are not enabled. Specify /EHsc > (C:\lld-x86_64_win7\lld-x86_**64-win7\llvm.src\tools\lld\** >

.. avoiding the need to update them with atomic (locked) ops. Conversion here isn''t complete in the sense that many places still use the old per-CPU accessors (which are now redundant). Since the patch is already rather big, I''d prefer replacing those in a subsequent patch. While doing this, I also converted x86''s multicall macros to no longer require inclusion of

Import the actual version of include/xen/interface/sched.h from Xen. Signed-off-by: Juergen Gross <jgross at suse.com> --- include/xen/interface/sched.h | 100 ++++++++++++++++++++++++++++++++++-------- 1 file changed, 82 insertions(+), 18 deletions(-) diff --git a/include/xen/interface/sched.h b/include/xen/interface/sched.h index f184909..a4c4d73 100644 ---

Import the actual version of include/xen/interface/sched.h from Xen. Signed-off-by: Juergen Gross <jgross at suse.com> Acked-by: David Vrabel <david.vrabel at citrix.com> --- include/xen/interface/sched.h | 100 ++++++++++++++++++++++++++++++++++-------- 1 file changed, 82 insertions(+), 18 deletions(-) diff --git a/include/xen/interface/sched.h b/include/xen/interface/sched.h index

Please CC as I''m not subscribed to valgrind-developers. Under Xen the toolstack is responsible for managing the domains in the system, e.g. creating, destroying, and otherwise manipulating them. To do this it uses a number of ioctls on the /proc/xen/privcmd device. Most of these (the MMAPBATCH ones) simply set things up such that a subsequenct mmap call will map the desired guest

Add a thread watching the xenbus shutdown control path and notifies a wait queue. Add HYPERVISOR_shutdown convenient inline for minios shutdown. Add proper shutdown to the minios test application. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> diff -r fdf241ea6ff4 extras/mini-os/include/kernel.h --- a/extras/mini-os/include/kernel.h Wed Nov 28 21:29:18 2012 +0100 +++

FWIW, I've seen it fail on some of my commits too, but I don't remember whether it was on the PS4 bot exclusively or not. Anyway, my understanding is that this test shouldn't inherently have different behaviour on PS4 specifically, but I could be mistaken. I suspect it's something more general to do with the configuration of the bot. James On 20 July 2018 at 03:52, Justin Bogner

Moritz Muehlenhoff writes ("Re: Xen package security updates for jessie 4.4, XSA-213, XSA-214"): > Yes, the distribution line should be jessie-security, but please send > a debdiff to team at security.debian.org for a quick review before > uploading (I have no idea whether dgit supports security-master). Here is the proposed debdiff (actually, a git diff) for xen in jessie. My

hi, my friends: Currently, i am studying the way of hypercall's implementation. i have already known the flow of hypercall's execuation, and i decided to add a new hypercall into the Xen. first, i want to know the detail of one hypercall function, for example, "do_xen_version", but i can not find the location of definition of "do_xen_version". who can help me? i have

Keir, The patch below is necessary to get ia64 building on current xen-unstable.hg. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 3983e4f1b054 xen/arch/ia64/Rules.mk --- a/xen/arch/ia64/Rules.mk Sun Mar 12 10:03:33 2006 +0100 +++ b/xen/arch/ia64/Rules.mk Mon Mar 13 09:36:01 2006 -0700 @@ -12,7 +12,7 @@ CPPFLAGS += -I$(BASEDIR)/include -I$(BA

I''m tinkering with some code to be able to talk to the hypervisor from Windows, with the ultimate aim to get a usable xenbus. So far I''ve created a driver for the Xen PCI ''device'', and (hopefully) mapped the hypercall space given by the CPUID call... What is the simplest hypercall I can make to get an answer from the hypervisor to tell me that it''s

This is slightly off-topic for the Syslinux mailing list, but I think it is still pertinent and it might be helpful anyway. I am confused about some conflicting information regarding DHCP option 93, Architecture Type. The UEFI specification v.2.4 Errata B, Table 179, "PXE Tag Definitions for EFI", makes reference to a table in:

It's pretty weird -- I can't reproduce this on my machine. Can you? I can only speculate a cause. But I'll try to disable the feature to see if buildbot will get back to green. On Thu, Feb 26, 2015 at 9:08 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > It looks like there are errors in the buildbot runs with std::future_error > when executing lot of tests,