Re: [Xen-devel] [HYBRID]: status update...

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

I hope this isn't bikeshedding; but I don't like "Hybrid" as a name
for this feature, mainly for "marketing" reasons.  I think it will
probably give people the wrong idea about what the technology does.
PV domains is one of Xen's really distinct advantages -- much simpler
interface, lighter-weight (no qemu, legacy boot), &c &c.  As I
understand it, the mode you've been calling "hybrid" still has all of
these advantages -- it just uses some of the HVM hardware extensions
to make the interface even simpler / faster.  I'm afraid "hybrid" may
be seen as, "Even Xen has had to give up on PV."

Can I suggest something like "PVH" instead?  That (at least to me)
makes it clear that PV domains are still fully PV, but just use some
HVM extensions.

Thoughts?

 -George

On Wed, Jun 27, 2012 at 2:17 AM, Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> wrote:
> Hi Guys,
>
> Just a quick status update. I refreshed my trees and then debugged as
> the code had changed a lot. I'm again few weeks behind from the latest
> tree on both linux and xen. After the refresh, I ran into few issues:
>
>    - xenstored is using gnttab interface that will not work for hybrid
>      For now I just disabled it.
>
>    - libxl has changed a lot, so for now, I'm only supporting
>           disk = ['phy:/dev/loop1,xvda,w']
>
>    - the struct pv_vcpu and hvm_vcpu are into a union now. I added a new
>      type hyb_vcpu and now going thru the code changing all refs.
>
>    - on the linux side I managed to remove all changes to non-xen files,
>      this should help a alot.
>
> Once I finish the changes for hyb_vcpu union, I should be able to get
> things working again. Then I'll refresh the linux tree, keeping xen the
> same, and test it all out and submit linux patch. After that I'll
> refresh xen tree and keeping same linux, test it out, and submit patch.
>
> Thanks,
> Mukesh
>
>
> _______________________________________________
> 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