search for: int80

...+ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can assemble it. +# Note: kbuild does not track this dependency due to usage of .include +$(obj)/vsyscall.o: $(obj)/vsyscall-int80.rel $(obj)/vsyscall-sysenter.rel +targets += $(foreach F,int80 sysenter,vsyscall-$F.so.alt vsyscall-$F.rel) +targets += vsyscall.lds.alt + +# The alternative DSO images are built using an alternate base address. +quiet_cmd_syscall_alt = REBASE $@ + cmd_syscall_alt = sed ''s,^\([[:spac...

...+ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can assemble it. +# Note: kbuild does not track this dependency due to usage of .include +$(obj)/vsyscall.o: $(obj)/vsyscall-int80.rel $(obj)/vsyscall-sysenter.rel +targets += $(foreach F,int80 sysenter,vsyscall-$F.so.alt vsyscall-$F.rel) +targets += vsyscall.lds.alt + +# The alternative DSO images are built using an alternate base address. +quiet_cmd_syscall_alt = REBASE $@ + cmd_syscall_alt = sed ''s,^\([[:spac...

...+ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can assemble it. +# Note: kbuild does not track this dependency due to usage of .include +$(obj)/vsyscall.o: $(obj)/vsyscall-int80.rel $(obj)/vsyscall-sysenter.rel +targets += $(foreach F,int80 sysenter,vsyscall-$F.so.alt vsyscall-$F.rel) +targets += vsyscall.lds.alt + +# The alternative DSO images are built using an alternate base address. +quiet_cmd_syscall_alt = REBASE $@ + cmd_syscall_alt = sed ''s,^\([[:spac...

...i/wakeup_rm.o LD arch/x86/kernel/acpi/built-in.o LDS arch/x86/kernel/vmlinux.lds LD arch/x86/kernel/built-in.o LDS arch/x86/vdso/vdso32/vdso32.lds VDSO arch/x86/vdso/vdso32-sysenter.so.dbg VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds VDSO arch/x86/vdso/vdso32-int80.so.dbg OBJCOPY arch/x86/vdso/vdso32-sysenter.so VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds OBJCOPY arch/x86/vdso/vdso32-int80.so VDSOSYM arch/x86/vdso/vdso32-syms.lds AS arch/x86/vdso/vdso32.o LD arch/x86/vdso/built-in.o LD arch/x86/built-in.o CC [M] drivers/usb/ser...

...i/wakeup_rm.o LD arch/x86/kernel/acpi/built-in.o LDS arch/x86/kernel/vmlinux.lds LD arch/x86/kernel/built-in.o LDS arch/x86/vdso/vdso32/vdso32.lds VDSO arch/x86/vdso/vdso32-sysenter.so.dbg VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds VDSO arch/x86/vdso/vdso32-int80.so.dbg OBJCOPY arch/x86/vdso/vdso32-sysenter.so VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds OBJCOPY arch/x86/vdso/vdso32-int80.so VDSOSYM arch/x86/vdso/vdso32-syms.lds AS arch/x86/vdso/vdso32.o LD arch/x86/vdso/built-in.o LD arch/x86/built-in.o CC [M] drivers/usb/ser...

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event

...rap. > > I agree, but don't forget the most prominent underlying reason for IST: > The SYSCALL gap. If SYSCALL would switch stacks most of those issues > would not exist. IST would still be needed because there are no task > gates in x86-64, but still... We could all go back to int80 ;-) /me runs like heck

On Tue, Jun 23, 2020 at 01:48:18PM +0200, Peter Zijlstra wrote: > On Tue, Jun 23, 2020 at 01:30:07PM +0200, Joerg Roedel wrote: > But you cannot do a recursion check in #VC, because the NMI can happen > on the first instruction of #VC, before we can increment our counter, > and then the #VC can happen on NMI because the IST stack is a goner, and > we're fscked again (or on a

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel