xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir.xen@gmail.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: PVH phase I complete....
Date: Mon, 2 Jun 2014 16:47:19 -0700	[thread overview]
Message-ID: <20140602164719.69992db5@mantra.us.oracle.com> (raw)

Yay.... 

    author	Mukesh Rathor <mukesh.rathor@oracle.com>	
    Mon, 2 Jun 2014 08:32:22 +0000 (10:32 +0200)
    committer	Jan Beulich <jbeulich@suse.com>	
    Mon, 2 Jun 2014 08:32:22 +0000 (10:32 +0200)
    commit	e6390ad57bdf11881e6375f6227b5a594b4bcc3f

and with that many thanks to all, specially Jan Beulich for all the
reviewing. Also thanks to Tim Deegan and those reviewing the linux side.
It's been fun, often arduous, developing the feature that found 
me hacking linux schedular one day, and xen pv mmu the other..  In the
end it feels worth it - I personally know of one banking customer who has 
been waiting anxiously for pvh for about 3 years now.

But we are not completely done, here is my list of pending items in random
order:

  - add mem removed by holes to end of memmap and send dom0 custom e820
          : Roger on xen/BSD side, David V on linux side

  - AMD port: i'm looking at it (grrr those invalid guest states.....)

  - MSI-x support: last I recall, it needed some work on the linux side. 
  
  - tsc emulation support
                  
  - migration 

  - passthru

  - 32bit guest kernel support

  - PIRQ EOI: I believe the xen work on this got done, and it seems to be
    working, so I think the comment in linux is outdated in xen_init_IRQ:
    
         /* TODO: No PVH support for PIRQ EOI */
         if (rc != 0) {
             free_page((unsigned long) pirq_eoi_map);
             pirq_eoi_map = NULL;
         ....

    Konrad, David: is there anything more to be done here you can think of?

  - control domain : p2m must be cleaned of any foreign types (refcnt released)

  - Shadow: at present HAP is required

  - Roger, you had a small patch for guest shutdown crashing the guest
    occassionally. It had to do something with a bit in one of the CRs iirc.

  - performance: last i ran lmbench, some othe numbers for pvh were not the
                 best of pv and hvm.

thanks,
Mukesh

             reply	other threads:[~2014-06-02 23:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 23:47 Mukesh Rathor [this message]
2014-06-03 13:34 ` PVH phase I complete Konrad Rzeszutek Wilk
2014-06-03 19:32   ` Mukesh Rathor

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=20140602164719.69992db5@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=david.vrabel@citrix.com \
    --cc=keir.xen@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=tim@xen.org \
    /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).