search for: syscall_enter

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?

...+0x107/0x1b4 (XEN) [<ffff83000010f10a>] get_page_and_type+0x21/0x50 (XEN) [<ffff8300001116c4>] __gnttab_copy+0x3f5/0x5b4 (XEN) [<ffff830000111971>] gnttab_copy+0xee/0x1c4 (XEN) [<ffff830000111dbd>] do_grant_table_op+0x376/0x3bc (XEN) [<ffff8300001b83e2>] syscall_enter+0xa2/0xfc (XEN) (XEN) Guest stack trace from rbp=ffff830000ff3cf8: (XEN) ???????????????? <G><2>grant_table.c:990:d0 do_grant_table_op: domain 0, cmd 5, count 1 (XEN) /export/build/schuster/xvm-gate/xen.hg/xen/include/asm/mm.h: 189:d0 Error pfn 30fc2a: rd=ffff830000fcf100, od=000000...

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

...gt;] domain_kill+0x7b/0x100 (XEN) [<ffff82c480103f54>] domctl_lock_acquire+0x44/0x70 (XEN) [<ffff82c48010465e>] do_domctl+0x4ae/0x1050 (XEN) [<ffff82c48014ab4d>] vcpu_kick+0x1d/0x80 (XEN) [<ffff82c48015d7b8>] get_page+0x28/0xf0 (XEN) [<ffff82c4801e9169>] syscall_enter+0xa9/0xae (XEN) (XEN) Pagetable walk from ffff8315ffffffe4: (XEN) L4[0x106] = 00000000cf56d027 5555555555555555 (XEN) L3[0x057] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 9: (XEN) FATAL PAGE FAULT (XEN) [error_code=0002] (XEN) Fault...

...popq %rcx # RIP popq %r11 # CS - cmpw $FLAT_KERNEL_CS32,%r11 + cmpw $FLAT_USER_CS32,%r11 popq %r11 # RFLAGS popq %rsp # RSP je 1f @@ -127,6 +131,9 @@ ENTRY(syscall_enter) movl $TRAP_syscall,4(%rsp) SAVE_ALL GET_CURRENT(%rbx) + movq VCPU_domain(%rbx),%rcx + testb $1,DOMAIN_is_32bit_pv(%rcx) + jnz compat_syscall testb $TF_kernel_mode,VCPU_thread_flags(%rbx) jz switch_to_kernel @@ -224,6 +231,4...

...ffffffff8100142a 0000000000000000 ffff88002db9d568 (XEN) Xen call trace: (XEN) [<ffff82c48015b450>] pci_enable_msi+0x466/0x945 (XEN) [<ffff82c48015cd07>] map_domain_pirq+0x28a/0x377 (XEN) [<ffff82c4801700a2>] do_physdev_op+0x7f2/0x1040 (XEN) [<ffff82c4801fb8e2>] syscall_enter+0xf2/0x14c (XEN) (XEN) Xen WARN at msi.c:649 (XEN) ----[ Xen-4.1-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 3 (XEN) RIP: e008:[<ffff82c48015b4ce>] pci_enable_msi+0x4e4/0x945 (XEN) RFLAGS: 0000000000010246 CONTEXT: hypervisor (XEN) rax: 0000000000000000 rbx: 00000000...

...ER(nmi_crash); DECLARE_TRAP_HANDLER(int3); DECLARE_TRAP_HANDLER(overflow); DECLARE_TRAP_HANDLER(bounds); @@ -545,6 +546,9 @@ DECLARE_TRAP_HANDLER(alignment_check); DECLARE_TRAP_HANDLER(spurious_interrupt_bug); #undef DECLARE_TRAP_HANDLER +void trap_nop(void); +void enable_nmis(void); + void syscall_enter(void); void sysenter_entry(void); void sysenter_eflags_saved(void);

...ffffbeef (XEN) ffffffffffffbeef ffffffff00000005 ffff8300ba9c1000 00000033ac86b080 (XEN) ffffffffffffffff (XEN) Xen call trace: (XEN) [<ffff82d080161cd6>] unmap_domain_page+0x1a7/0x1ff (XEN) [<ffff82d08017c6b7>] do_mmu_update+0x16e3/0x19aa (XEN) [<ffff82d0802248db>] syscall_enter+0xeb/0x145 (XEN) (XEN) Assertion ''l1e_get_pfn(MAPCACHE_L1ENT(idx)) == mfn'' failed at domain_page.c:94 (XEN) (XEN) **************************************** (XEN) ----[ Xen-4.4-unstable x86_64 debug=y Not tainted ]---- (XEN) Panic on CPU 5: (XEN) CPU: 6 (XEN) Assertion '...

This set of patches converts the way frames gets created from using PUSHes/POPs to using MOVes, thus allowing (in certain cases) to avoid saving/restoring part of the register set. While the place where the (small) win from this comes from varies between CPUs, the net effect is a 1 to 2% reduction on a combined interruption entry and exit when the full state save can be avoided. 1: use MOV

...ex: 2007-03-19/xen/arch/x86/x86_64/entry.S =================================================================== --- 2007-03-19.orig/xen/arch/x86/x86_64/entry.S 2007-02-28 12:10:32.000000000 +0100 +++ 2007-03-19/xen/arch/x86/x86_64/entry.S 2007-03-27 12:11:33.000000000 +0200 @@ -147,7 +147,7 @@ ENTRY(syscall_enter) pushq UREGS_rip+8(%rsp) #endif leaq hypercall_table(%rip),%r10 - PERFC_INCR(PERFC_hypercalls, %rax) + PERFC_INCR(PERFC_hypercalls, %rax, %rbx) callq *(%r10,%rax,8) #ifndef NDEBUG /* Deliberately corrupt parameter regs used by this hypercall. */...

Hello, I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN and copied the blk files from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN (I don''t know which of these patches have been applied to xen unstable, so

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend

(The list appears to have eaten my previous attempt to send this. Apologies if you receive multiple copies.) The attached patches allow you to use paravirtualised network and block interfaces from fully virtualised domains, based on Intel''s patches from a few months ago. These are significantly faster than the equivalent ioemu devices, sometimes by more than an order of magnitude.

...0x3b (XEN) [<ffff82d0801286ec>] _spin_lock_irqsave+0x17/0x84 (XEN) [<ffff82d08016c1c5>] pirq_spin_lock_irq_desc+0x38/0x80 (XEN) [<ffff82d08016c59d>] pirq_guest_eoi+0x1f/0x36 (XEN) [<ffff82d080180249>] do_physdev_op+0x13c/0x112b (XEN) [<ffff82d0802248db>] syscall_enter+0xeb/0x145 (XEN) (XEN) Pagetable walk from ffff830448098c28: (XEN) L4[0x106] = 00000000ba681063 ffffffffffffffff (XEN) L3[0x011] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Fa...

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,

Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have