RE: [Xen-devel] Xen 4.0.1-rc4 and stable 2.6.32.x pvops won't start xend

["Rose, Gregory V" <gregory.v.rose@xxxxxxxxx>]

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
>bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Rose, Gregory V
>Sent: Tuesday, July 20, 2010 8:53 AM
>Subject: RE: [Xen-devel] Xen 4.0.1-rc4 and stable 2.6.32.x pvops won't
>start xend
>
>>-----Original Message-----
>>From: Pasi Kärkkäinen [mailto:pasik@xxxxxx]
>>Sent: Tuesday, July 20, 2010 2:05 AM
>>To: Rose, Gregory V
>>Subject: Re: [Xen-devel] Xen 4.0.1-rc4 and stable 2.6.32.x pvops won't
>>start xend
>>
>>>
>>
>>Does that help?
>
>Well, it tells me what is wrong but not how to fix it...
>
>;-)
>
>For some reason the stable-2.6.32x branch doesn't have the
>drivers/xen/gntdev driver source in it while the 2.6.31 kernel does.
>Beats me why...
>
>When I run menuconfig in the 2.6.31 kernel I see the option for
>XEN_GNTDEV but not in the 2.6.32 kernel.  Copying the config from 2.6.31
>to 2.6.32 doesn't help because the driver module is missing from the
>tree and just won't show up.
>
>I'll go search the archives some more and see if I can find any answers.

OK, I was working off of a special branch created by Jeremy to test the SR-IOV 
patches that allow for setting the VF MAC and VLAN from the host VMM using 
RTNETLINK messages and netdev ops.  That branch doesn't include the gntdev.c 
device.  When I switched back to the xen/stable-2.6.32.x branch it was back 
again.  My confusion I guess, I was under the impression Jeremy's sr-iov branch 
was based on the stable-2.6.32.x branch that I had originally posted my patches 
against.  Evidently they're not.

I'm going to chalk it up to code management and branching confusion...

- Greg



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