search for: x86info

The following makes 'x86info -r' dump hypervisor leaf cpu ids (for kvm this is signature+features) when running in a vm. On the guest we see the signature and the features: eax in: 0x40000000, eax = 00000000 ebx = 4b4d564b ecx = 564b4d56 edx = 0000004d eax in: 0x40000001, eax = 0100007b ebx = 00000000 ecx = 00000000 edx =...

The following makes 'x86info -r' dump hypervisor leaf cpu ids (for kvm this is signature+features) when running in a vm. On the guest we see the signature and the features: eax in: 0x40000000, eax = 00000000 ebx = 4b4d564b ecx = 564b4d56 edx = 0000004d eax in: 0x40000001, eax = 0100007b ebx = 00000000 ecx = 00000000 edx =...

On Mon, Apr 30, 2012 at 11:43:19AM +0300, Gleb Natapov wrote: > On Sun, Apr 29, 2012 at 01:10:21PM +0300, Michael S. Tsirkin wrote: > > The following makes 'x86info -r' dump kvm cpu ids > > (signature+features) when running in a vm. > > > > On the guest we see the signature and the features: > > eax in: 0x40000000, eax = 00000000 ebx = 4b4d564b ecx = 564b4d56 edx = 0000004d > > eax in: 0x40000001, eax = 0100007b ebx = 0000000...

On Mon, Apr 30, 2012 at 11:43:19AM +0300, Gleb Natapov wrote: > On Sun, Apr 29, 2012 at 01:10:21PM +0300, Michael S. Tsirkin wrote: > > The following makes 'x86info -r' dump kvm cpu ids > > (signature+features) when running in a vm. > > > > On the guest we see the signature and the features: > > eax in: 0x40000000, eax = 00000000 ebx = 4b4d564b ecx = 564b4d56 edx = 0000004d > > eax in: 0x40000001, eax = 0100007b ebx = 0000000...

...resentable. I don't know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others attempting to comprehend LLVM. PNG attached; dot file follows. digraph G { ipo [shape=box,style=filled,color=olivedrab1]; ipa [shape=box,style=filled,color=olivedrab1]; X86Info [shape=box,style=filled,color=olivedrab1]; X86Disassembler [shape=box,style=filled,color=olivedrab1]; X86CodeGen [shape=box,style=filled,color=olivedrab1]; X86AsmPrinter [shape=box,style=filled,color=olivedrab1]; X86AsmParser [shape=box,style=filled,color=olivedrab1]; TransformUtils [shape=box,styl...

...K ##################################### getconf show information only for one core. *getconf -a |grep CACHE * LEVEL1_ICACHE_SIZE 32768 LEVEL1_DCACHE_SIZE 32768 LEVEL2_CACHE_SIZE 6291456 L1 - 64KiB - not true L2 - 6MiB - true ############################ According the most powerful tool - x86info we can presume that we have: *x86info -c * Found 2 identical CPUs Extended Family: 0 Extended Model: 1 Family: 6 Model: 23 Stepping: 6 Type: 0 (Original OEM) CPU Model (x86info's best guess): Core 2 Duo P8600 Processor name string (BIOS programmed): Intel(R) Core(TM)2 Duo CPU T9300 @ 2...

...o `vtable for llvm::ModulePass' ... and lots more Running make in the clang top level had link errors too, undoubtedly because the llvm build failed: make[1]: Entering directory `/home/llvm/tools/clang/tools' The system cannot find the path specified. llvm-config: unknown component name: x86info make[2]: Entering directory `/home/llvm/tools/clang/tools/clang-cc' llvm[2]: Compiling clang-cc.cpp for Debug build The system cannot find the path specified. llvm-config: unknown component name: x86info llvm[2]: Linking Debug executable clang-cc C:/msys/1.0/home/llvm/tools/clang/tools/clang-cc...

On Mon, Jan 27, 2014 at 10:27:20AM +0100, Pino Toscano wrote: > On Monday 27 January 2014 11:06:14 Kashyap Chamarthy wrote: > > Running virt-builder in a guest Fedora-20 guest hypervisor w/ Rawhide > > Kernel, throws the below: > > > > $ virt-builder fedora-20 --format qcow2 --size 20G > > virt-builder: symbol lookup error: /lib64/libgnutls.so.28: undefined

...64 > libvirt-1.1.3.1-2.fc20.x86_64 > qemu-system-x86-1.6.1-2.fc20.x86_64 > > When I briefly discussed this double fault panic with Paolo Bonzini (KVM > maintainer), he mentioned it is probably a host hypervisor bug. But this > needs more investigation (ftrace for nested guest, x86info in L1 and L2 > - if possible). > > > Answering Rom's earlier question ("Kashyap, can you please share your > experience?"): Yes, ested virtualization with KVM and Intel is not > *really* the most stable, but there's on going work upstream to improve > this and...

On Apr 8, 2013, at 2:55 PM, "Robinson, Paul" <Paul_Robinson at playstation.sony.com> wrote: I keep seeing "this is a layering violation" comments on the lists. > While there are a few llvm.org pages that mention layers in passing, > there is nothing (that I've found) actually specifying the layers. > Trying to infer the layering from the code is tedious and

Thanks Richard for a fast reply. Yes, indeed, im working on a nested environment. I try to run v2v inside a VM (L1) and to create an L2 by the conversion process. And on Intel. As I wrote, it fails once in few times, mainly when there is a memory pressure on L0. Kashyap, can you please share your experience? Why should it crash during nested conversion. I'm not too familiar with libguestfs

I keep seeing "this is a layering violation" comments on the lists. While there are a few llvm.org pages that mention layers in passing, there is nothing (that I've found) actually specifying the layers. Trying to infer the layering from the code is tedious and error-prone (or we wouldn't see so many violations in code reviews, eh?). Now, I understand that Google has some sort

...1.3.1-2.fc20.x86_64 >> qemu-system-x86-1.6.1-2.fc20.x86_64 >> >> When I briefly discussed this double fault panic with Paolo Bonzini (KVM >> maintainer), he mentioned it is probably a host hypervisor bug. But this >> needs more investigation (ftrace for nested guest, x86info in L1 and L2 >> - if possible). >> >> >> Answering Rom's earlier question ("Kashyap, can you please share your >> experience?"): Yes, ested virtualization with KVM and Intel is not >> *really* the most stable, but there's on going work upstream...

...llvm/lib -lpthread -lm bash-3.2$ /sw/lib/llvm/bin/llvm-config --libs -lLLVMLinker -lLLVMipo -lLLVMInterpreter -lLLVMInstrumentation -lLLVMJIT -lLLVMExecutionEngine -lLLVMBitWriter -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMMCParser -lLLVMX86AsmPrinter -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMX86Info -lLLVMAsmPrinter -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine -lLLVMTransformUtils -lLLVMipa -lLLVMAsmParser -lLLVMArchive -lLLVMBitReader -lLLVMAnalysis -lLLVMTarget -lLLVMMC -lLLVMCore -lLLVMSupport -lLLVMSystem bash-3.2$ /sw/lib/llvm/bin/llvm-config --libnames libLLVMLinker.a libLLVMipo.a l...

...g @sound-and-video @system-tools @text-internet @xen @web-server @smb-server @x-software-development @base-x system-config-kickstart system-config-netboot system-config-netboot-cmd keyutils dmraid-events-logwatch kexec-tools gpart iscsi-initiator-utils trousers bridge-utils authd fipscheck hardlink x86info device-mapper-multipath hfsutils perl-XML-SAX perl-XML-Twig perl-XML-Dumper perl-TimeDate perl-libxml-perl perl-Convert-ASN1 perl-XML-NamespaceSupport perl-DateManip perl-Crypt-SSLeay perl-Mozilla-LDAP perl-LDAP perl-XML-Grove python-imaging perl-Archive-Zip pexpect imake gcc-objc expect java-1.6.0...

...telnet-server termcap tetex tetex-dvips tetex-fonts tetex-latex texinfo tftp time tk tk-devel tmpwatch traceroute -tree ttmkfdir tzdata udev unix2dos unzip urw-fonts usbutils usermode util-linux vconfig vim-common vim-enhanced -vim-minimal vixie-cron wget which -wireless-tools words -wpa_supplicant x86info Xaw3d -xferstats xinetd xkeyboard-config xml-common -xorg-x11-drv-evdev -xorg-x11-drv-keyboard -xorg-x11-drv-mouse -xorg-x11-drv-vesa -xorg-x11-drv-void xorg-x11-filesystem xorg-x11-fonts-100dpi xorg-x11-fonts-75dpi xorg-x11-fonts-base xorg-x11-fonts-ISO8859-1-100dpi xorg-x11-fonts-ISO8859-1-75dpi...