search for: d32

Hi, I am trying to run libvchan on ARM Fast Model for VExpress platform for using inter domain communication. But there are some errors. I am attaching the strace outputs for vchan-node1 run in dom0 and domU. Has anybody faced these issues before. Xl console 1The command is Usage: vchan-node1 [client|server] [write|read] domid nodepath my nodepath is - /local/domain/1/data/vchan-2-1 Regards

...e (xs.c:1143) ==5722== by 0x427A89B: read_thread (xs.c:1219) ==5722== by 0x40E7953: start_thread (pthread_create.c:304) ==5722== by 0x41CF95D: clone (clone.S:130) And the bootloader one appears to increase with each reboot. FTR I did: valgrind --leak-check=full xl cr -F /etc/xen/d32-1 (-F runs xl in the foreground, so this won't return to a prompt). Then in another window: xl reboot d32-1 (equivalent to running init 6). Ian.

...see sth that to me looks like a JIT bug. The program is the KMeans benchmark from the STAMP benchmark suite (http://stamp.stanford.edu). Overwrite ./common/Defines.common.mk with the attached files to make CC/LD customizable. in ./kmeans, for ./kmeans -m40 -n40 -t0.00001 -i inputs/random-n65536-d32-c16.txt -p 1 : make -f Makefile.seq clean CC='llvm-gcc' LD='llvm-gcc -lm' make -f Makefile.seq -->works, but is slower than gcc (35s vs 16s on my Intel 32b system) CC='llvm-gcc -emit-llvm' LD='llvm-ld -lm' make -f Makefile.seq --> does not work (lot's of...

...ots2, suffix2) d22 = myone(roots2, suffix3) d23 = myone(state, roots) d24 = myone(city, roots) d25 = myone(cityst, roots) d26 = myone(inscompany, roots) d27 = myone(state, roots2) d28 = myone(city, roots2) d29 = myone(cityst, roots2) d30 = myone(inscompany, roots2) d31 = mytwo(state, roots, suffix) d32 = mytwo(city, roots, suffix) d33 = mytwo(cityst, roots, suffix) d34 = mytwo(inscompany, roots, suffix) d35 = mytwo(state, roots, suffix2) d36 = mytwo(city, roots, suffix2) d37 = mytwo(cityst, roots, suffix2) d38 = mytwo(inscompany, roots, suffix2) d39 = mytwo(state, roots, suffix3) d40 = mytwo(city...

..."c32" "c33" "d11" "d12" "d13" [31] "d14" "d21" "d22" "d23" "d24" "d25" [37] "d31" "d32" "d33" "e11" "e12" "e13" [43] "e21" "e22" "e23" "e31" "e32" "e33" [49] "f11" "f12"...

...The program is the KMeans > benchmark > from the STAMP benchmark suite (http://stamp.stanford.edu). > Overwrite ./common/Defines.common.mk with the attached files to make > CC/LD > customizable. > > in ./kmeans, for > ./kmeans -m40 -n40 -t0.00001 -i inputs/random-n65536-d32-c16.txt -p > 1 : > > make -f Makefile.seq clean > > CC='llvm-gcc' LD='llvm-gcc -lm' make -f Makefile.seq > -->works, but is slower than gcc (35s vs 16s on my Intel 32b system) > > CC='llvm-gcc -emit-llvm' LD='llvm-ld -lm' make -f Makefile...

Greetings all- I have a new X4200 that I''m getting ready to deploy. It has four 146 GB SAS drives. I''d like to setup the box for maximum redundancy on the data stored on these drives. Unfortunately, it looks like ZFS boot/root aren''t really options at this time. The LSI Logic controller in this box only supports either a RAID0 array with all four disks, or a RAID 1

...truct static_key *key, bool #else /* __ASSEMBLY__ */ -.macro STATIC_BRANCH_NOP l_yes:req key:req branch:req -.Lstatic_branch_nop_\@: - .byte STATIC_KEY_INIT_NOP -.Lstatic_branch_no_after_\@: +.macro STATIC_JUMP_IF_TRUE target, key, def +.Lstatic_jump_\@: + .if \def + /* Equivalent to "jmp.d32 \target" */ + .byte 0xe9 + .long \target - .Lstatic_jump_after_\@ +.Lstatic_jump_after_\@: + .else + .byte STATIC_KEY_INIT_NOP + .endif .pushsection __jump_table, "aw" _ASM_ALIGN - .long .Lstatic_branch_nop_\@ - ., \l_yes - . - _ASM_PTR \key + \branch - . + .long .Lst...

This series reverts the in-kernel workarounds for inlining issues. The commit description of 77b0bf55bc67 mentioned "We also hope that GCC will eventually get fixed,..." Now, GCC provides a solution. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html explains the new "asm inline" syntax. The performance issue will be eventually solved. [About Code cleanups] I know Nadam

This series reverts the in-kernel workarounds for inlining issues. The commit description of 77b0bf55bc67 mentioned "We also hope that GCC will eventually get fixed,..." Now, GCC provides a solution. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html explains the new "asm inline" syntax. The performance issue will be eventually solved. [About Code cleanups] I know Nadam

Package: xen-utils-4.4 Version: 4.4.1-3 When booting domU's running amd64 jessie, I notice some memory problems with xl. root at xen:~# pmap -x 4121 4121: /usr/lib/xen-4.4/bin/xl create --quiet --defconfig /etc/xen/auto/mail_deb80.cfg Address Kbytes RSS Dirty Mode Mapping 0000000000400000 144 128 0 r-x-- xl 0000000000623000 4 4 4 r---- xl

...ne("state", "roots2") d28 = myone("city", "roots2") d29 = myone("cityst", "roots2") d30 = myone("inscompany", "roots2") d31 = mytwo("state", "roots", "suffix") d32 = mytwo("city", "roots", "suffix") d33 = mytwo("cityst", "roots", "suffix") d34 = mytwo("inscompany", "roots", "suffix") d35 = mytwo("state", "roots", "suffix2")...

On 27 May 2011 19:47, Jim Grosbach <grosbach at apple.com> wrote: > Not exactly. The distinction is clear, it's just not expressed as an > either/or question. Specifically, the code generator considers NEON to be a > proper superset of VFP3. So if it has only VFP3, that's all it will use. If > it has NEON, it assumes it also has VFP3 and can use either. Indeed. >

...ne("state", "roots2") d28 = myone("city", "roots2") d29 = myone("cityst", "roots2") d30 = myone("inscompany", "roots2") d31 = mytwo("state", "roots", "suffix") d32 = mytwo("city", "roots", "suffix") d33 = mytwo("cityst", "roots", "suffix") d34 = mytwo("inscompany", "roots", "suffix") d35 = mytwo("state", "roots", "suffix2")...

Hello all Xen devels, I''m writing howto''s in brazilian portuguese language about Xen-3.3.0 stubdom, pv-grub and others configurations. Following what is written in xen-3.3.0/stubdom/README, I tried start a HVM but without success. When I start the virtual machine calling ''xm create hvmtest'' command, in a few seconds the virtual machine is dead (see

The raspberry Pi2 is an armv7a chip (Cortex-A7), the first stage builds fine with the native g++ (if not a little slowly at 10+ hours), but it crashes at some point with this command line: Program arguments: /home/ben/development/llvm/3.6.0/rc2/Phase2/Release/llvmCore-3.6.0-rc2.install/bin/clang -cc1 -triple armv7-unknown-linux-gnueabihf -emit-obj -disable-free -disable-llvm-verifier

...truct static_key *key, bool #else /* __ASSEMBLY__ */ -.macro STATIC_BRANCH_NOP l_yes:req key:req branch:req -.Lstatic_branch_nop_\@: - .byte STATIC_KEY_INIT_NOP -.Lstatic_branch_no_after_\@: +.macro STATIC_JUMP_IF_TRUE target, key, def +.Lstatic_jump_\@: + .if \def + /* Equivalent to "jmp.d32 \target" */ + .byte 0xe9 + .long \target - .Lstatic_jump_after_\@ +.Lstatic_jump_after_\@: + .else + .byte STATIC_KEY_INIT_NOP + .endif .pushsection __jump_table, "aw" _ASM_ALIGN - .long .Lstatic_branch_nop_\@ - ., \l_yes - . - _ASM_PTR \key + \branch - . + .long .Lst...

...truct static_key *key, bool #else /* __ASSEMBLY__ */ -.macro STATIC_BRANCH_NOP l_yes:req key:req branch:req -.Lstatic_branch_nop_\@: - .byte STATIC_KEY_INIT_NOP -.Lstatic_branch_no_after_\@: +.macro STATIC_JUMP_IF_TRUE target, key, def +.Lstatic_jump_\@: + .if \def + /* Equivalent to "jmp.d32 \target" */ + .byte 0xe9 + .long \target - .Lstatic_jump_after_\@ +.Lstatic_jump_after_\@: + .else + .byte STATIC_KEY_INIT_NOP + .endif .pushsection __jump_table, "aw" _ASM_ALIGN - .long .Lstatic_branch_nop_\@ - ., \l_yes - . - _ASM_PTR \key + \branch - . + .long .Lst...

...(N1) d8(N1) d9(N1) d10(N1) d11(N1) d12(N1) d13(N1) > > d14(N1) d15(N1) d16(N1) d17(N2) d18(N1) d19(N1) d20(N1) . > > > > - RECORD TYPE 'B'. > > - DATA LIST LIST / i1(A1) d21(N1) d22(N1) d23(N1) d24(N1) d25(N1) > > d26(N1) d27(N1) d28(N1) d29(N1) d30(N1) d31(N1) d32(N1) d33(N1) > > d34(N1) d35(N1) d36(N1) d37(N1) d38(A37) d39(N1) d40(N1) . > > > > - RECORD TYPE 'C'. > > - DATA LIST LIST / i2(A1) d41(N1) d42(N1) d43(N1) d44(N1) d45(N1) > > d46(N1) d47(N1) d48(N1) d49(N1) d50(N1) d51(N1) d52(N1) d53(N1) > > d54(N1) d55...

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding