On Sun, Mar 01, 2009 at 05:12:25PM +0800, Zhang, Yang wrote:
Isaku Yamahata wrote:
- The pages for vhpt is allocated by alloc_domheap_pages(NULL, ...),
Thus those memory doesn't accounted to the domain.
So adjusting domain memory size doesn't make sense. Just drop it.
In the previous
Isaku Yamahata wrote:
As you described above, you used alloc_domheap_page(NULL, ) which
means that pages for vhpt aren't accounted for a given domain.
So the hunk in tools/python/xen/xend/image.py doesn't make sense,
does it? Or have you found any issues without the modification to
image.py?
On Mon, Mar 02, 2009 at 05:38:22PM +0800, Zhang, Yang wrote:
Isaku Yamahata wrote:
As you described above, you used alloc_domheap_page(NULL, ) which
means that pages for vhpt aren't accounted for a given domain.
So the hunk in tools/python/xen/xend/image.py doesn't make sense,
does it? Or
Isaku Yamahata wrote:
So you want to account vhpt memory.
Then, pass the domain pointer as argument to alloc_domheap_page(d,
...) and leave the hunk in image.py.
Maybe the code path which frees domain memory needs twist.
it doesn't pass the domain pointer as argument. There are separate
On Mon, Mar 02, 2009 at 07:21:28PM +0800, Zhang, Yang wrote:
Isaku Yamahata wrote:
So you want to account vhpt memory.
Then, pass the domain pointer as argument to alloc_domheap_page(d,
...) and leave the hunk in image.py.
Maybe the code path which frees domain memory needs twist.
it
Isaku Yamahata wrote:
You want to balloon the memory for vhpt from dom0 and don't want to
allocate the memory by alloc_domheap_page() with explicit domain
pointer.
Then, IA64_HVM_ImageHandler::getRequiredAvailableMemory() is wrong
place to modify.
Please see _initDomain() in
Hi, Tristan
Attached patch targets for fixing the issue when assigning the devices
with 64-bit bars. Current logic may deem one 64-bit bar as two 32-bit bars, and
make the system crash finally.
Thanks
Xiantao
fix-64-bit-bars-in-pci-scan.patch
Description:
PATCH: Fix the logic when deassign the mmio ranges for vti-domain.
When de-assign the mmio range, it should resume its original value
for p2m value, otherwise, it may fail to determin mmio range's type.
Signed-off-by: Xiantao Zhang xiantao.zh...@intel.com
diff -r 67f2e14613ef
