similar to: Kernel panic in pin_pagetable_pfn

This change updates a few of the functions to use __pa_symbol when translating C visible symbols instead of __pa. By using __pa_symbol we are able to drop a few extra lines of code as don't have to test to see if the virtual pointer is a part of the kernel text or just standard virtual memory. Cc: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> Signed-off-by: Alexander Duyck

This change updates a few of the functions to use __pa_symbol when translating C visible symbols instead of __pa. By using __pa_symbol we are able to drop a few extra lines of code as don't have to test to see if the virtual pointer is a part of the kernel text or just standard virtual memory. Cc: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> Signed-off-by: Alexander Duyck

To get x86 to work, you need to compile /arch/x86/boot and /arch/x86/boot/compressed with gcc. The rest can be compiled with llvm-gcc. The only adjustment you need to make is to /arch/x86/kernel/signal_32.c to fix the stack offset in sys_sigreturn. Also you must compile with -O0. instcombine is causing the crashes you are seeing. I know mem2reg, sccp, simplifycfg, and dce result in a working

For people who want to try hacking on the linux kernel with llvm, here is a head start: http://llvm.org/~alenhar2/k.tbz This is a 2.6.27.5 kernel with a .config file for qemu/kvm with virtio devices (I also think it will work with the default devices). The build process uses llvm-gcc -> opt -> llc so you can add your own (per-file) passes to the build process or debug specific passes.

One other note I forgot... sig_sysreturn (arch/x86/kernel/signal_32.c) has a magic fudge factor to fix up stack layout differences between llvm and gcc. If when you hit userspace you get signal handling errors, look at the frame addresses printed out and adjust the fudge factor to make the frame addresses match. (the code automatically enables the debug output after the first signal frame

Hi, I am trying to build the Linux kernel with LLVM. 'ARCH=um' appears to work, now I am trying to get 'ARCH=x86' to work. So far it seems there is something wrong with the boot vga code (it finds no video modes), the acpi code, and the serial console code. I am now trying to compile drivers/ with llvm-gcc and the rest with gcc-4.2 (I have a wrapper script), I am compiling to

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 On a fresh installation of Debian Jessie, when I try to start a domU, it try to access to a dom0 LVM Volume Group : [...] (I put all the boot at the end) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD

[Please keep replies on the list] > ************************************************************ > * IMPORTANT NOTICE > * > * When reporting bugs, include the COMPLETE, UNEDITED > * output below in your bug report. > * > ************************************************************ > libguestfs: trace: set_verbose true

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: important -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core) Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-amd64 depends on no

I've tried the workaround you suggested but it doesn't seem to work. Also tried to add just "libsbz.so" to zz-workaround with no success. It throws the same error as before. PS: Sorry I've just hit reply without checking the "To:" address and I guess it sent directly to you. On Thu, Sep 3, 2020 at 1:59 PM Richard W.M. Jones <rjones@redhat.com> wrote: >

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

what does it mean? i never seen that before xen4 on debian squeeze 2.6.32-5-xen-amd64 [22077.208077] BUG: soft lockup - CPU#7 stuck for 61s! [udisks-dm-expor:11772] [22077.208139] Modules linked in: ext4 jbd2 crc16 xfs exportfs xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev bridge stp ip6table_filter ip6_tables iptable_filter ip_tables x_tables xen_evtchn xenfs fuse

Hi, I''m trying to boot a PV VM I just installed (following http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer) without success. My XEN installation is xen-unstable 54c8c9eaee92+ on a Debian unstable machine (x86_64), kernel 3.3.4+. The VM I installed is, again, a Debian unstable x86_64. The installation went smoothly; I used an 8GB file as a disk back-end. I went

Hello, I guess it possible distro specific issue but is it resolvable? I have one node(testing purpose) ganeti 2.0.1 cluster installed over Debian5 Lenny. Almost everything from distro repositories. Only ganeti 2.0.1 and ganeti-debootstrap are from sources. I have it successful run with vmlinuz-2.6.26-2-xen-686 and initrd.img-2.6.26-2-xen-686 from repositories. Both Dom0 and DomU are use the

Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,

Hi, we''re using Xen 3.3.0 on Debian Etch with 2.6.18.8 kernel from xen.org on dom0. We have problems starting Intrepid domU (using Intrepid''s kernel 2.6.27-7-server) if we give more than 4GB of memory to this domain. Using memory = ''4096'' works perfectly, but changing it to ''4097'' already gives an error. Can anyone put some light on this?

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal After giving xen a shoot with the fresh lenny packages, an annoying bug comes up right after trying to boot into the new system. I'll provide further informations if needed. Please see serial debug output below and here http://plzk.de/xen-lenny (maxlines got extended for comfortable reading) XEN) Xen version 3.2-1

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Hi, I have been trying to get NIC PCI Passthrough to work on Xen 4.3.0 and have hit a wall. On attaching the NIC the domU network driver (igb) crashes. I followed the Xen PCI Passthrough wiki http://wiki.xen.org/wiki/Xen_PCI_Passthrough and am using dynamic device assignment with xl. Trying to passthrough this device: root@dom0:~# lspci|grep 82575EB 05:00.1 Ethernet controller: Intel