similar to: can dom0 modify Shadow PT of HVM domU?

The guest handle checks should use paging_* predicates, not shadow_*. Also tidy up a few places where p2m definitions were being imported via asm/guest_access.h -> asm/shadow.h -> asm/p2m.h Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> -- Tim Deegan <Tim.Deegan@citrix.com> Principal Software Engineer, Citrix Systems (R&D) Ltd. [Company #02300071, SL9 0DZ, UK.]

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, all Page offline can be used by many purpose, like memory offline, memory power management, proactive action when multiple CE error happen to one page etc. In virtualization environment without guest offline support, we think offline a page usually means replace the old page with a new one transparently to guest. Currently we are trying to add page offline support in Xen environment .

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

Trying to migrate a 64bit PV guest with 64GB running medium to heavy load on xen 3.4.0, it is showing lot of soft lockups. The softlockups are causing dom0 reboot by the cluster FS. The hardware has 256GB and 32 CPUs. Looking into the hypervisor thru kdb, I see one cpu in sh_resync_all() while all other 31 appear spinning on the shadow_lock. I vaguely remember seeing some thread on this while

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

We''ve got reports of that change causing HVM data corruption issues. While I can''t see what''s wrong with the patch, I''d suggest at least reverting it from the 3.3 tree (which is what our code is based upon) for the time being. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

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_mapping is a #defined to RO_MPT_VIRT_START

Hi, I looked at the function xc_translate_foreign_address(), and see that it walks the page table of the guest VM. So at best, it should return the pfn of the guest (?) We can see taht the Later part of the function is like this: ... if (pt_levels >= 3) mfn = (pte & L0_PAGETABLE_MASK_PAE) >> PAGE_SHIFT; else mfn = (pte & L0_PAGETABLE_MASK)

Hi all, When i do ''xm dmesg'' the last statement says "*** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen)" (i have no clue what''s that supposed to mean??) But when i press ctrl-a three times at the serial console, nothing happens. Iam using minicom to connect to the serial port of xen machine. Once xen

Simplify paging_invlpg when flush is not required. New ''flush'' parameter is added to paging_invlpg, to allow caller assigning whether flush check is required. It''s wasteful to always validate shadow linear mapping if caller doesn''t check return value at all. Signed-off-by Kevin Tian <kevin.tian@intel.com> Thanks, Kevin

One could even debate whether reserved bit faults are always fatal (and should never be propagated to the guest)... Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2008-01-28/xen/arch/x86/traps.c =================================================================== --- 2008-01-28.orig/xen/arch/x86/traps.c 2008-01-28 11:31:44.000000000 +0100 +++ 2008-01-28/xen/arch/x86/traps.c

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

We recently observed a problem with Solaris HVM domains. The bug was seen was seen with a higher number of VCPUs (3 or more), and always had the same pattern: some memory was allocated in the guest, but the first reference caused it to crash with a fatal pagefault. However, on inspection of the page tables, the guests'' view of the pagetables was consistent: the page was present.

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

With pretty trivial user mode programs being able to crash the kernel due to the ref counter widths in Xen being more narrow than in Linux, I started an attempt to put together a kernel side fix. While addressing the plain hypercalls is pretty strait forward, dealing with multicalls (both when using them for lazy mmu mode batching and when explicitly using them in e.g. netback - the backends are

Hello, I''m new to Xen and especially to the hypervisor code. I''m working off a 3.0.4.1 base and have the following questions regarding the memory management code for an x86, 32-bit platform (capable of supporting PAE). I''m doing some research into providing grant table hypercall support from a Windows 2003 HVM. I have made all the necessary changes to allow the

This fixes a bug in changeset 22526:7a5ee3800417, where the wrong value is read when deciding whether to flush the VTd tables. The effect is minor: in situations where the p2m entry is changed but the mfn is the same, the VTd tables will be unnecessarily flushed. old_entry is left untouched in the second case, since having a present old_entry will cause the an unnecessary check to be taken at

This patch series tidies up a few bits ofthe nested p2m code. The main thing it does is reorganize the locking so that most of the changes to nested p2m tables happen only under the p2m lock, and the nestedp2m lock is only needed to reassign p2m tables to new cr3 values. Changes since v1: - a few minor fixes - more sensible flushing policy in p2m_get_nestedp2m() - smoke-tested this time!