xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@xen.org>
To: xen-devel@lists.xensource.com, netlogic.xen@gmail.com
Subject: Re: MIPS port
Date: Tue, 31 Jan 2012 15:07:15 +0000	[thread overview]
Message-ID: <4F2803A3.60507@xen.org> (raw)
In-Reply-To: <CAPw52B_k1UUqBV0AtxHNfdsBGgAF9JRb7P2rtoQOUGE1yW2Htw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2369 bytes --]

Prasad,

I just saw the press announcement. Congratulations.

Seems nobody has come back regarding submitting changes. That is 
probably because you baselined on Xen 3.4. I guess we could look into 
publishing the code as a tarball, but to be honest this has not worked 
that well for the Xen ARM project and Samsung is going through the 
process of moving all the code into a repo.

I would much rather prefer if we created a repo (that could be baselined 
from the 3.4 branch). Basically, I wanted to double check whether you 
intend to move to xen-unstable and PVOPS and in what timeframe (months, 
years). It may make sense for you guys to send somebody to the Hackathon 
in Santa Clara - Konrad who runs the PVOPS project I think will be 
there. And many of the other devs too. And so will I. I understand you 
are based in Santa Clara?

Sign up here http://wiki.xen.org/wiki/Hackathon/March2012

It would also be great if you could introduce me to some marketing 
people. I want to make sure that you are listed at 
http://www.xen.org/community/vendors/XenProductsPage.html ; I also 
wanted to discuss other ways how Xen.org can help promote you guys as 
well as how you can help Xen (it is not only about code contributions).

Regards
Lars

On 05/01/2012 23:38, Prasad Boddupalli wrote:
> Hello All,
>
> About 3 weeks back, after resolving some console related issues, SMP 
> versions of PV dom0 and domU could be booted on our MIPS boards. Our 
> current version of MIPS Xen is based on an old version (3.4.0) and are 
> currently in the process of moving the changes to the unstable branch. 
> The Linux changes are not part of pv-ops infrastructure.
>
> Although we have our simulator, the plan is to get the above running 
> on Qemu to enable others try out the MIPS version of Xen. Linux could 
> be released as a tarball for the present.
>
> The performance of applications such as hackbench is a little 
> unsatisfactory when run on PV Linux (due to frequent traps in the 
> syscall path). So, we are also working on performance improvements, 
> which probably could go on in parallel with the submission to open source.
>
> Any suggestions with regard to submitting our changes are welcome.
>
> Prasad.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 3393 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

      parent reply	other threads:[~2012-01-31 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 23:38 MIPS port Prasad Boddupalli
2012-01-06 10:34 ` Stefano Stabellini
2012-01-06 12:00 ` Ian Campbell
2012-01-31 15:07 ` Lars Kurth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F2803A3.60507@xen.org \
    --to=lars.kurth@xen.org \
    --cc=netlogic.xen@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).