similar to: 2.6.25.* domU i386 baremetal/xen dual boot kernels (Fedora 8)

Displaying 20 results from an estimated 9000 matches similar to: "2.6.25.* domU i386 baremetal/xen dual boot kernels (Fedora 8)"

2013 Sep 22
0
UEFI boot - no console will be available to OS
I''m trying to run Xen on Arch Linux with UEFI boot. I followed the steps for Xen in the Arch Linux Wiki https://wiki.archlinux.org/index.php/Xen I get the following when attempting to boot: Loading Xen 4.2.2 ... WARNING: no console will be available to the OS Loading Linux linux ... Loading initial ramdisk ... Unfortunately there is no console so I cannot determine what has gone wrong,
2015 Jul 03
2
Fedora 21 extlinux 6.03 boot failure
Hi, On Fri, Jul 03, 2015 at 06:41:41PM +0300, Ady via Syslinux wrote: > Are the other systems (those that are booting OK) also attached to a serial > console? Yes. > Is there any other output method available (I mean, other than the serial console)? I can also attach a VGA display to the system, but the serial console output is nice because it's logged. > What happens when
2011 Nov 08
2
[LLVMdev] LLVM JIT on a Baremetal x86 Machine !!!
Hi, First question: "/module" is mapped to a special file that reads a kernel module passed in by the bootloader. Much like GRUB, kiwi's bootloader loads a kernel and can load one or more extra files into memory. These are passed to the kernel. The horizon kernel expects one file, which it makes accessible at "/module". This should be set up to be whatever you set
2011 Nov 08
0
[LLVMdev] LLVM JIT on a Baremetal x86 Machine !!!
Hi James, I have two questions for you. Firstly, what is the role of 'module' in init.cc? I can see that its being treated like it is a 'bytecode' file, as we open it and then pass it to the ByteCoder and eventually construct llvm module from it. Like In file init.cc, line:121 FILE *stream = fopen("/module", "rb"); ... fread(c, 1, sz,
2011 Nov 03
1
[LLVMdev] LLVM JIT on a Baremetal x86 Machine !!!
Hi Mian, Looking at the runlog, everything seems fine until LLVM attempts to use lseek() on a file. You see the PANIC because Horizon hasn't implemented lseek yet. Obviously the version of GlibC I was using does not use lseek in that circumstance, but yours does. You just need to implement lseek :) Cheers, James -----Original Message----- From: Mian M. Hamayun
2019 Aug 07
2
Compiling compiler-rt for baremetal CortexM on Ubuntu Linux
Hello, I want to build LLVM/Compiler-rt for baremetal targets like Cortex-M3. By adopting CMake options from http://llvm.1065342.n5.nabble.com/llvm-dev-Compiling-for-baremetal-ARMv4-on-Ubuntu-Linux-tp124226p124500.html, I can only build "libclang_rt.builtins-x86_64.a" in lib/linux, but what I want to build is "libclang_rt.builtins.arm.a". My CMake options are: cmake -G Ninja
2010 May 28
1
Multi-partition domain not recognizing extra partitions
Hello, I have been having an annoying problem with a multi-partition domain. This domain has a separate partition for : /, /home, /usr, /var, /tmp and /data. I created it using xen-tools and the custom partitionning scheme option. The partitions are inside a LVM. When I boot the domain, it mounts the / and swap partition but none of the others. Therefore it doesn''t work... I get the
2004 Oct 07
1
x86 vs. x86_64 detection proof of concept patch (try two)
Greetings all, Sorry, resending this with the attachment inline. First of all, a disclaimer: Please forgive my horrible assembly code. This is just a quick munging of code to achieve x86 versus x86_64 detection within pxelinux. So please look at it as a proof of concept and not a real piece of code. :) For example it only works on pxelinux and has no thought for extending it beyond simple x86
2014 Jun 23
4
[LLVMdev] [cfe-dev] [PATCH] triples for baremetal
Hi Jonathan, The main issue with your patch is that it can change user expected behaviour, and I can't tell you what is the expected behaviour in Darwin or BSD. If people usually use "unknown" in triples, this will break their builds. If not, this could break the build of someone who does. My advice is to create a "default" mechanism for the affected targets, something
2017 Sep 11
2
Using source-based code coverage on baremetal
I think that this proposal would be very useful, and I will describe our experiences of trying to do this for our embedded bare-metal target. Recently we implemented support for just the '-fprofile-instr-generate' option and the 'compiler-rt/lib/profile' sources, and added the following to our LD scripts: /* Append the LLVM profiling sections */ . = ALIGN(4);
2011 Nov 09
0
[LLVMdev] LLVM JIT on a Baremetal x86 Machine !!!
Hi James, Thanks again for bearing with me, you have been very helpful. I have got the problem fixed. In fact I needed to override the 'LSeek' implementation of SpecialFile in SpecialModule class as well. The log for the working example is attached, just as a reference. Now one more thing, when the build system creates the ISO9660 CD-ROM Image, it executes the following commands:
2009 Jul 18
1
GlusterFS & XenServer Baremetal
Hello, What is for you the best GlusterFS scenario in using XenServer (i'm not talking about Xen on a linux but XenServer baremetal) for a web farm (Apache-Tomcat) ? I were thinking of using ZFS as the filesystem for the different nodes. The objectives/needs : * A storage cluster with the capacity equal to at least 1 node(assuming all nodes are the same). * being able to lose/take down any
2014 Jun 19
2
[LLVMdev] [PATCH] triples for baremetal
Eric, Attached are patches for llvm and clang that implement this. I've made 'none' a component that must be added explicitly (i.e. don't turn arm-eabi into arm--none-eabi, but rather turn it into arm--unknown-eabi) to try to reduce surprises. It also keeps the normalization logic a bit simpler than it would otherwise have to be. SPIR triples were one place where I was
2017 Sep 06
5
Using source-based code coverage on baremetal
Hi all, I think using code coverage on baremetal has come up once or twice on llvmdev, but I don't think anyone has actually written up how the workflow works, or what issues come up.  This description is based on work done together with my colleague Weiming Zhao. By "baremetal" here, I mean an embedded environment without an operating system.  We specifically used a ARM target
2013 Jun 19
1
Fedora 18 dom0, no video?
Hi all. I''ve got a situation with Fedora 18 on a dual Xeon E5506 box, 16GB RAM, Tyan S7002 motherboard with the latest BIOS. Because of all the issues, I''m starting to think maybe there''s something wrong with the box itself, maybe something strange going on with the BIOS or mobo resources. Although this box was in service without incident for about 2 years prior. I
2017 Oct 31
3
Cross compiling for Baremetal ARM without using GCC
Dear LLVM developers, Hello, I'm trying to find a way of cross-compiling my c code against Baremetal Cortex-M device (so target triple will be arm-none-eabi) only using LLVM/Clang, and not using anything from GNU (ld or libc). I'm doing this to know which one of LLVM/clang and GCC produces smaller flash image size because saving flash is a big deal in our projects. 1) When I just follow
2011 Oct 26
3
[LLVMdev] LLVM JIT on a Baremetal x86 Machine !!!
Dear All, I have tested a few examples of LLVM-JIT Framework on Linux x86 Machine. So generating functions on the fly and then executing them is OK on linux i.e. i686-pc-linux-gnu My question is: Can we use the LLVM-JIT on a baremetal x86 machine ? Actually my target is a virtual machine, and I need some dynamic code generation support. I intend to use LLVM-JIT (if possible) for this
2014 Jun 17
4
[LLVMdev] triples for baremetal
[+llvmdev, -llvm-dev] (Oopsies, llvmdev doesn't have a hyphen in it like all the others do) On 6/17/14, 10:45 AM, Jonathan Roelofs wrote: > [+llvm-dev, cfe-dev] > > Was "Re: [PATCH] ARM: allow inline atomics on Cortex M" > > On 6/17/14, 10:42 AM, Jonathan Roelofs wrote: >> >> >> On 6/17/14, 9:35 AM, Renato Golin wrote: >>> On 17 June 2014
2015 Mar 02
0
installing C7 on a laptop with Win7, dual boot
On 03/02/2015 02:06 AM, Fred Smith wrote: > Hi all! > > I've just installed C7 on my netbook that already contained Win7 (and > also Fedora 19, which the C7 is intended to replace). The Fedora installer > had found the windows installation and it appeared in the grub menu, > and was bootable and worked fine. > > The C7 installer did not put the windows installation
2004 Oct 05
0
x86 vs. x86_64 detection proof of concept patch
Greetings all, First of all, a disclaimer: Please forgive my horrible assembly code. This is just a quick munging of code to achieve x86 versus x86_64 detection within pxelinux. So please look at it as a proof of concept and not a real piece of code. :) For example it only works on pxelinux and has no thought for extending it beyond simple x86 versus x86_64 architectures. I had the need for