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

[Xen-devel] Xen port for MIPS


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: maheen butt <maheen_butt26@xxxxxxxxx>
  • Date: Thu, 30 Aug 2012 22:59:17 -0700 (PDT)
  • Delivery-date: Fri, 31 Aug 2012 06:00:06 +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:Content-Transfer-Encoding; b=Q841kOVELj6eyT51dJH52Defu1ZUbCHMjhSnTVJgafHUcy0YEEySJdZFSimvGtcmYe+Xmj1Pz8xgUOnDFx3zzunSFOdI+ldeiB6B8ATAW5i8hPdTR7f+Khr+ZEWqeasKkTdrtpTkOxsD0AzX3CYbh56fIpgmvdZsFG89GbKzyNE=;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

Hi all,

I want to port Xen for MIPS64 architecture as my MS thesis. My strategy
is that to know (some how) what are changes required to make a kernel into 
xen enabled kernel for x86 and try to change accordingly MIPS portion of the 
code.
Now I have two issues over here
1) The above strategy is for xen enabled kernel but have no clear picture for 
Xen hypervisor.
2) I'm currently working on 2.6.18 xenlinux. Why I'm not using the current 
version because 
newer kernels are using pv_ops. and there is no such interface exist for MIPS( 
considering that 
I'm following X86). I know my knowledge is very limited in case of pv_ops.

So anybody can guide me what should be correct strategy? and can I use newer
kernel (any thing having version >= 2.6.26) and xen-unstable but avoiding 
pv_ops as well?
we are two members in the team. Any guess how much time it will take?  

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

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