search for: get_phys_to_machine

Hello. log of the crashing boot process: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-14-xen331-linux-2.6.29-rc6-crash.txt 2.6.29-rc5 based pv_ops dom0 works on the same computer.. with the same Xen version. I tried with and without pci=nomsi. adding ''noapic'' doesn''t seem to help (I need that with 2.6.29-rc5 to make it work). Any ideas

...lse; + + if (xen_feature(XENFEAT_auto_translated_physmap)) + return 0; + + if (kmap_ops && + !in_interrupt() && + paravirt_get_lazy_mode() == PARAVIRT_LAZY_NONE) { + arch_enter_lazy_mmu_mode(); + lazy = true; + } + + for (i = 0; i < count; i++) { + unsigned long mfn = get_phys_to_machine(page_to_pfn(pages[i])); + unsigned long pfn = page_to_pfn(pages[i]); + + if (mfn == INVALID_P2M_ENTRY || !(mfn & FOREIGN_FRAME_BIT)) { + ret = -EINVAL; + goto out; + } + + set_page_private(pages[i], INVALID_P2M_ENTRY); + WARN_ON(!PagePrivate(pages[i])); + ClearPagePrivate(pages[i]); +...

...lse; + + if (xen_feature(XENFEAT_auto_translated_physmap)) + return 0; + + if (kmap_ops && + !in_interrupt() && + paravirt_get_lazy_mode() == PARAVIRT_LAZY_NONE) { + arch_enter_lazy_mmu_mode(); + lazy = true; + } + + for (i = 0; i < count; i++) { + unsigned long mfn = get_phys_to_machine(page_to_pfn(pages[i])); + unsigned long pfn = page_to_pfn(pages[i]); + + if (mfn == INVALID_P2M_ENTRY || !(mfn & FOREIGN_FRAME_BIT)) { + ret = -EINVAL; + goto out; + } + + set_page_private(pages[i], INVALID_P2M_ENTRY); + WARN_ON(!PagePrivate(pages[i])); + ClearPagePrivate(pages[i]); +...

Hello Jeremy & Keir, sorry to be persistent, but the problem that pvops0 kernel 2.6.32.x still does not boot if x > 18 on my machines (and on many other machines, see this mailing list) is not solved yet. Shouldn''t this be a great focus of debugging and fixing? What is the point of having releases for 4.0.2 or 4.1 if I don''t have a dom0 kernel? The last time I tried

I am working on some other bugs and perf issues - and while working I noticed that both sparse and Coverity have reported some issues with Xen drivers. Please see attached various bug-fixes that I am proposing for 3.6.

Attached patch makes the balloon driver arch-neutral (compiles on ia64... look ma, no #ifdef''s!). Please apply to xen-unstable. One change should be eyeballed, line 257 in balloon.c, because phys_to_machine_mapping[pfn] is not identical to pfn_to_mfn (different by sign bit, should be OK?) Signed-off by: Dan Magenheimer <dan.magenheimer@hp.com> diff -r 0255f48b757f

Hi everyone, I am very excited to see that dom0 pvops is finally coming close to working, so I wanted to give it a try. >From the description it was not clear to me which kernel to chose as base for the patches.hg, so I took the latest (that was ~ 2 weeks ago) kernel on git.kernel.org I could find (post-2.6.28 git tip at that point). I managed to more or less apply all of the patches in the

Hi all, this patch series enables xen-swiotlb on arm and arm64. It has been heavily reworked compared to the previous versions in order to achieve better performances and to address review comments. We are not using dma_mark_clean to ensure coherency anymore. We call the platform implementation of map_page and unmap_page. We assume that dom0 has been mapped 1:1 (physical address == machine

Hi, we have some problems with acpidump running on Xen Dom0. On 64 bit Dom0 it will trigger the OOM killer, on 32 bit Dom0s it will cause a kernel crash. The hypervisor does not matter, I tried 4.1.3-rc2 as well as various unstable versions including 25467, also 32-bit versions of 4.1. The Dom0 kernels were always PVOPS versions, the problems starts with 3.2-rc1~194 and is still in 3.5.0-rc3.

Hi, I have this bug when I activate java-6-jdk on Tomcat 5.5.26 in a Lenny Guest : Jul 31 21:24:15 tomcat01 kernel: 1 multicall(s) failed: cpu 3 Jul 31 21:24:15 tomcat01 kernel: call 1/1: op=14 arg=[b7f1a000] result=-22 Jul 31 21:24:15 tomcat01 kernel: ------------[ cut here ]------------ Jul 31 21:24:15 tomcat01 kernel: kernel BUG at arch/x86/xen/multicalls.c:103! Jul 31 21:24:15 tomcat01

...ault+0x1b6/0x345 Jul 17 06:25:51 placka kernel: [34974.028297] [<ffffffff81195900>] ? part_round_stats+0x2f/0x40 Jul 17 06:25:51 placka kernel: [34974.030601] [<ffffffff81197e0c>] ? drive_stat_acct+0x106/0x115 Jul 17 06:25:51 placka kernel: [34974.032875] [<ffffffff810072b8>] ? get_phys_to_machine+0x16/0x58 Jul 17 06:25:51 placka kernel: [34974.035085] [<ffffffff81350b35>] ? page_fault+0x25/0x30 Jul 17 06:25:51 placka kernel: [34974.037276] [<ffffffff811b37d7>] ? clear_page_c+0x7/0x10 Jul 17 06:25:51 placka kernel: [34974.039488] [<ffffffff810bb69d>] ? get_page_from_free...

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine

...11c/0x2c4 Sep 5 18:03:46 pcale kernel: [ 1017.376428] [<ffffffff8134de00>] ? out_of_line_wait_on_bit_lock+0x2/0x78 Sep 5 18:03:46 pcale kernel: [ 1017.376432] [<ffffffff8127e462>] ? sock_aio_write+0x121/0x135 Sep 5 18:03:46 pcale kernel: [ 1017.376436] [<ffffffff810072e8>] ? get_phys_to_machine+0x16/0x58 Sep 5 18:03:46 pcale kernel: [ 1017.376439] [<ffffffff81004e24>] ? pte_pfn_to_mfn+0x26/0x77 Sep 5 18:03:46 pcale kernel: [ 1017.376442] [<ffffffff8127e341>] ? sock_aio_dtor+0x9/0x9 Sep 5 18:03:46 pcale kernel: [ 1017.376446] [<ffffffff810fa6df>] ? do_sync_readv_wri...