Re: [Xen-ia64-devel] [PATCH 0/5] [P2M/VP step 3]

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

On Wed, May 10, 2006 at 05:04:12PM -0600, Alex Williamson wrote:
> On Wed, 2006-05-10 at 15:46 +0900, Isaku Yamahata wrote:
> > The following patches are the P2M/VP step 3.
> > These patches are only for preparetion patches.
> > I don't expect that these patches affect on stability.
> > 
> > Subject: [PATCH 1/5] [P2M/VP step 3] linux: ia64 Kconfig
> > Subject: [PATCH 3/5] [P2M/VP step 3] linux: ia64 coreMakefile clean up
> > Subject: [PATCH 2/5] [P2M/VP step 3] linux: ia64 drivers Makefile clean up
> > Subject: [PATCH 4/5] [P2M/VP step 3] linux: maddr_t definition to compile 
> > netback and netfront
> > Subject: [PATCH 5/5] [P2M/VP step 3] linux: MULTI_update_va_mapping to 
> > copmile netback and netfront
> 
>    Applied.  Are we still on track for the 5 step plan to incorporate
> all of p2m/vp?  I was initially thinking we might have working
> networking after step 3.  Thanks,

Probably networking works with step 3. But I haven't tested it.
I only tested networking with the step 4 patches.

The P2M/VP merge effort will be finished with the step 4 patches.
It will includes three patches.
(balloon_driver_xen.patch, remove_dom0vp_populate_physmap_xen.patch,
remove_populate_physmap_linux.patch)
I'm going to post the step 4 patches today or tomorrow.
The original plan has the 5 steps, but the step 5 becomes unnecessary.
There still remains the patches related to domain destruction,
however I plan to post them independet patches because some debugging
is needed which might take time.

I think the final step is to switch the default configuration.
This must be after thorough regression tests.
-- 
yamahata

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