similar to: MMIO emulation failed & successful reboot

Hello list, Using the mainline 3.5-rc6 kernel and yesterday''s xen-unstable, I''m having trouble passing in some PCI devices. Everything else works smoothly. Attached are some of the relevant logs and configurations. I did notice from the qemu logs that all the problematic devices have "IRQ type = INTx" whereas those that are working have "IRQ type =

Hi Johannes, Actually, I'm working in the same scenario, i.e. configure + make of a benchmark/program/library like you said. I've got your point of using this script as a replacement to generate .bc files instead of a executable. That's truly helpful and has already answered my original question. Now I'm actually moving a step further. Take the same example in your reply, say, if

Hi Johannes, By following your directions, I can use your script as is to produce the .bc file now. Here's my command line for compiling s_sin.c into s_sin.bc file and the output: command line: ~/Downloads/newlib-2.1.0/newlib/libm/mathfp » python ~/llvm_link.py s_sin.c -I../common/ -I../../libc/include/ -o s_sin.bc output: Initiate CLANG (/path-to-clang): Options: 's_sin.c

Hello, I run into a situation where I need to provide the library functions, such as sqrt() from <math.h> and rand() from <stdlib.h>, in the format of LLVM IR bitcode files. Then I can try to link the bitcode of my program against these library bitcode files to formulate a holistic bitcode file. However, these library functions are only available in object format. And the source

Thanks for your reply, Yabin. Actually I'm trying to come up with a way to translate any source code into bitcode format. So some of them are not necessarily LLVM intrinsics. Also it seems like that dynamically loading the library by dlopen() is for loading object files, not .bc files. So it might not be useful for library in .bc files. Anyway, I've found a way to solve this by manually

- we used the C4/C5 (first prefix) byte instead of the apparent ModR/M one as the second prefix byte - early decoding normalized vex.reg, thus corrupting it for the main consumer (copy_REX_VEX()), resulting in #UD on the two-operand instructions we emulate Also add respective test cases to the testing utility plus - fix get_fpu() (the fall-through order was inverted) - add cpu_has_avx2,

Good tips. Although I have used llvm-link to merge .bc files together, I guess -flto could optimize the resultant .bc file further. As for the assembly, yes it is an issue. Anyway, I'll try to address those sources which are available for being translated into .bc first. Thanks for your advice, Tim. On Mon, Sep 15, 2014 at 2:55 PM, Tim Northover <t.p.northover at gmail.com> wrote:

The Quantitative Decision Strategies group at Janssen Research & Development, Johnson & Johnson, is looking for a candidate to represent QDS in Beijing, China in the subsidiary company of Xian-Janssen Pharmacetical Ltd. The basic requirements for this candidate are 1) 3+ years experience in a quantitative field, but not necessarily pharmaceutical; 2) PhD in statistics or related field

Clone the existing movq emulation to also support the most fundamental SIMD FP moves. Extend the testing code to also exercise these instructions. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/tools/tests/x86_emulator/test_x86_emulator.c +++ b/tools/tests/x86_emulator/test_x86_emulator.c @@ -629,6 +629,60 @@ int main(int argc, char **argv) else

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, While updating my xen package today, I was prompted with a config file conflict. --- /etc/xen/scripts/hotplugpath.sh 2013-04-28 01:51:20.899778510 +0800 +++ /etc/xen/scripts/hotplugpath.sh.dpkg-new 2013-04-19 19:39:55.000000000 +0800 @@ -1,12 +1,10 @@ SBINDIR="/usr/sbin" BINDIR="/usr/bin"

I''ve been trying to pass through a GPU to a domU, so far with a lot of trouble but finally a success. PCI passthrough works, I''ve had the usb hubs work successfully. Today I tried to pass through my ATI card to an ubuntu hvm domU with no gfx_passthru and got this: [...] (XEN) memory_map:add: dom14 gfn=f3040 mfn=f7c40 nr=4 (XEN) memory_map:remove: dom14 gfn=f3040 mfn=f7c40 nr=4

On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote: > Hello, > > In my testing of crosvm[1] with Linux 4.4.175, I am observing failures > on a 'kevin' Chromebook (RK3399) device - the guest kernel does not > even get to the point of printing its first messages, and the host > seems to be spinning at 100% CPU in KVM_RUN. > > I narrowed this down to the

On 28/02/2019 08:49, Marc Zyngier wrote: > On Thu, 28 Feb 2019 08:16:05 +0000, > Greg KH <gregkh at linuxfoundation.org> wrote: > > Hi both, > >> >> On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote: >>> Hello, >>> >>> In my testing of crosvm[1] with Linux 4.4.175, I am observing failures >>> on a 'kevin'

> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > Gerd Hoffmann > Sent: 17 May 2006 07:43 > To: Petersson, Mats > Cc: xen-devel@lists.xensource.com; xen-changelog@lists.xensource.com > Subject: Re: [Xen-devel] RE: [Xen-changelog] Fix MOVS > instruction emulation for HVM MMIO. >

Hello, In my testing of crosvm[1] with Linux 4.4.175, I am observing failures on a 'kevin' Chromebook (RK3399) device - the guest kernel does not even get to the point of printing its first messages, and the host seems to be spinning at 100% CPU in KVM_RUN. I narrowed this down to the 4.4 stable backport of "arm64: KVM: Skip MMIO insn after emulation" - with this patch

Hello, In my testing of crosvm[1] with Linux 4.4.175, I am observing failures on a 'kevin' Chromebook (RK3399) device - the guest kernel does not even get to the point of printing its first messages, and the host seems to be spinning at 100% CPU in KVM_RUN. I narrowed this down to the 4.4 stable backport of "arm64: KVM: Skip MMIO insn after emulation" - with this patch

On Thu, 28 Feb 2019 08:16:05 +0000, Greg KH <gregkh at linuxfoundation.org> wrote: Hi both, > > On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote: > > Hello, > > > > In my testing of crosvm[1] with Linux 4.4.175, I am observing failures > > on a 'kevin' Chromebook (RK3399) device - the guest kernel does not > > even get to the

On Thu, 28 Feb 2019 08:16:05 +0000, Greg KH <gregkh at linuxfoundation.org> wrote: Hi both, > > On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote: > > Hello, > > > > In my testing of crosvm[1] with Linux 4.4.175, I am observing failures > > on a 'kevin' Chromebook (RK3399) device - the guest kernel does not > > even get to the

Hi Everybody I've got a weird problem. I am running one Asterisk system on a dual processor box. This box mostly do VoIP only but it has a Fritz PCI ISDN card installed with latest drivers. Dialing out through the ISDN cards from an internal Snom phone works fine and so does dialing in. Except - if I load the ztdummy module (for IAX channels) the capi drivers starts acting up. It is hard

Hello, I've been playing around with two generic X100P analog cards to create a proof-of-concept system before we go ahead and hook up a PRI. I'm running into a reproducible problem with sound quality of bridged calls, and am hoping someone will be able to point me in the right direction. I have in my dial plan a _9. extension so outgoing calls can be made... the first thing is