Displaying 3 results from an estimated 3 matches for "p2m_ram_broken".
2012 Oct 31
0
[PATCH 00/02] broken page handle wrt migration
...before migration, and the broken page occur during migration.
Patch 01 handles the case that broken page occurred before migration: At the sender, the broken page would not be copied to target while its pfn_type and pfn number would be transferred to target, so that at target, it would set p2m as p2m_ram_broken for broken page.
Patch 02 handles the case that broken page occurred during migration: At the sender, marks the broken page to dirty bitmap, so that at copypages stage of migration, its pfn_type and pfn number would transfer to target. At the target, it would set p2m as p2m_ram_broken for broken p...
2012 Dec 12
2
[PATCH v7 1/2] xen: unify domain locking in domctl code
These two patches were originally part of the XSM series that I have
posted, and remain prerequisites for that series. However, they are
independent of the XSM changes and are a useful simplification
regardless of the use of XSM.
The Acked-bys on these patches were provided before rebasing them over
the copyback changes in 26268:1b72138bddda, which had minor conflicts
that I resolved.
[PATCH
2013 Dec 06
36
[V6 PATCH 0/7]: PVH dom0....
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