RE: [Xen-devel] [PATCH] Paging and memory sharing for HVM guests

[Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>]

With the missing patch present, applying in the
order of series worked fine.  Against 20656 (tip as
of 117 minutes ago), there are about 14
hunks with an offset, but those are unlikely
to be any problem.

Thanks!
Dan

> -----Original Message-----
> From: Patrick Colp [mailto:pjcolp@xxxxxxxxx]
> Sent: Wednesday, December 16, 2009 5:00 PM
> To: Dan Magenheimer
> Cc: Grzegorz Milos; xen-devel@xxxxxxxxxxxxxxxxxxx; Andrew Peace; Keir
> Fraser
> Subject: Re: [Xen-devel] [PATCH] Paging and memory sharing for HVM
> guests
> 
> 
> Oops! I've attached the missing patch.
> 
> The easiest way to apply them is to use a mercurial patch 
> queue, but simply 
> applying them in order of the series file works too. Did the 
> patches that 
> failed fail before or after this missing one? If after, then 
> try again with 
> this patch and see if there are still any problems. If 
> before, which patches?
> 
> The queue was refreshed against revision 20683, pulled 
> yesterday morning.
> 
> 
> Patrick
> 
> 
> Dan Magenheimer wrote:
> > Hi Gregor and Patrick --
> > 
> > Congrats!
> > 
> > Could you provide instructions on how to apply them
> > to xen-unstable tip?  I tried applying them using
> > "patch -p1" in the order given in the file "series"
> > and most applied but I got a handful of failed hunks
> > and even one patch file missing altogether
> > (...pfec_page_paged.patch).
> > 
> > (Just xen patches, no Linux patches tried yet.)
> > 
> > Thanks,
> > Dan
> > 
> >> -----Original Message-----
> >> From: Grzegorz Milos [mailto:gm281@xxxxxxxxx]
> >> Sent: Wednesday, December 16, 2009 4:15 PM
> >> To: xen-devel@xxxxxxxxxxxxxxxxxxx; Patrick Colp; Andrew Peace; Keir
> >> Fraser
> >> Subject: [Xen-devel] [PATCH] Paging and memory sharing for 
> HVM guests
> >>
> >>
> >> The series of 46 patches attached to this email contain the initial
> >> implementation of memory paging and sharing for Xen. Patrick Colp
> >> leads the work on the pager, and I am mostly responsible for memory
> >> sharing. We would be grateful for any comments/suggestions 
> you might
> >> have. Individual patches are labeled with comments describing their
> >> purpose and a sign-off footnote. Of course we are happy to discuss
> >> them in more detail, as required. Assuming that there are no major
> >> objections against including them in the mainstream 
> xen-unstable tree,
> >> we would like to move future development to that tree.
> >>
> >> Thanks
> >> Patrick & Gregor
> >>
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
>

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