similar to: issue using SRIOV "Unable to start - perhaps the PF driver is not up yet", while PF driver is actually up

Hi, trying to pass through a intel x520 VF on a Dell R620, I''m getting in domU: [ 58.162639] pci 0000:00:00.6: address space collision: [mem 0xd500c000-0xd500ffff 64bit pref] conflicts with System RAM [mem 0x00100000-0x176ffffff] [ 58.162654] pcifront pci-0: Could not claim resource 0000:00:00.6/0! Device offline. Try using e820_host=1 in the guest config. and in dom0 (XEN)

Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of

Guest needs the ability to enable and disable MSI-X interrupts by setting the MSI-X control bit, for a passed-through device. Guest is allowed to write MSI-X mask bit only if Xen *thinks* that mask is clear (interrupts enabled). If the mask is set by Xen (interrupts disabled), writes to mask bit by the guest is ignored. Currently, a write to MSI-X mask bit by the guest is silently ignored. A

Hello, to compile kexec-tools statically against klibc we still need a patch for socket.h, otherwise: | kexec/ifdown.c:46:16: error: 'SIOCGIFCONF' undeclared (first use in this function) | kexec/ifdown.c:46:16: note: each undeclared identifier is reported only once for each function it appears in | kexec/ifdown.c:65:18: error: 'SIOCSIFFLAGS' undeclared (first use in this

On 1/21/2013 2:01 AM, Óscar Fuentes wrote: > Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > >> I was using the find_package(LLVM llvm/share/llvm/cmake) and >> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get >> the libraries to link against. This works well for the libLLVM* >> libraries, but how do I implement similar find stuff for

Resending :(. Any pointers? tia On 5/21/2012 2:46 PM, Ashok Nalkund wrote: > On 5/21/2012 11:15 AM, Nick Lewycky wrote: >> Ashok Nalkund wrote: >>> Resending, any pointers? I demangled the symbol and it turns out to be: >>> std::__1::locale::use_facet(std::__1::locale::id&) const >> >> My guess is that you've got a .bc file produced on a mac using

yeah i m concerned about jit compilation time.. On Sun, Jun 30, 2019 at 12:57 PM Praveen Velliengiri < praveenvelliengiri at gmail.com> wrote: > Yes I think so.. Could you please tell me in which context (compile time > improvement)? That is whether you are interested in knowing whether having > ORC instead of MCJIT, will increase your LLVM Build time or you are > concerned

Use the -I<install path>/include . This directory <install path>/include should look something like: clang/ clang-c/ llvm/ llvm-c/ HTH ashok On 7/9/2012 3:15 PM, NY Knicks Fan wrote: > I downloaded the 3.1 LLVM and Clang sources. > > I followed the directions at: http://clang.llvm.org/get_started.html > > I am able to use Clang to compile stuff, but I could

On 6/20/2012 11:55 PM, Ashok Nalkund wrote: > On 6/20/2012 11:00 PM, "C. Bergström" wrote: >> On 06/21/12 12:47 PM, Chandler Carruth wrote: >>> On Wed, Jun 20, 2012 at 5:13 PM, Nick Lewycky <nlewycky at google.com >>> <mailto:nlewycky at google.com>> wrote: >>> >>> Is there anybody who is certain that our autoconf dependency

The "make install" should collect everything into your <install path>. The <install path> will then have bin, lib and include dirs. On 7/9/2012 3:52 PM, NY Knicks Fan wrote: > Hi Ashok, > > The documentation suggests that I put clang inside of llvm/tools and so > I have two separate include directories. I tried both of them and > neither worked: > > $

Hi, LLVM/Clang version: 3.2svn (r156975). I have a bitcode file that I'm trying to load/execute using lli as below but it reports an error about unresolved symbol: > LLVM ERROR: Program used external function '_ZNKSt3__16locale9use_facetERNS0_2idE' which could not be resolved! > lli: /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/lib/Support/ThreadLocal.cpp:54:

hi I''m in need of help to proceed in my project which is titled,"Performance improvements for Patchless lustre client" can u tell me the step by step approach in setting up a patchless lustre client in a high end system. Waiting 4 ur reply thanks and regards, Ashok Bharat -------------- next part -------------- An HTML attachment was scrubbed... URL:

Looks like your make/install is incomplete wrt clang. I follow the instuctions for checking out the sources but build using cmake instead of configure: > cmake -G ""Unix Makefiles" -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE="Release" -DCMAKE_INSTALL_PREFIX="../bin" ../llvm > make install This builds and installs llvm+clang in the bin

Ashok Nalkund wrote: > > Resending :(. Any pointers? Fundamentally the issue is that the system linker is supposed to define __dso_handle when linking, but since there is no system linker between your build of the .bc files and running lli, nobody has defined it. It seems reasonable to me that lli should define __dso_handle if it's declared in the module. You could module

This is just standard behavior of the Python interpreter. The files are just a cache (it is not the sources being modified) and also won't be written if the source tree is made read only, and shouldn't cause a problem in practice. - Daniel On Jan 22, 2013, at 0:02, Duncan Sands <baldrick at free.fr> wrote: > I would have expected the .pyc files to go in the objects directory.

Thanks Praveen. Is it suitable for LLVM 7.0.1 ? Apart from flexibility, do we see any compile time improvements as well with ORC? On Sun, Jun 30, 2019 at 12:31 PM Praveen Velliengiri < praveenvelliengiri at gmail.com> wrote: > MCJIT hopefully will be removed in subsequent releases. I think the last > release version is more suitable. > > On Sun, 30 Jun 2019 at 11:45, Ashok

Ashok Nalkund wrote: > Resending, any pointers? I demangled the symbol and it turns out to be: > std::__1::locale::use_facet(std::__1::locale::id&) const My guess is that you've got a .bc file produced on a mac using libc++ (hence the ::_1 part) and you're trying to run it on linux with libstdc++ (which doesn't use inline namespaces, the '::_1::' part). That

Hello, When running an application developed in Windows, the following error occurs. Any thoughts? Does it have something to do with directx support for wine? fixme:d3d:IWineD3DImpl_CreateDevice (0x7ff41940) Incomplete stub for d3d8 fixme:d3d_caps:IDirect3D8Impl_FillGLCaps found GL_VERSION ("1.2 (1.5 Mesa 6.2.1)")->(0x00000009) fixme:d3d_caps:IDirect3D8Impl_FillGLCaps found

Hi All, I'm using LLVM/Clang 3.1 release. I first compiled llvm/clang using GCC per the instructions on the web with cmake. I then compiled libc++ per the instructions on the web. I then tried to compile llvm/clang with previously compiled clang and libc++ using "-std=c++0x -stdlib=libc++" flags. But the compilation fails at: > [ 58%] Building CXX object

On 1/21/2013 10:25 AM, Ashok Nalkund wrote: > On 1/21/2013 2:01 AM, Óscar Fuentes wrote: >> Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: >> >>> I was using the find_package(LLVM llvm/share/llvm/cmake) and >>> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get >>> the libraries to link against. This works well for the