search for: phys_to_machine_map

Hi, At x86_64 linux domain, phys_to_machine_mapping, pfn_to_mfn_frame_list_list, and pfn_to_mfn_frame_list should be aligned to pagesize, but it can be misaligned now. If they aren''t aligned to pagesize, it will cause fails while saving the domain. This patch fixed it. regards, Signed-off-by: Kazuo Moriwaka <moriwaka@valinux.co.jp&...

Hi all, Can some one tell me where phys_to_machine_mapping is being initialized for a domU having paging mode set to PG_translate. I see that, populate_physmap() after calling __alloc_xen_heap_pages only updates the machine_to_physmap but how is the mfn for the allocated page being updated/set for phys_to_machine_mapping?? I see that phys_to_machine_...

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 linux-2.6-xen-sparse/drivers/xen/balloon/balloon.c --- a/linux-2.6-xen-sparse/drivers/xen/balloon/balloon.c Sun Dec 4 19:12:00 2005 +++...

...: 0xcaef _edata : 0xe8c4 __bss_start : 0x10000 _end : 0x21590 nr_pages : 3072 start_info : 0x27000 pt_base : 0x2a000 nr_pt_frames : 5 machine_to_phys_mapping: 0xffff800000000000 phys_to_machine_mapping: 0x21000 The Mini-OS source says that free pages follow pt_base + nr_pt_frames + 3 (store, console, something pages). So far so good. So I reserve myself 42 pages for initial data structures and remove the rest from the initial page tables. After some initializing I move over the unmapped page...

Hi, Is there any tool out there that can help me analyze a coredump? Thanks, David. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...f the loop early if one of the handles returned from HYPERVISOR_grant_table_op is negative: for (i = 0; i < nseg; i++) { if (unlikely(map[i].handle < 0)) { DPRINTK("invalid buffer -- could not remap it\n"); fast_flush_area(pending_idx, nseg); goto bad_descriptor; } phys_to_machine_mapping[__pa(MMAP_VADDR( pending_idx, i)) >> PAGE_SHIFT] = FOREIGN_FRAME(map[i].dev_bus_addr >> PAGE_SHIFT); pending_handle(pending_idx, i) = map[i].handle; } The implementation of fast_flush_area uses pending_handle and is called to flush the whole range nseg but the loop above...

...a. Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 27ad7ed41be2 extras/mini-os/arch/x86/mm.c --- a/extras/mini-os/arch/x86/mm.c Fri Jan 18 15:55:13 2008 +0000 +++ b/extras/mini-os/arch/x86/mm.c Fri Jan 18 16:02:32 2008 +0000 @@ -50,6 +50,7 @@ #endif unsigned long *phys_to_machine_mapping; +unsigned long mfn_zero; extern char stack[]; extern void page_walk(unsigned long virt_addr); @@ -492,10 +493,13 @@ static void clear_bootstrap(void) static void clear_bootstrap(void) { struct xen_memory_reservation reservation; - xen_pfn_t mfns[] = { virt_to_mfn(0), virt_to_mfn(...

...e dist cd linux-2.6.11-xen0 make ARCH=xen oldconfig make modules make modules_install make install After which point I get the following error : CC drivers/xen/balloon/balloon.o drivers/xen/balloon/balloon.c: In function `balloon_process'': drivers/xen/balloon/balloon.c:218: error: `phys_to_machine_mapping'' undeclared (first use in this function) drivers/xen/balloon/balloon.c:218: error: (Each undeclared identifier is reported only once drivers/xen/balloon/balloon.c:218: error: for each function it appears in.) drivers/xen/balloon/balloon.c:218: error: `INVALID_P2M_ENTRY'' unde...

...table_offset(va)]; } static inline void __guest_set_l2e( - struct exec_domain *ed, unsigned long va, unsigned long value) + struct exec_domain *ed, unsigned long va, l2_pgentry_t value) { if ( shadow_mode_translate(ed->domain) ) { unsigned long pfn; - pfn = phys_to_machine_mapping(value >> PAGE_SHIFT); + pfn = phys_to_machine_mapping(l2_pgentry_val(value) >> PAGE_SHIFT); ed->arch.hl2_vtable[l2_table_offset(va)] = mk_l2_pgentry((pfn << PAGE_SHIFT) | __PAGE_HYPERVISOR); - ed->arch.guest_vtable[l2_table_offset(va...

I installed Xen using the binary release on debian sarge and got it to boot no problem but when I check if dma is enabled with ''hdparm /dev/hda'' it''s not. I can''t enable it either with ''hdparm -d1 /dev/hda''. Says operation not permited. Using my debian default kernel dma works just fine. How can I enable dma with the Xen Kernel? Thanks!

Hi Folks, I want to do the guest physical address (GPA) to host physical address (HPA) conversion for a VT domain in the VT domains itself. So essentially I would like to access the phys_to_machine_mapping table in the V domain. does a VT domain already have access to this table? if not, how can I do this address conversion inside the VT domain? Thanks, Sanjay -- ---------------------- PhD Student, Georgia Tech http://www.cc.gatech.edu/~ksanjay/ _____________________________________________...

When compiling a 2.6.10-xen0 kernel I get the following error: CC drivers/xen/balloon/balloon.o drivers/xen/balloon/balloon.c: In function `balloon_process'': drivers/xen/balloon/balloon.c:209: error: `phys_to_machine_mapping'' undeclared (first use in this function) drivers/xen/balloon/balloon.c:209: error: (Each undeclared identifier is reported only once drivers/xen/balloon/balloon.c:209: error: for each function it appears in.) drivers/xen/balloon/balloon.c:209: error: `INVALID_P2M_ENTRY'' undecl...

Hi Jeremy. According to your suggestion, I recreated patches for Ingo's x86.git tree. And this patch series includes Eddie's modification. Please review and forward them. (or push back to respin.) Recently the xen-ia64 community started to make efforts to merge xen/ia64 Linux to upstream. The first step is to merge up domU portion. This patchset is preliminary for xen/ia64 domU linux

Hi Jeremy. According to your suggestion, I recreated patches for Ingo's x86.git tree. And this patch series includes Eddie's modification. Please review and forward them. (or push back to respin.) Recently the xen-ia64 community started to make efforts to merge xen/ia64 Linux to upstream. The first step is to merge up domU portion. This patchset is preliminary for xen/ia64 domU linux

add a hypercall number for virtual device in unmodified guest There are 6 patches for para-driver support in vmx guest. This is the first one. Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> diff -r 287d36b46fa3 xen/arch/x86/x86_32/entry.S --- a/xen/arch/x86/x86_32/entry.S Tue Aug 30 20:36:49 2005 +++

...nsigned long, unsigned long); extern void vmx_wait_io(void); extern int vmx_setup_platform(struct vcpu *, struct cpu_user_regs *); +extern void vmx_io_assist(struct vcpu *v); // XXX - think about this -- maybe use bit 30 of the mfn to signify an MMIO frame. #define mmio_space(gpa) (!VALID_MFN(phys_to_machine_mapping((gpa) >> PAGE_SHIFT))) diff -r febfcd0a1a0a -r 9a43d5c12b95 xen/arch/x86/vmx.c --- a/xen/arch/x86/vmx.c Thu Jun 30 03:20:48 2005 +++ b/xen/arch/x86/vmx.c Thu Jun 30 04:08:50 2005 @@ -135,17 +135,20 @@ } #endif - if (!vmx_paging_enabled(current)) + if (!vmx_paging_enabled(cur...

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some