search for: i387

...= 2.6.16.33" in the file "buildconfigs/mk.linux-2.6-xen". When I did "make world", the xen builder did download 2.6.16.33 tarball. But the compiling procedure failed with the following error message: /****************************************************/ include2/asm/i387.h: In function â__save_init_fpuâ: include2/asm/i387.h:63: error: expected expression before â[â token include2/asm/i387.h:63: error: âfxâ undeclared (first use in this function) include2/asm/i387.h:63: error: (Each undeclared identifier is reported only once include2/asm/i387.h:63: error: for each...

Package: xen-hypervisor-4.0-i386 Version: 4.0.1~rc6-1 Severity: important --- Please enter the report below this line. --- Booting up the Xen Dom0 fails with an error in "i387.c:159" --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686-bigmem Kernel: Linux 2.6.32-5-xen-686 Debian Release: squeeze/sid 500 testing security.debian.org 500 testing ftp2.de.debian.org --- Package information. --- Package's Depen...

...ystem-2.6.32-5-xen-amd64? system with grub2 but get an XEN BUG. We´ve tried alot, tested grub-legacy version but cannot get the XEN kernel to boot up. The XEN BUG occurs a  second after grub boots the kernel and there are no outputs at the serial console with debugging on. It only shows : xen BUG i387.c159 and reboots ore stays there if we add ?noreboot? to the configuration parameter. Here´s the grub config, thats sadly all i have:           insmod raid           insmod mdraid           insmod part_msdos           insmod part_msdos           insmod ext2             Insmod lvm          ...

If a guest sets a state and dirties the state, but later temporarily clears the state, and at this time if this vcpu is scheduled out, then other vcpus may corrupt the state before the vcpu is scheduled in again, thus the state cannot be restored correctly. To solve this issue, this patch save/restore all states unconditionally on vcpu context switch. Signed-off-by: Weidong Han

...ons(+), 27 deletions(-) =================================================================== --- a/arch/x86_64/kernel/Makefile +++ b/arch/x86_64/kernel/Makefile @@ -8,7 +8,8 @@ obj-y := process.o signal.o entry.o trap ptrace.o time.o ioport.o ldt.o setup.o i8259.o sys_x86_64.o \ x8664_ksyms.o i387.o syscall.o vsyscall.o \ setup64.o bootflag.o e820.o reboot.o quirks.o i8237.o \ - pci-dma.o pci-nommu.o alternative.o hpet.o tsc.o sched-clock.o + pci-dma.o pci-nommu.o alternative.o hpet.o tsc.o sched-clock.o \ + bugs.o obj-$(CONFIG_STACKTRACE) += stacktrace.o obj-$(CONFIG_X86_MCE) +=...

...ons(+), 27 deletions(-) =================================================================== --- a/arch/x86_64/kernel/Makefile +++ b/arch/x86_64/kernel/Makefile @@ -8,7 +8,8 @@ obj-y := process.o signal.o entry.o trap ptrace.o time.o ioport.o ldt.o setup.o i8259.o sys_x86_64.o \ x8664_ksyms.o i387.o syscall.o vsyscall.o \ setup64.o bootflag.o e820.o reboot.o quirks.o i8237.o \ - pci-dma.o pci-nommu.o alternative.o hpet.o tsc.o sched-clock.o + pci-dma.o pci-nommu.o alternative.o hpet.o tsc.o sched-clock.o \ + bugs.o obj-$(CONFIG_STACKTRACE) += stacktrace.o obj-$(CONFIG_X86_MCE) +=...

...y became apparent that this would be a long, tedious, error prone process that would eventually result in the death of a large section of my brain. In addition, it is not very fun to test this on the actual hardware it is designed to run on (although I did manage to track down a 386 with detachable i387 coprocessor, the owner is not sure it still boots). Someday it would be nice to have an audit of this code; it appears to be riddled with bugs relating to segmentation, for example it assumes LDT segments on overrides, does not use the mm->context semaphore to protect LDT access, and generally l...

...y became apparent that this would be a long, tedious, error prone process that would eventually result in the death of a large section of my brain. In addition, it is not very fun to test this on the actual hardware it is designed to run on (although I did manage to track down a 386 with detachable i387 coprocessor, the owner is not sure it still boots). Someday it would be nice to have an audit of this code; it appears to be riddled with bugs relating to segmentation, for example it assumes LDT segments on overrides, does not use the mm->context semaphore to protect LDT access, and generally l...

The first patch really isn''t as much of a follow-up than what triggered the security issues to be noticed in the first place. 1: x86: preserve FPU selectors for 32-bit guest code 2: x86: fix XCR0 handling 3: x86/xsave: adjust state management 4: x86/fxsave: bring in line with recent xsave adjustments The first two I would see as candidates for 4.3 (as well as subsequent backporting,

...= 0, sc_edi = 4583440, sc_esi = 4583424, sc_ebp = 1078935716, sc_esp = 1078935700, sc_ebx = 1074829380, sc_edx = 4583424, sc_ecx = 3117568, sc_eax = 14, sc_trapno = 14, sc_err = 4, sc_eip = 1074344288, sc_cs = 35, __csh = 0, sc_eflags = 66050, esp_at_signal = 1078935700, sc_ss = 43, __ssh = 0, i387 = 0, oldmask = 0, cr2 = 4583436}) at signal_i386.c:882 #3 <signal handler called> #4 find_entry_by_id (dir=0x45f000, id=14, root=0x45f000) at pe_resource.c:83 #5 0x4009322e in find_entry_by_nameW (dir=0x45f000, name=0xe, root=0x45f000) at pe_resource.c:115 #6 0x400934b4 in PE_Find...

Hello Clang and LLVM Devs, I have been working to add support for an attribute in clang and LLVM that helps user to guide interprocedural register allocation. But the use case I am having is very limited and thus I belieave it is good to have discussion on this before sending a patch. So for IPRA we have a situation where a function is calling a function which is written in assembly and it is

Hi all, at the moment SYSV ABI on i386 and use of double force stack realignments. This is an unfortunate side effect of double requesting 8 Bytes alignment, even though i387 support requires only 32bit alignment. Are there other cases like that around? I can think of a number of cases where it makes sense to align strings to 32bit at least. Joerg

...For logging the output is the same as in the above thread: Xen call trace ========== xsave_init + 0x6d/0x1f0 init_intel + 0x13d/0x380 generic_identity + 0x39/0x190 identify_cpu + 0xe2/0x250 __start_xen + 0x2ec6/0x3340 __high_start + 0xa1/0xa3 Error message: =========== Panic on CPU 0: Xen BUG at i387.c:159 For more info: http://wiki.xensource.com/xenwiki/Xen4.0 In Xen 4.0.1 there's a bug in HVM guest save/restore/livemigration on Intel CPUs, related to XSAVE feature. As a workaround you can add "no-xsave" as an option to Xen command line in grub.conf. This issue is fixed in...

I've been working on a fixed point mec3 echo can. The old "mec3" which crashed a lot of peoples machines because it was floating point in the kernel is now available as "mec3-float.h". I'd appreciate any testing / feedback on the new fixed point mec3 echo can. Thanks! Mark

...decided that a specific glibc bug (that causes mangled audio or crashes) that I found nearly a year ago (and has been fixed for as long) had probably become scarce enough to risk removing the '-D__NO_MATH_INLINES' define from the build. Math inlines help decode performance by using direct i387 assembly for exp() rather than a function call. I was wrong. It seems that glibc 2.1.2 and older is still alive and well. Glibc 2.1.3 is required for libvorbis to build correctly. Older versions of glibc contain a bug in the hand-rolled inline assembly for math functions; specifically, they int...

...decided that a specific glibc bug (that causes mangled audio or crashes) that I found nearly a year ago (and has been fixed for as long) had probably become scarce enough to risk removing the '-D__NO_MATH_INLINES' define from the build. Math inlines help decode performance by using direct i387 assembly for exp() rather than a function call. I was wrong. It seems that glibc 2.1.2 and older is still alive and well. Glibc 2.1.3 is required for libvorbis to build correctly. Older versions of glibc contain a bug in the hand-rolled inline assembly for math functions; specifically, they int...

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

.../* clts(); */ /* ''clts'' is done for us by Xen during virtual trap. */ + /* NB. ''clts'' is done for us by Xen during virtual trap. */ + __get_cpu_var(xen_x86_cr0) &= ~X86_CR0_TS; if (!used_math()) init_fpu(me); restore_fpu_checking(&me->thread.i387.fxsave); --- a/include/asm-i386/mach-xen/asm/system.h +++ b/include/asm-i386/mach-xen/asm/system.h @@ -2,8 +2,10 @@ #define __ASM_SYSTEM_H #include <linux/kernel.h> +#include <linux/threads.h> #include <asm/segment.h> #include <asm/cpufeature.h> +#include <asm/percp...

...-clean-files := hypervisor-blob.c hypervisor-raw + segments.o io.o lguest_user.o hypervisor.o diff -r 9d462a93e1fa arch/i386/lguest/core.c --- a/arch/i386/lguest/core.c Wed Mar 21 08:56:52 2007 +1100 +++ b/arch/i386/lguest/core.c Thu Mar 22 11:44:17 2007 +1100 @@ -19,17 +19,21 @@ #include <asm/i387.h> #include "lg.h" -/* This is our hypervisor, compiled from hypervisor.S. */ -static char __initdata hypervisor_blob[] = { -#include "hypervisor-blob.c" -}; +/* Found in hypervisor.S */ +extern char start_hyper_text[], end_hyper_text[], switch_to_guest[]; +extern unsigned...

...-clean-files := hypervisor-blob.c hypervisor-raw + segments.o io.o lguest_user.o hypervisor.o diff -r 9d462a93e1fa arch/i386/lguest/core.c --- a/arch/i386/lguest/core.c Wed Mar 21 08:56:52 2007 +1100 +++ b/arch/i386/lguest/core.c Thu Mar 22 11:44:17 2007 +1100 @@ -19,17 +19,21 @@ #include <asm/i387.h> #include "lg.h" -/* This is our hypervisor, compiled from hypervisor.S. */ -static char __initdata hypervisor_blob[] = { -#include "hypervisor-blob.c" -}; +/* Found in hypervisor.S */ +extern char start_hyper_text[], end_hyper_text[], switch_to_guest[]; +extern unsigned...