Hi guys,
Ok, I've made all the changes from prev RFC patch submissions. Tested
all the combinations. The patches are organized slightly differently
from prev version because of the nature of changes after last review. I
am building xen patch just for the corresponding header file changes.
Following that I'll refresh xen tree, debug, test, and send patches.
For linux kernel mailing list introduction, PVH is a PV guest that can
run in an HVM container, uses native pagetables, uses callback vector,
native IDT, and native syscalls.
They were built on top of 89d0307af2b9957d59bfb2a86aaa57464ff921de
commit.
thanks,
Mukesh
On Thu, 2012-10-11 at 22:49 +0100, Mukesh Rathor wrote:
> Hi guys,
>
> Ok, I've made all the changes from prev RFC patch submissions. Tested
> all the combinations. The patches are organized slightly differently
> from prev version because of the nature of changes after last review. I
> am building xen patch just for the corresponding header file changes.
> Following that I'll refresh xen tree, debug, test, and send patches.
>
> For linux kernel mailing list introduction, PVH is a PV guest that can
> run in an HVM container, uses native pagetables, uses callback vector,
> native IDT, and native syscalls.
>
> They were built on top of 89d0307af2b9957d59bfb2a86aaa57464ff921de
> commit.
I took a (fairly quick) look. I had a few comments but overall looks
pretty good, thanks!
I'm constantly amazed by how small this patchset is. I suspect you are
going to make up for it in the hypervisor side ;-)
Ian.
On Fri, 12 Oct 2012 10:18:31 +0100
Ian Campbell <[email protected]> wrote:
> On Thu, 2012-10-11 at 22:49 +0100, Mukesh Rathor wrote:
> > Hi guys,
> >
> > Ok, I've made all the changes from prev RFC patch submissions.
> > Tested all the combinations. The patches are organized slightly
> > differently from prev version because of the nature of changes
> > after last review. I am building xen patch just for the
> > corresponding header file changes. Following that I'll refresh xen
> > tree, debug, test, and send patches.
> >
> > For linux kernel mailing list introduction, PVH is a PV guest that
> > can run in an HVM container, uses native pagetables, uses callback
> > vector, native IDT, and native syscalls.
> >
> > They were built on top of 89d0307af2b9957d59bfb2a86aaa57464ff921de
> > commit.
>
> I took a (fairly quick) look. I had a few comments but overall looks
> pretty good, thanks!
>
> I'm constantly amazed by how small this patchset is. I suspect you are
> going to make up for it in the hypervisor side ;-)
Hehe... yes! The patch has become almost half since I first got it
working. Each review trims it down :).
thanks
Mukesh
On Thu, 2012-10-11 at 22:49 +0100, Mukesh Rathor wrote:
> Hi guys,
>
> Ok, I've made all the changes from prev RFC patch submissions. Tested
> all the combinations. The patches are organized slightly differently
> from prev version because of the nature of changes after last review. I
> am building xen patch just for the corresponding header file changes.
> Following that I'll refresh xen tree, debug, test, and send patches.
>
> For linux kernel mailing list introduction, PVH is a PV guest that can
> run in an HVM container, uses native pagetables, uses callback vector,
> native IDT, and native syscalls.
>
> They were built on top of 89d0307af2b9957d59bfb2a86aaa57464ff921de
> commit.
Are they in a git branch anywhere?
On Mon, 15 Oct 2012 17:15:43 +0100
Ian Campbell <[email protected]> wrote:
> On Thu, 2012-10-11 at 22:49 +0100, Mukesh Rathor wrote:
> > Hi guys,
> >
> > Ok, I've made all the changes from prev RFC patch submissions.
> > Tested all the combinations. The patches are organized slightly
> > differently from prev version because of the nature of changes
> > after last review. I am building xen patch just for the
> > corresponding header file changes. Following that I'll refresh xen
> > tree, debug, test, and send patches.
> >
> > For linux kernel mailing list introduction, PVH is a PV guest that
> > can run in an HVM container, uses native pagetables, uses callback
> > vector, native IDT, and native syscalls.
> >
> > They were built on top of 89d0307af2b9957d59bfb2a86aaa57464ff921de
> > commit.
>
> Are they in a git branch anywhere?
>
not in a public accessible location. we are very close to getting this
done (it appears ;)), and once konrad puts in his tree it should be
publicly available.
thanks
mukesh