similar to: [LLVMdev] linker script

Thanks. I actually checked the IR code generated, it seems inline assembly is being handled correctly. The preprocessing is also being done correctly. Here is the asm-offsets.i file snippet.. ... builtin_offsetof(struct crypto_tfm,__crt_ctx))); asm volatile("\n->" : : ); asm volatile("\n->" "__NR_syscall_max" " %0 " "sizeof(syscalls) - 1"

Hello, I've recently started working on compiling UML with LLVM: the goal is to produce a bitcode version of vmlinux. With some tweaks to the build process, I can use: make ARCH=um CROSS_COMPILE=llvm- CFLAGS="-emit-llvm" to produce vmlinux bitcode. The question is with respect linker script support. Since llvm-ld does not support linker scripts--please correct me if I'm

Thanks for the help. I've a couple of questions though: How does LLVM deal with inline assembly? I'm trying to compile kernel and I get this error probably because LLVM is not able to handle inline assembly. I'm using LLVM-2.3 code snippet from "arch/x86_64/kernel/asm-offsets.c" .... #define DEFINE(sym, val) \ asm volatile("\n->" #sym " %0 "

On Sep 27, 2008, at 4:34 PM, Ashish Bijlani wrote: > Thanks for the help. I've a couple of questions though: > > How does LLVM deal with inline assembly? It's been implemented piece by piece on an as-needed basis. At this point most of the things people actually use should work. llvm-gcc has seen the Linux kernel, so most usages in there ought to work. The symptoms here

does that mean .o generated with gcc (.c -> .s and .s -> .o) will not contain llvm ir? i meant, final kernel bitcode ir arch independent and can be JIT with any arch-specific backend. Is it not the case? thanks, ashish On Sat, Sep 27, 2008 at 10:43 PM, Andrew Lenharth <andrewl at lenharth.org> wrote: > On Sat, Sep 27, 2008 at 8:08 PM, Ashish Bijlani > <ashish.bijlani at

No, this is not the case. Just because you compile something to LLVM IR does not make the thing you compiled work on every architecture. You may even be able to retarget it to any architecture (it depends), but this in no way means the result will *actually work*. The LLVM IR generated by llvm-gcc is very architecture dependent. Theoretically you could make a C compiler that was mostly C

Hi, I''ve a quad-core x86_64 machine (Intel Xeon), with sse/mmx support. However, I want to disable sse/mmx support from HVM guests. How can I do this? Also, is it reasonable to expect illegal instruction fault in non-root VMX mode if a guest VM runs an application with sse/mmx instructions? Thanks, Ashish _______________________________________________ Xen-devel mailing list

Hi, I'm trying to compile linux-2.6.23.16 with llvm-2.3. Is it at all possible? I get "Not an ELF" error. I pass "-emit-llvm" option to spit LLVM IR, which can be JITed at runtime $ make CROSS_COMPILE=llvm- CFLAGS="-O2 -emit-llvm" Error: not ELF make[2]: *** [scripts/mod/elfconfig.h] Error 1 make[1]: *** [scripts/mod] Error 2 make: *** [scripts] Error 2 using

hello, does lustre support OSD T10 standard? Can it be used with IBM''s/Intel''s OSD initiator and target? Thanks, Ashish -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071128/c2de31a6/attachment-0002.html

On Sat, Sep 27, 2008 at 8:08 PM, Ashish Bijlani <ashish.bijlani at gmail.com> wrote: > If I use GCC to generate asm-offsets.s file, then the build system go > ahead but fails when it generates .so files as Andrew pointed out. You have to generate this with gcc. .c -> .s and .s -> .o need gcc, .c -> .o can use llvm-gcc. The combination has to be fixed up in final linking.

On Fri, Sep 26, 2008 at 9:19 PM, Ashish Bijlani <ashish.bijlani at gmail.com> wrote: > Hi, > > I'm trying to compile linux-2.6.23.16 with llvm-2.3. Is it at all > possible? Yes, but it requires significant hacking, and the result for 2.6 is a mostly bitcode kernel with a few userspace shared libraries linked in as objcode (yes, the kernel builds .so files and includes them

I plan to use virtualization infrastructure to JIT VM Kernel Code. Michael Engel has done that in the past to have dynamic aspect in the Kernel: http://llvm.org/pubs/2005-03-14-ACP4IS-AspectsKernel.pdf He used L4 based Hypervisor and Virtual Machines. Can this not be done or am I missing something? -Ashish On Sat, Sep 27, 2008 at 3:13 AM, Török Edwin <edwintorok at gmail.com> wrote: >

Thanks to Andrew for pointing these out. This patch moves the parvirtprobe section into .init.data: it's only used in very very early boot, and for similar reasons, puts lguest_maybe_init and lguest_memory_setup in init.text. As well as fixing some warnings, this frees up a tiny bit more memory. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r ecec388180b2

Thanks to Andrew for pointing these out. This patch moves the parvirtprobe section into .init.data: it's only used in very very early boot, and for similar reasons, puts lguest_maybe_init and lguest_memory_setup in init.text. As well as fixing some warnings, this frees up a tiny bit more memory. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r ecec388180b2

Hello, I've recently started working on compiling UML with LLVM: the goal is to produce a bitcode version of vmlinux. With some tweaks to the build process, I can use: make ARCH=um CROSS_COMPILE=llvm- CFLAGS="-emit-llvm" to produce vmlinux bitcode. The question is with respect linker script support. Since llvm-ld does not support linker scripts--please correct me if I'm

Hi, I''m trying to run guest pv vm on my machine running xen-unstable (xen-4.0.0-rc3.pre + linux-2.6-pvops). However, I get blktap error: " sudo xm create -c xmexample Using config file "./xmexample". Error: Failed to create device. stdout: unrecognized child response stderr: Check that target "/home/ashish/xen/hd.img" exists and that blktap2 driver

This patch updates x86_64 linker script to pack any .note.* sections into a PT_NOTE segment in the output file. To do this, we tell ld that we need a PT_NOTE segment. This requires us to start explicitly mapping sections to segments, so we also need to explicitly create PT_LOAD segments for text and data, and map the sections to them appropriately. Fortunately, each section will default to its

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]? I don't have a usable Xen setup. Also, I'd appreciate a review of patches 4 and 5 from some

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]? I don't have a usable Xen setup. Also, I'd appreciate a review of patches 4 and 5 from some

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]? I don't have a usable Xen setup. Also, I'd appreciate a review of patches 4 and 5 from some