similar to: QEMU on solaris/sparc to lunch linux

Ralph Corderoy wrote: > Hi Tilmann, > > >> Nevertheless, it is unlikely that llvm-qemu will ever be much faster >> than regular qemu (by replacing its code generator completely, which >> it currently does), which is due to the fact that regular qemu has a >> very lightweight code generator (it basically only copies blocks of >> memory and performs some

Hi Tilmann, > Nevertheless, it is unlikely that llvm-qemu will ever be much faster > than regular qemu (by replacing its code generator completely, which > it currently does), which is due to the fact that regular qemu has a > very lightweight code generator (it basically only copies blocks of > memory and performs some patching to them and only does static > register

Hello > I'm implementing an LLVM backend for qemu-arm (by creating an ARM frontend > for LLVM - from what I understand a slightly different approach than the > original llvm-qemu project) I don't see the difference so far. Could you please explain? > and I've got to the point where I have to deal with Qemu's use of global register variables. Why? The whole point of

> > > Are there particular reasons why you want to translate to LLVM IR? > (E.g. the authors of the paper wanted to be able to use KLEE with > machine code) > > Hi Tilmann I want to do the same. Using KLEE with machine code. With such a framework, I could try to do the same that what is explained here :

Hi all, I'm implementing an LLVM backend for qemu-arm (by creating an ARM frontend for LLVM - from what I understand a slightly different approach than the original llvm-qemu project) and I've got to the point where I have to deal with Qemu's use of global register variables. From what I've read LLVM doesn't support GCC style register variables and the workaround was to

Anton Korobeynikov wrote: > Hello > >> I'm implementing an LLVM backend for qemu-arm (by creating an ARM frontend >> for LLVM - from what I understand a slightly different approach than the >> original llvm-qemu project) > I don't see the difference so far. Could you please explain? Again, from what I understand, llvm-qemu worked by emitting LLVM IR from QEMU

I have uploaded a current source drop from the qemu subversion repository, to the download area. Additionally, there is a new Kernel kqemu module that will allow a 32-bit guest to run on a 64-bit host. The current source base uses a different code generator from the orignial Dyngen one. The new one is called "TCG" for "The Code Generator" and is supposed to fix the

Not sure if this is the list for posting questions like this but please let me know. We are using Mongrel 0.13.4, Mongrel Cluster 0.2.1 with Rails 1.2.2 with 3 different mongrel processes running in the cluster. All appears to be well for hours and then one of the mongrel processes appears to hang and all incoming requests to that process timeout. The requests are not logged in the rails log,

I''ve been writing via tar to a pool some stuff from backup, around 500GB. Its taken quite a while as the tar is being read from NFS. My ZFS partition in this case is a RAIDZ 3-disk job using 3 400GB SATA drives (sil3124 card) Ever once in a while, a "df" stalls and during that time my io''s go flat, as in : capacity operations bandwidth pool

Hello. My problem contain in starting cs 1.6.through wine shows up welcome screen but in the same time everything hangs up and there are no other options in menu. Steam starts correctly, works smooth. When cs 1.6 hangs up i can easily switch virtual desktop. Let me add that first time problem shows up today morning after update (really cant remember what i updated/upgraded but it was only one

Caught a message in /var/log/messages about the time Nouveau went out to lunch: Oct 22 19:40:12 one kernel: [drm] nouveau 0000:06:00.0: EvoCh 0 Mthd 0x0000 Data 0x00000400 (0x1002 0x01) This was with kernel 2.6.38.8-server-10.mga on Mageia 1, and I don't see any other version number in modinfo output. The graphics card is an Asus ENGT430. Motherboard is an Asus P6T6 WS Revolution. CPU is

It seems that it would be more convenient for some of the folks working on the Toronto area to meet for lunch instead of an after work social. As an experiment, lets try to host the fist one: * Where: Tone Sushi (414 Queen W). They do have some vegetation or non-fish options. * When: Next Tuesday (17th) at 12:00. It is a similar idea to the socials, just less drinks (at this one at least :-) ).

Today I had channel 1 on my TDM400 go to sleep, verified by pluggin in known good telco lines in various combinations on channel 1 through 4 - problem is channel 1, not anything external. So after seeing lots of stuff on the list re: TDM400's I power cycled, removed board and let linux say nothing's home, replaced board, told linux to ignore it etc. No OS/asterisk/etc changes made on

Greetings, I'm organizing summer econometrics lunch meetings to discuss thesis work. The first meeting will be this friday July 18 12-1pm in the conference room on the third floor of Wohlers. The first talk will be by Lingjie Ma Control Variate Estimation of Structural Quantile Regression Models url: www.econ.uiuc.edu/~roger/my.html Roger Koenker email rkoenker@uiuc.edu Department of

Reminder for Mac Puppeteers going to WWDC How about we meet for lunch at noon on Tuesday. Let''s try to get the table closet to the Odwalla refrigerator, just for reference. We can get more specific on this list on the 8th after we verify the set up. I might even get there a little earlier and put down "reserved" tags. --- Thank you, Allan Marcus Solutions Architect Central

Hi, Has anyone come across this problem please? Couldn''t see it in the list archives: This is the error message generated by make tools (run twice, so the successful object creation has been removed.) Thanks Install prefix /usr BIOS directory /usr/share/qemu binary directory /usr/bin Manual directory /usr/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path

Source: xen Version: 4.1.4-4 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value

Hyper-V SynIC (synthetic interrupt controller) device implementation. The implementation contains: * msr's support * irq routing setup * irq injection * irq ack callback registration * event/message pages changes tracking at Hyper-V exit * Hyper-V test device to test SynIC by kvm-unit-tests Andrey Smetanin (7): standard-headers/x86: add Hyper-V SynIC constants target-i386/kvm: Hyper-V

Hyper-V SynIC (synthetic interrupt controller) device implementation. The implementation contains: * msr's support * irq routing setup * irq injection * irq ack callback registration * event/message pages changes tracking at Hyper-V exit * Hyper-V test device to test SynIC by kvm-unit-tests Andrey Smetanin (7): standard-headers/x86: add Hyper-V SynIC constants target-i386/kvm: Hyper-V

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are