search for: pagetables

hi, I''m developing my own 32-bit (no PAE) paravirtualized kernel for xen with Mini-OS as a starting point. I am currently working on process page table support (equivalent of arch/i386/mm/pgtable-xen.c) and mostly following Linux for the moment. I noticed that linux-2.6.18-xen never pins an L1 table (a pte), yet __pgd_pin() walks the page directory and gives up write access on the kernel

I want to know any difference between writing, reading and shadow page table (for example performance). I am thankful for any help or resource for that. -- Best Regards Mohamad Taghi Mir Mohamad Rezaie Iran University of Science and Technology Department of Computer Science & Engineering System Software Group _______________________________________________ Xen-devel mailing list

Hi, I have a question about memory page tables in Xen. As far as I understood, every modification to page table will go through Xen(hypervisor). Is it so that all page tables are actually allocated in Xen(hypervisor) instead of guest OS(domain)? Also, is it the case that Xen(hypervisor) needs to maintain a page table for each process running in every domain? Thanks Haifeng

-stable review patch. If anyone has any objections, please let us know. ------------------ From: Jeremy Fitzhardinge <jeremy@goop.org> patch 9f79991d4186089e228274196413572cc000143b in mainline. When a pagetable is no longer in use, it must be unpinned so that its pages can be freed. However, this is only possible if there are no stray uses of the pagetable. The code currently deals

-stable review patch. If anyone has any objections, please let us know. ------------------ From: Jeremy Fitzhardinge <jeremy@goop.org> patch 9f79991d4186089e228274196413572cc000143b in mainline. When a pagetable is no longer in use, it must be unpinned so that its pages can be freed. However, this is only possible if there are no stray uses of the pagetable. The code currently deals

Hi, guys Recently I have been doing some research & I''ve got in trouble. I have altered the kernel of domU and put the code section and data section of selinux security server which locate ~/security/selinux/ss into two seperate sections in the final vmlinux image(see below) objdump -h vmlinux vmlinux: file format elf32-i386 Sections: Idx Name Size VMA

Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2009-01-27.orig/xen/drivers/passthrough/amd/iommu_map.c 2009-01-30 08:43:35.000000000 +0100 +++ 2009-01-27/xen/drivers/passthrough/amd/iommu_map.c 2009-01-30 08:46:29.000000000 +0100 @@ -461,8 +461,8 @@ int amd_iommu_map_page(struct domain *d, iommu_l2e = iommu_l2e_from_pfn(hd->root_table, hd->paging_mode, gfn); if (

...000010000 000 180 000 010) vm_enter:895: about to instantiate new maps pml4=0x6000010000 vm_enter:901: Using physical pml4 0x13091000 for Xen (XEN) mm.c:1664:d72 Bad type (saw 00000000e8000001 != exp 0000000080000000) for mfn 13091 (pfn 10) (XEN) mm.c:1724:d72 New baseptr 13091: slow path via idle pagetables (XEN) mm.c:1664:d72 Bad type (saw 00000000e8000001 != exp 0000000080000000) for mfn 13091 (pfn 10) (XEN) mm.c:1737:d72 Fatal error while installing new baseptr 13091 I''ve tried both with and without the writable page tables turned on with vm_assist. Is there something that I am missing?...

Hi all, I''ve been reading through the code regarding paging --> spending a lot of time in mm/*.*, as well as some of the other parts up a level or two, but I''m still unclear as to some key things. Here''s what I think I know: I think I know how a domain''s shadow page table is first allocated E.G. the hash_table is xmalloc''ed and when it is

In a recent conversation one of my coworkers raised a concern about memory limitations when running 32-bit guests on top of the 64-bit hypervisor. At this point the discussion is academic; I don''t know when/if we''ll ever be able to get system resources to test it, to see if the concerns that he expressed are real. So I decided to post this in hope of getting comments from the

Dear All: I am pretty new to xen-devel, please correct me in the following. Assume we have the following terms GPT: guest page table SPT: shadow page table (Question a) When guest OS is running, is it always using SPT for address translation? If it is the case, how does guest OS refer and modify its own GPT content? It seems that there is a page table entry in SPT for the GPT page. (Question

Hi all, Can Xen hypervisor modify HVM domU's Shadow page table, under the dom0's context, like trapped from dom0's hypercall? I think it have to call 2 functions at least: guest_walk_tables() and flush_tlb_all(). Can these 2 functions called in dom0's context? In my test, if hypervisor tries to modify HVM's shadow page table, it will bring down the whole system. I am not

clear MPT l2 entries when allocating monitor pagetable Changeset 10734 removed the code clearing MPT l2 entries, however these entries are stained when copying from idle_pg_table_l2. Signed-off-by: Xin Li <xin.b.li@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...: 186, btch: 31 usd: 0 CPU 1: hi: 186, btch: 31 usd: 0 active_anon:5831 inactive_anon:2 isolated_anon:0 active_file:3833 inactive_file:57589 isolated_file:0 unevictable:1124 dirty:99 writeback:0 unstable:0 free:283729 slab_reclaimable:4785 slab_unreclaimable:2380 mapped:3362 shmem:36 pagetables:1029 bounce:0 Node 0 DMA free:12904kB min:32kB low:40kB high:48kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:12712kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimabl...

This is my current set of updates to Xen for 2.6.24. This is largely a bugfix set, and a couple of them are also relevent to 2.6.23. These are in the pre-x86 merge form; I'll update them once the merge goes into git. Quick overview: - remove some dead code in arch/i386/mm/init.c - clean up some duplicate includes - when sending an IPI, yield the vcpu if the destination doesn't have

This is my current set of updates to Xen for 2.6.24. This is largely a bugfix set, and a couple of them are also relevent to 2.6.23. These are in the pre-x86 merge form; I'll update them once the merge goes into git. Quick overview: - remove some dead code in arch/i386/mm/init.c - clean up some duplicate includes - when sending an IPI, yield the vcpu if the destination doesn't have

This is my current set of updates to Xen for 2.6.24. This is largely a bugfix set, and a couple of them are also relevent to 2.6.23. These are in the pre-x86 merge form; I'll update them once the merge goes into git. Quick overview: - remove some dead code in arch/i386/mm/init.c - clean up some duplicate includes - when sending an IPI, yield the vcpu if the destination doesn't have

Hello, I am hacking on a Mini-OS that is able to run as domain 0 and is able to start a guest (another Mini-OS for now). I was able to get a memory allocated to the guest and am now trying to build its pagetable and after that copy the kernel to the right places. The problem is: Given a machine frame number from a memory frame of the guest, how do I conceptionally map this into

At OLS I gave a talk on some of the Xen scalability inhibitors, and one of these was writable page tables. We went over why the feature does not scale, but just as important, we found that the uniprocessor case does not provide any advantage either. These tests were done on x86_64, so I wanted to run the 1-way test on 32 bit to show the same problem. So, I have run with writable PTs and

...le page tables. In the short-term I''m more interested in functionality than performance. This patch disables them and fixes a compile issue. # This is a BitKeeper generated diff -Nru style patch. # # ChangeSet # 2005/04/29 19:26:00-07:00 kmacy@curly.lab.netapp.com # disable writable pagetables + compile fix # Signed-off-by: Kip Macy <kmacy@fsmware.com> # # freebsd-5.3-xen-sparse/i386-xen/include/xenpmap.h # 2005/04/29 19:25:58-07:00 kmacy@curly.lab.netapp.com +5 -3 # disable writable pagetables + compile fix # diff -Nru a/freebsd-5.3-xen-sparse/i386-xen/include/xenpmap.h b...