[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-ia64-devel] [Patch] Add more dom0 operations


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Tue, 14 Jun 2005 22:06:54 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 14 Jun 2005 14:05:58 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcVw6lHOFIqjL7g+TIGKW2Kcakj/dw==
  • Thread-topic: [Patch] Add more dom0 operations

Hi, Dan,
        This patch adds more dom0 operations support, with following
notes:

1. Each architecture may have its own set of operations, so a new
dom0_ops_ia64.h is created temporarily. Later cleaner re-org should be
made. :)

2. Add a new hypercall DOM0_GET_SECTIONINFO, to get memory hole, I/O
port, etc in guest physical address space. This is necessary for CP and
DM to create foreign map, especially for VTI domain. As Ian said before,
para-virtualized x86 guest is configured with contiguous physical memory
without any hole. Though currently not required for para, keeping it
there at least provides a possibility for other variations. :)

3. I'm not sure why latest check-in about DOM0_GETMEMLIST differs much
from x86 behavior. Could you explain a bit about that? IMHO, XEN/IA64
can have same syntax as x86 easily, since page allocator already
aggregates available pages list under domain struct. So a different
version is provided enclosed by CONFIG_VTI. If we can set on the same
page later, it may be extracted out then.

Signed-off-by   Kevin Tian <Kevin.tian@xxxxxxxxx>

Thanks,
Kevin

Attachment: patch_domN_support_3
Description: patch_domN_support_3

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.