WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] upstream merge status for 2.6.35, .36?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] upstream merge status for 2.6.35, .36?
From: Łukasz Oleś <lukaszoles@xxxxxxxxx>
Date: Wed, 4 Aug 2010 23:09:01 +0200
Delivery-date: Wed, 04 Aug 2010 14:10:40 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=uAFeLryZ5UDYVsb0kSXmk9OBxo6rmDzTb5sBHj+AW00=; b=EeKO4knPbJlUGKXN5zu7sGaezwvnkn27c22ogFdTxpg+kRr4exsfXgpy9ZuMmX0tLJ /IaqFEvV/nkGJ4mg5fiz/fYN1wuG6uCr64z6IVYqkV9l7NsslcGjG2FhWeps6AvV+rCM qNr1OYYP3aDC79GzyT7YlWn6CUsklfZPEaoCg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=LFr5pgtFlCe0oMUwY1ludTlVvwO5a9dktuuUcfC1Ak24HrK+k1d5Q986iOzi1QuU3R jEz3Sv0CQe+cQ1MEcaEubmwpcgcyEShbvHC1pvT4ZZvAz+kxfI+KhSQB11RYo3WQy5sL NW4kRgSHYsYtqdFr7m04UhHF/JWYjhNPVRbPo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100804201100.GA16839@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100604223929.GA8819@xxxxxxxxxxxxxxx> <20100804194457.GA6914@xxxxxxxxxxxxxxx> <20100804201100.GA16839@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.3 (Linux/2.6.32-5-686; KDE/4.4.4; i686; ; )
On Wednesday 04 August 2010 22:11:00 Konrad Rzeszutek Wilk wrote:
> On Wed, Aug 04, 2010 at 09:44:57PM +0200, Josip Rodin wrote:
> > On Mon, Jun 07, 2010 at 10:57:43AM -0400, Konrad Rzeszutek Wilk wrote:
> > > So the SWIOTLB is 1 out 3. The next component is:
> > > 
> > > 2). Xen SWIOTLB. This is the xen swiotlb code that utilizes the swiotlb
> > > proper that was just made generic enough to be used in this capacity.
> > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb-2.6.git
> > > xen-swiotlb-0.8.2
> > > 
> > > 3). and then the Xen PCI front. Which utilizes the Xen-SWIOTLB (and
> > > also the Xen PCI), to well, allow guests to have PCI devices passed
> > > in.
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> > > pv/pcifront-2.6.34
> > > 
> > > The 2) and 3) are mostly Xen specific so they should be much more
> > > palpable than the first one.
> > 
> > JFTR these now look to be:
> > 
> > http://lkml.org/lkml/2010/8/2/289 [ SWIOTLB GIT PULL ]
> > http://lkml.org/lkml/2010/7/27/246 [ Xen-SWIOTLB]
> > http://lkml.org/lkml/2010/8/4/374 [ RFC Xen PCI patches]
> > 
> > But in the latter you wrote that you don't expect #2 to get in the 2.6.36
> > merge window. Why? I saw a single tentative complaint from hpa on one
> 
> No. The #2 is right now brewing in linux-next and I am thinking to ask
> Linus to pull it next week.

Linus merged it today 
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4a35cee066df1b1958e25e71595b3845d06b192e
  
:)

--
Łukasz Oleś

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