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

Re: [Xen-devel] [PATCH 01/24] PVH xen: Add readme docs/misc/pvh-readme.txt



On Thu, Jul 18, 2013 at 11:32:00AM +0100, Jan Beulich wrote:
> >>> On 18.07.13 at 04:32, Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> wrote:
> > Signed-off-by: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>
> > ---
> >  docs/misc/pvh-readme.txt |   40 ++++++++++++++++++++++++++++++++++++++++
> >  1 files changed, 40 insertions(+), 0 deletions(-)
> >  create mode 100644 docs/misc/pvh-readme.txt
> > 
> > diff --git a/docs/misc/pvh-readme.txt b/docs/misc/pvh-readme.txt
> > new file mode 100644
> > index 0000000..a813373
> > --- /dev/null
> > +++ b/docs/misc/pvh-readme.txt
> > @@ -0,0 +1,40 @@
> > +
> > +PVH : a pv guest running in an HVM container. HAP is required for PVH.
> > +
> > +See: 
> > http://blog.xen.org/index.php/2012/10/23/the-paravirtualization-spectrum-p 
> > art-1-the-ends-of-the-spectrum/
> > +
> > +
> > +The initial phase targets the booting of a 64bit UP/SMP linux guest in PVH 
> > +mode. This is done by adding: pvh=1 in the config file. xl, and not xm, is 
> > +supported. Phase I patches are broken into three parts:
> > +   - xen changes for booting of 64bit PVH guest
> > +   - tools changes for creating a PVH guest
> > +   - boot of 64bit dom0 in PVH mode.
> > +
> > +The best way to find all the patches is to use "git log|grep -i PVH", both
> > +in xen and linux tree.
> 
> Which doesn't really say which tree. Do you mean the upstream
> ones or some private ones you maintain?

It is my upstream one:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/pvh.v8

or just follow the #linux-next branch which has them as well. I am
waiting for the trigger when I should push it to Linus.

> 
> > +
> > +Following fixme's exist in the code:
> > +  - Add support for more memory types in arch/x86/hvm/mtrr.c.
> > +  - arch/x86/time.c: support more tsc modes.
> > +  - check_guest_io_breakpoint(): check/add support for IO breakpoint.
> > +  - implement arch_get_info_guest() for pvh.
> > +  - vmxit_msr_read(): during AMD port go thru hvm_msr_read_intercept() 
> > again.
> > +  - verify bp matching on emulated instructions will work same as HVM for
> > +    PVH guest. see instruction_done() and check_guest_io_breakpoint().
> > +
> > +Following remain to be done for PVH:
> > +   - AMD port.
> > +   - 32bit PVH guest support in both linux and xen. Xen changes are tagged 
> > +     "32bitfixme".
> > +   - Add support for monitoring guest behavior. See hvm_memory_event* 
> > functions
> > +     in hvm.c
> > +   - vcpu hotplug support
> > +   - Live migration of PVH guests.
> > +   - Avail PVH dom0 of posted interrupts. (This will be a big win).
> > +
> > +
> > +Note, any emails to must be cc'd to Xen-devel@xxxxxxxxxxxxxxxxxxxx
> 
> Please let's not add more references to this super stale mailing
> list. It had been @lists.xen.org for a couple of years, and recently
> changed to @lists.xenproject.org.
> 
> Also there must be something missing between "to" and "must"...
> 
> Jan
> 
> > +
> > +Mukesh Rathor
> > +mukesh.rathor [at] oracle [dot] com
> > -- 
> > 1.7.2.3
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxx 
> > http://lists.xen.org/xen-devel 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

_______________________________________________
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®.