Xen project Mailing List

[XenARM] Xen-ARM and paravirt_ops?

To: "xen-arm@xxxxxxxxxxxxxxxxxxx" <xen-arm@xxxxxxxxxxxxxxxxxxx>, "sbuk.suh@xxxxxxxxxxx" <sbuk.suh@xxxxxxxxxxx>, "keir@xxxxxxx" <keir@xxxxxxx>, "community.manager@xxxxxxx" <community.manager@xxxxxxx>

From: maheen butt <maheen_butt26@xxxxxxxxx>

Date: Thu, 9 Aug 2012 22:45:00 -0700 (PDT)

Delivery-date: Fri, 03 May 2013 12:35:04 +0000

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=VynNME7JCbO+QJxWGzbQpLXuzSoSqtHzaq9tR2RxWchqvdwcODxF5qERrLUJOzgWC8fW376ViJb0czRHs74RIALoOoooj1Sx4l9kAKwUl7fOcP2FuzwIbOkdruSdzn7glIhlddjolmZLCcSgt3OynZ0ODxAZYSsJx2oug3ZIOwE=;

List-id: List for Xen ARM developers and users <xen-arm.lists.xen.org>

Hi,

I came to know from Xen-ARM wiki and other related pages that ARM port is based on

xen-unstable and it can boot a Linux 3.0 based virtual machine (dom 0). for reference

https://lkml.org/lkml/2011/11/29/265

As Xen-ARM can boot Linux 3.0, it means that this hypervisor is using

paravirt_ops infrastructure of kernel. I want to know that did you explicitly

add paravirt_ops support in kernel for ARM?

As far as I know paravirt_ops is an infrastructure given by Linux kernel to support

hypervisor. and http://wiki.xensource.com/xenwiki/XenParavirtOps tells that

at present paravirt_ops is available for x86_32, x86_64 and ia64 architectures.

If this the case that you have add support of paravirt_ops in Linux kernel for ARM

architecture then what is the level of complexity for adding this kind of support?

Thanks

_______________________________________________ Xen-arm mailing list Xen-arm@xxxxxxxxxxxxx http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm