similar to: How to know hypercall entry and exit addresses?

Hi, I implemented my own Hypercall in xen. Now I wish my application under dom0 could talk to Xen via my hypercall. Currently, I make a stub in dom0''s kernel, which works as a proxy to forward the request. So, my application first makes a system call to dom0, which then makes hypercall to xen. Is this design necessary? May I call hypercalls from user application under dom0 directly?

For my debugging pleasure I have added another domctrl to call trace_var from xc_save. That works as expected. However, it adds additional pressure on the tracebuffer because each hypercall is traced as well. My question is: Would an additional domctrl (or whatever), or another trace hypercall be acceptable? Another hypercall would at least have a chance to be ignored by trace_hypercall()

Hi, I''d like to do some operation every time an hypercall is issued in a domU kernel. I started modifying include/asm-i386/mach-xen/asm/hypercall.h but I don''t think it''s such a great idea, so I think that, as a last chance, I''ll have to substitute all of the hypercall function call with some wrapper function of my own. Can anyone tell me if

Hi, I am working on a security architecture. In this architecture, the application in DomU has to communicate directly with the hypervisor. But as I can see, the xen architecture allows only DomU kernel to raise a hypercall. I am planning to enable application to communicate with xen directly. I am assuming, setting up a trap gate with Ring-3 access should do the trick. I have few questions

Sorry, forget to join lists. Regards, Jinsong -----Original Message----- From: Liu, Jinsong Sent: 2007年5月16日 8:23 To: ''Keir Fraser''; Tian, Kevin; xen-devel@lists.xensource.com Subject: RE: [Xen-devel] trap/interrupt gate for hypercall In native linux, syscall (gate type 15) and its RESTORE_ALL code provides weak fixup mechanism when reload segment register, by sending 0

This patch pretty prints the hypercall section for $xenperf -f Each hypercall count is tagged by its name. Reference: http://lists.xensource.com/archives/html/xen-ia64-devel/2006-08/msg00261.html Signed-off-by Ken Hironaka <kenny@logos.ic.i.u-tokyo.ac.jp> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, I need to find the points where we enters into hypercall (for all the hypercalls) execution and from where we come out... from what i have understood entry-point is somewhere in arch/x86/x86_32/entry.S ...but exactly where and what about exit point? -- Nitin Gupta _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Hi, I have *implemented a new hypercall* and it is working fine when tested from the Dom0 user-space. I want to invoke this hypercall from DomU user-space. I copied all the /usr/lib/libxen* and /usr/include/xen* (recursively) to the DomU Here''s the code I wrote to invoke hypercall: #include <stdio.h> #include <xenctrl.h> int main(void){ int xc_handle, rc;

Any thoughts on setting breakpoints around hypercalls? ---------- Forwarded message ---------- From: Kip Macy <kip.macy@gmail.com> Date: Dec 26, 2005 12:14 AM Subject: setting breakpoints around hypercalls in a domU causes dom0 to lockup To: xen-devel <xen-devel@lists.xensource.com>, Keir Fraser < Keir.Fraser@cl.cam.ac.uk> Stepping through hypercalls (at the source level, not

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

When operating on an unpinned pagetable (ie, one under construction or destruction), it isn''t necessary to use a hypercall to update a pud/pmd entry. Jan Beulich observed that a similar optimisation avoided many thousands of hypercalls while doing a kernel build. One tricky part is that early in the kernel boot there''s no page structure, so we can''t check to see if the

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

Hello, For our research we are trying to come up with a Virtual - passthrough model of device drivers in  PV guests. We are looking for 2 separate implementations : 1 for transmitting and the other for receiving the packets in the guest OS. We are relying on IOMMU to ensure isolation. We need to add  these new hypercalls for communication between the guest device driver and the hypervisor. The

(CCed to xen-devel for completeness. ;) On Wed, 2006-08-16 at 17:24 +0200, Tristan Gingold wrote: > I am porting xen-ppc''s xencomm to xen/ia64. > Currently on xen/ia64 copy_from/to_guest uses guest virtual address. This > works well as long as the virtual addresses are in the TLB. When not in TLB > (or vTLB) the hypercall can''t success without domain help. The

Hi All, I am new to XEN and I am trying to measure the overhead of each hypercall (number of instructions or cycles per hypercall). Please help me if anybody has done such experiments. Thanks, Vikas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Keir Fraser wrote: > On 19 Apr 2006, at 17:44, Hollis Blanchard wrote: > >> "xen_frameno_t" then? > > xen_pfn_t? Definitely won''t conflict with anyone, and I prefer ''pfn'' > to ''frameno'' as it''s more consistent with other names we have in the > interface. > >> Attached is the updated patch, with

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.

Hi, the attached patch makes Xen tracing work again, after the introduction of the hypercall buffers broke it. Just a missing line. Thanks to Uwe Dannowski for reporting this. Signed-off-by: Andre Przywara <andre.przywara@amd.com> Regards, Andre. -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 448-3567-12

What are the possible cases (I hope there are not many:)) that this Hypercall might fail, HYPERVISOR_event_channel_op(EVTCHNOP_send, &op)???,With an error value of "-ENOSYS (-38)" on a "HVM"? Thx, Venkat _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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