From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: TMEM + pv_ops kernel? Date: Sat, 15 May 2010 13:03:35 -0700 Message-ID: <4BEEFE17.9060509@goop.org> References: <4BEC7A56.1050707@buzz-media.com> <614bc626-d7e1-449a-bcbe-3f783f52dcd6@default 4BEDD0E0.8070502@buzz-media.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: Rick Boone , xen-devel@lists.xensource.com, konrad.wilk@oracle.com List-Id: xen-devel@lists.xenproject.org On 05/14/2010 03:59 PM, Dan Magenheimer wrote: > > Hi Rick =96 > > > Which exact pv_ops tree do you expect to use? The Linux patch is > slightly different on each Linux version and I don=92t know if/how > patches such as tmem will get transferred across Jeremy=92s and Konrad=92= s > different pv_ops trees. > Since the tmem patches seem to be settling down, I was waiting a bit to see if they get into an upstreamable state for this next merge window (though that's getting pretty tight at this point). But if we can set up a git branch based on 2.6.32 we should be able to easily merge it into all the various pvops branches. Are there any tmem changes needed between .32 and later kernels? J