search for: __x86_64__

Displaying 20 results from an estimated 252 matches for "__x86_64__".

2006 Jun 02
1
Re: [PATCH] klibc
On Thu, 01 June 2006, H. Peter Anvin wrote: > Brian F. G. Bidulock wrote: > > On Thu, 01 Jun 2006, Bob Picco wrote: > >> > >> -#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc_v9__) > >> +#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc_v9__) && \ > >> + !defined(__powerpc64__) > > > > Why not just !defined(__LP64__) ? > > _BITSIZE ==...
2006 Feb 19
2
[patch] statfs64 sparc64 fix
...bc-1.2.2.orig/include/sys/vfs.h 2006-02-15 18:32:10.000000000 +0100 +++ klibc-1.2.2/include/sys/vfs.h 2006-02-15 18:32:35.000000000 +0100 @@ -13,7 +13,7 @@ /* struct statfs64 -- there seems to be two standards - one for 32 and one for 64 bits, and they're incompatible... */ -#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc64__) +#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__arch64__) struct statfs { uint32_t f_type;
2015 Aug 04
0
[PATCH] Create OPUS_FAST_INT64 macro, to abstract conditions where opus_int64 should be used.
...ff --git a/silk/macros.h b/silk/macros.h index 2f24950..bc30303 100644 --- a/silk/macros.h +++ b/silk/macros.h @@ -43,17 +43,20 @@ POSSIBILITY OF SUCH DAMAGE. #define opus_unlikely(x) (!!(x)) #endif +/* Set this if opus_int64 is a native type of the CPU. */ +#define OPUS_FAST_INT64 (defined(__x86_64__) || defined(__LP64__) || defined(_WIN64)) + /* This is an OPUS_INLINE header file for general platform. */ /* (a32 * (opus_int32)((opus_int16)(b32))) >> 16 output have to be 32bit int */ -#if defined(__x86_64__) || defined(__LP64__) || defined(_WIN64) +#if OPUS_FAST_INT64 #define silk_SM...
2007 Jun 27
0
[PATCH 1/10] Provide basic Xen PM infrastructure
....S Tue Jun 26 20:28:13 2007 -0400 @@ -0,0 +1,267 @@ + .text + +#include <xen/config.h> +#include <xen/multiboot.h> +#include <public/xen.h> +#include <asm/asm_defns.h> +#include <asm/desc.h> +#include <asm/page.h> +#include <asm/msr.h> + +#if defined(__x86_64__) + + .code64 + +#define GREG(x) %r##x +#define SAVED_GREG(x) saved_r##x(%rip) +#define DECLARE_GREG(x) saved_r##x: .quad 0 +#define SAVE_GREG(x) movq GREG(x), SAVED_GREG(x) +#define LOAD_GREG(x) movq SAVED_GREG(x), GREG(x) + +#define REF(x) x(%rip) + +#define R...
2012 Sep 10
10
[PATCH] mem_event: fix regression affecting CR3, CR4 memory events
This is a patch repairing a regression in code previously functional in 4.1.x. It appears that, during some refactoring work, calls to hvm_memory_event_cr3 and hvm_memory_event_cr4 were lost. These functions were originally called in mov_to_cr() of vmx.c, but the commit http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the original code into generic functions up a level in
2012 Apr 21
6
[PATCH] xen: Add GS base to HVM VCPU context
...11:36:02 2012 -0700 +++ b/xen/arch/x86/domctl.c Fri Apr 20 17:55:49 2012 -0700 @@ -1592,6 +1592,12 @@ void arch_get_info_guest(struct vcpu *v, c.nat->user_regs.fs = sreg.sel; hvm_get_segment_register(v, x86_seg_gs, &sreg); c.nat->user_regs.gs = sreg.sel; +#ifdef __x86_64__ + if ( ring_0(&c.nat->user_regs) ) + c.nat->gs_base_kernel = sreg.base; + else + c.nat->gs_base_user = sreg.base; +#endif } else {
2009 Mar 10
2
[LLVMdev] linux mixed 32/64 systems
Currently the build systems sets ARCH based on the result of 'uname -m'. On a mixed 32/64 system (one with a 64-bit kernel and a 32-bit userspace) this will result in "x86_64" which is wrong. We'd like the ARCH variable to represent the userspace we're compiling in/for, not what the kernel happens to be. Does anyone know of a clean way to detect this sort of system
2009 Mar 10
0
[LLVMdev] linux mixed 32/64 systems
...ot; which is wrong. > > We'd like the ARCH variable to represent the userspace we're compiling > in/for, not what the kernel happens to be. > > Does anyone know of a clean way to detect this sort of system > configuration? Cleanest way is probably to explicitly test if __x86_64__ is defined, ie AC_COMPILE_IFELSE([AC_LANG_PROGRAM( [[#ifndef __x86_64__ error: Not x86-64 even if uname says so! #endif ]])], [ARCH=x86_64], [ARCH=i386]) Or in the alternative you can always key off sizeof(void *) == 8. Cheers, Nathan
2007 Aug 09
1
[PATCH] svm: allow guest to use EFER.FFXSE and EFER.LMSLE
...xen/arch/x86/hvm/svm/svm.c 2007-08-08 11:40:11.000000000 +0200 +++ 2007-08-08/xen/arch/x86/hvm/svm/svm.c 2007-08-08 11:43:53.000000000 +0200 @@ -68,6 +68,11 @@ static void *hsa[NR_CPUS] __read_mostly; /* vmcb used for extended host state */ static void *root_vmcb[NR_CPUS] __read_mostly; +#ifdef __x86_64__ +/* indicate whether guest may use EFER.LMSLE */ +static unsigned char cpu_has_lmsl = 1; +#endif + /* SVM feature flags */ u32 svm_feature_flags; @@ -190,7 +195,10 @@ static enum handler_return long_mode_do_ case MSR_EFER: /* Offending reserved bit will cause #GP. */ #ifdef __x86...
2008 Jan 18
0
[PATCH] minios: support COW for a zero page
...+++ b/extras/mini-os/arch/x86/traps.c Fri Jan 18 16:02:32 2008 +0000 @@ -118,6 +118,46 @@ void page_walk(unsigned long virt_addres } +static int handle_cow(unsigned long addr) { + pgentry_t *tab = (pgentry_t *)start_info.pt_base, page; + unsigned long new_page; + int rc; + +#if defined(__x86_64__) + page = tab[l4_table_offset(addr)]; + if (!(page & _PAGE_PRESENT)) + return 0; + tab = pte_to_virt(page); +#endif +#if defined(__x86_64__) || defined(CONFIG_X86_PAE) + page = tab[l3_table_offset(addr)]; + if (!(page & _PAGE_PRESENT)) + return 0; + tab =...
2018 Jan 25
2
[PATCH net-next 12/12] tools/virtio: fix smp_mb on x86
...2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/virtio/ringtest/main.h b/tools/virtio/ringtest/main.h index 593a328..301d59b 100644 --- a/tools/virtio/ringtest/main.h +++ b/tools/virtio/ringtest/main.h @@ -111,7 +111,7 @@ static inline void busy_wait(void) } #if defined(__x86_64__) || defined(__i386__) -#define smp_mb() asm volatile("lock; addl $0,-128(%%rsp)" ::: "memory", "cc") +#define smp_mb() asm volatile("lock; addl $0,-132(%%rsp)" ::: "memory", "cc") #else /* * Not using __ATOMIC_SEQ_CST since gcc...
2018 Jan 25
2
[PATCH net-next 12/12] tools/virtio: fix smp_mb on x86
...2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/virtio/ringtest/main.h b/tools/virtio/ringtest/main.h index 593a328..301d59b 100644 --- a/tools/virtio/ringtest/main.h +++ b/tools/virtio/ringtest/main.h @@ -111,7 +111,7 @@ static inline void busy_wait(void) } #if defined(__x86_64__) || defined(__i386__) -#define smp_mb() asm volatile("lock; addl $0,-128(%%rsp)" ::: "memory", "cc") +#define smp_mb() asm volatile("lock; addl $0,-132(%%rsp)" ::: "memory", "cc") #else /* * Not using __ATOMIC_SEQ_CST since gcc...
2013 May 31
3
[LLVMdev] compiler-rt tests in cmake?
Those changes shouldn't affect ARM at all, since everything is under #if defined(__i386__) || defined(__x86_64__). What version of glibc are you building with on x86? On Fri, May 31, 2013 at 7:16 PM, Greg Fitzgerald <garious at gmail.com> wrote: > The failures happen on x86 Linux, Ubuntu Lucid. On ARM Android, my > example code segfaults, whereas before it worked. I wasn't planning to &g...
2005 Jul 20
1
MMX IDCT for theora-exp
...*/ + +# define r0 "%mm0" +# define r1 "%mm1" +# define r2 "%mm2" +# define r3 "%mm3" +# define r4 "%mm4" +# define r5 "%mm5" +# define r6 "%mm6" +# define r7 "%mm7" + + +# undef M + +#if (defined(__amd64__) || defined(__x86_64__)) + + __asm__ __volatile__ ("\n" + "#lea %1,%%rcx\n" + : + : "d" (_y), + "c" (idctconstants) + + ); + +# define MIDM(M,I) MtoSTR(M+I*8(%rcx)) +# define M(I) MIDM( MaskOffset , I ) +# define MIDC(M,I) MtoSTR(M+(I-1)*8(%rcx)) +# define C(I) MIDC( CosineOff...
2008 Apr 21
1
[PATCH] x86-64: emulation support for cmpxchg16b
..._regs.edx) ) - { - _regs.eax = old_lo; - _regs.edx = old_hi; - _regs.eflags &= ~EFLG_ZF; - } - else if ( ops->cmpxchg8b == NULL ) - { - rc = X86EMUL_UNHANDLEABLE; - goto done; - } - else +#ifdef __x86_64__ + if ( op_bytes != 8 ) { - if ( (rc = ops->cmpxchg8b(ea.mem.seg, ea.mem.off, old_lo, old_hi, - _regs.ebx, _regs.ecx, ctxt)) != 0 ) + unsigned long old, new; + + if ( (rc = ops->read(ea.mem.seg, ea.mem.off, &...
2007 Oct 19
3
Problem with nr_nodes on large memory NUMA machine
We''ve run into an issue with an 8 node x3950 where xm info is showing only 6 nodes. I''ve traced the problem to the clip_to_limit function in arch/x86/e820.c. #ifdef __x86_64__ clip_to_limit((uint64_t)(MACH2PHYS_COMPAT_VIRT_END - __HYPERVISOR_COMPAT_VIRT_START) << 10, "Only the first %u GB of the physical memory map " "can be accessed by 32-on-64 guests."); #endif Boot messages.......
2017 Dec 08
3
Unresolved symbols in compiler-rt
...o the MS compiler, but according to my tests the code compiles and links OK with clang: I have not tested functionality though. Regarding the __LP64__ define, it's wrong to define it for Windows. SUA/Interix have LP64 long type model, while Cygwin, mingw and native Windows have LLP64. _M_X64 or __x86_64__ is more common. So I wonder, is the disabled compiler-rt parts intentional and not suitable for Windows? If not so, what can be done to enable it? Thanks Erik
2013 May 31
0
[LLVMdev] compiler-rt tests in cmake?
...x86? 2.11.1 for 64-bit x86 linux $ ldd --version ldd (Ubuntu EGLIBC 2.11.1-0ubuntu7.8) 2.11.1 On Fri, May 31, 2013 at 8:24 AM, Sergey Matveev <earthdok at google.com> wrote: > Those changes shouldn't affect ARM at all, since everything is under #if > defined(__i386__) || defined(__x86_64__). > > What version of glibc are you building with on x86? > > > On Fri, May 31, 2013 at 7:16 PM, Greg Fitzgerald <garious at gmail.com> wrote: >> >> The failures happen on x86 Linux, Ubuntu Lucid. On ARM Android, my >> example code segfaults, whereas before i...
2013 May 31
2
[LLVMdev] compiler-rt tests in cmake?
...; > $ ldd --version > ldd (Ubuntu EGLIBC 2.11.1-0ubuntu7.8) 2.11.1 > > On Fri, May 31, 2013 at 8:24 AM, Sergey Matveev <earthdok at google.com> > wrote: > > Those changes shouldn't affect ARM at all, since everything is under #if > > defined(__i386__) || defined(__x86_64__). > > > > What version of glibc are you building with on x86? > > > > > > On Fri, May 31, 2013 at 7:16 PM, Greg Fitzgerald <garious at gmail.com> > wrote: > >> > >> The failures happen on x86 Linux, Ubuntu Lucid. On ARM Android, my > >...
2017 Sep 01
1
[PATCH] launch: direct: limit kvm-pit.lost_tick_policy to x86
...b/launch-direct.c @@ -519,8 +519,10 @@ launch_direct (guestfs_h *g, void *datav, const char *arg) arg ("-rtc", "driftfix=slew"); if (guestfs_int_qemu_supports (g, data->qemu_data, "-no-hpet")) flag ("-no-hpet"); +#if defined(__i386__) || defined(__x86_64__) if (guestfs_int_version_ge (&data->qemu_version, 1, 3, 0)) arg ("-global", "kvm-pit.lost_tick_policy=discard"); +#endif /* UEFI (firmware) if required. */ if (guestfs_int_get_uefi (g, &uefi_code, &uefi_vars, &uefi_flags) == -1) -- 2.13.5