similar to: page table question!

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

There has been some progress, but still no joy. Definitely not intended for inclusion at this point. Tim, Wei, I added a Xen command line toggle to disable IOMMU and P2M table sharing. Tim, I verified that changes to p2m-pt.c don''t break shadow mode (64bit hypervisor and Win 7 guest). Hongkaixing, I incorporated your suggestion in patch 2, so I should add your Signed-off-by eventually.

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

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

Hi All, I have several questions about log dirty mode during live migration. For my understanding, each time after XEN_DOMCTL_SHADOW_OP_CLEAN or XEN_DOMCTL_SHADOW_OP_PEEK operation, all the pages are set as read only. The following memory accesses to the memory pages will cause page fault (permission conflict) then using page_mark_dirty function to set the dirty bitmap. However, after I read

Hi, I am really confused about NPT walks for guest page table , and eager to know the details about it. It is treated as data writes even if the access itself is a code read in AMD NPT.I just want to know : is it the same in EPT? Could anyone help me? I would like to know that very much Thank you in advance Bo Ma _______________________________________________ Xen-devel mailing list

From: Zhang Xiantao <xiantao.zhang@intel.com> With virtual EPT support, L1 hyerpvisor can use EPT hardware for L2 guest''s memory virtualization. In this way, L2 guest''s performance can be improved sharply. According to our testing, some benchmarks can show > 5x performance gain. Signed-off-by: Zhang Xiantao <xiantao.zhang@intel.com> Zhang Xiantao (11):

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

paging mechanism clarification Hi All, The Xen uses 2 level Paging Mechanism to resolve the Virtual Addresses into frame numbers from domU.The first level is taken care by the MMU for the domU i.e translation from virtual address to the physical address just like normal paging mechanism. The second level of translation is done by the Xen hypervisor.It translates the pseduo physical address

Just found this patch in house which I thought sent out already. :-) Still one thing remaining is to special case for UP guest which suffers overhead from this change... ---- Remove lock on first guest table walk Existing shadow fault path grabs big lock before walking guest tables, to ensure consistency with shadow content lest concurrent change from other vcpu in a bad OS. But this lock

hi, How can I get corresponding shadowed page number of a virtual address in vm? -- Best Regards, Mohamad Rezaei

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

Hi! Attached patch removes gfn_to_mfn_current(). It is redundant and effectively unused. All remaining users now use proper replacement function. => No functional change. While here, silence stdvga and use page_mode_hap() consequently. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH

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, This is today''s nightly testing report; no new issue found, bug #1259 got fixed. Some vt-d cases failed in first round testing, but can get pass in retesting. Fixed issue: ============================================== 1. booting windows guest causes Xen HV crash http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1259 Old issues:

Hi Tim, Could you please have a look at this bug? Thanks a lot. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1774 Best Regards, Yongjie Ren (Jay) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This patch series includes a series of bugs related to p2m, ept, and PoD code which were found as part of our XenServer product testing. Each of these fixes actual bugs, and the 3.4-based version of the patch has been tested thoroughly. (There may be bugs in porting the patches, but most of them are simple enough as to make it unlikely.) Each patch is conceptually independent, so they can each

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

Hi, V6: The only change from V5 is in patch #6: - changed comment to reflect autoxlate - removed a redundant ASSERT - reworked logic a bit so that get_page_from_gfn() is called with NULL for p2m type as before. arm has ASSERT wanting it to be NULL. Tim: patch 4 needs your approval. Daniel: patch 5 needs your approval. These patches implement PVH dom0. Patches 1 and 2

I wanted to run without 2MB and 1GB EPT pages, so I added "hap_2mb=0 hap_1gb=0" to the Xen grub command line. However I see the following on Xen boot: (XEN) EPT supports 2MB super page. When I bring up a guest I see a non-zero number of 2MB pages in the "xl create" output: xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000017af10 TOTAL: