From: "Ky Srinivasan" Subject: Re: [PATCH][RESEND] PV drivers for HVM guests Date: Fri, 20 Oct 2006 07:54:43 -0600 Message-ID: <45389CA5.E57C.0030.0@novell.com> References: <4535F8F5.E57C.0030.0@novell.com>Your message of Wed, 18 Oct 2006 07:51:45 -0600. <4535F8F5.E57C.0030.0@novell.com> <200610182356.k9INuAF03840@photon.sky.yk.fujitsu.co.jp><45374AE9.E57C.0030.0@novell.com>Your message of Thu, 19 Oct 2006 07:53:42 -0600. <45374AE9.E57C.0030.0@novell.com> <200610201012.k9KACIF29714@photon.sky.yk.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200610201012.k9KACIF29714@photon.sky.yk.fujitsu.co.jp> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Doi.Tsunehisa@jp.fujitsu.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> On Fri, Oct 20, 2006 at 6:12 AM, in message <200610201012.k9KACIF29714@photon.sky.yk.fujitsu.co.jp>, wrote: > Hi, > > You (ksrinivasan) said: >> We intend to maintain the source for the unmodified drivers separately >> in our source tree. The idea is that this will track the official xen >> source tree; we would apply the patch to target this source for a >> particular unmodified guest target. This would eliminate the need to >> carry the compatibility baggage in the pristine unmodified driver code. > > I understand that it has to be separated from xen source tree for > maintenacne as products. But I think that we should avoid to fork the > source tree. Because its code structure is not stable, I think. > > What do you think about ? We are not forking tree. The pristine PV driver code will always be the exact code in the xen source tree. Regards, K. Y >