From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Kvasnica Subject: Re: vscsi 2TB patches Date: Tue, 4 Jan 2011 15:46:43 +0100 Message-ID: <4D2332D3.3010105@list.ims.co.at> References: <4D222D71.9020508@list.ims.co.at> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-path: In-Reply-To: <4D233968020000780002A36E@vpn.id2.novell.com> References: <20110103230621.GP2754@reaktio.net> References: <4D230357.3070604@list.ims.co.at> References: <4D231647020000780002A2EE@vpn.id2.novell.com> References: <4D231A46.2000209@list.ims.co.at> References: <4D232ADB020000780002A33B@vpn.id2.novell.com> References: <4D2321DE.9030706@list.ims.co.at> References: <4D233968020000780002A36E@vpn.id2.novell.com> 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: Jan Beulich , =?ISO-8859-1?Q?Pasi_K=E4rkk=E4in?= =?ISO-8859-1?Q?en?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi Pasi, we had some discussion with Jan in the background: On 01/04/2011 03:14 PM, Jan Beulich wrote: >>>> On 04.01.11 at 14:34, Samuel Kvasnica wrote: >>> Did you *try* whether it applies to the 2.6.18 tree? And in order >>> for it to be applied (given that the 2.6.18 tree is legacy and not >>> fully maintained anymore), you'd also have to specifically indicate >>> that it's intended for that tree in the subject, otherwise Keir will >>> just ignore any Linux patches, assuming they're destined for >>> pv-ops. >> well, never tried 2.6.18 and I did not even assume xen community still >> sticks to 2.6.18 tree >> for whatever strange reasons. There is no way to even boot 2.6.18 in my >> case, so lets forget >> about it, not going to submit patch without testing it on real system. > In all reality that's what happens quite frequently. Pasi: do you see a possibility to try it out on 2.6.18 ? I'm not sure if anybody from Fujitsu takes actively care, it is quite old code. >> Well, ok, so now whats the procedure to get this by default at least to >> opensuse kernel ? > If it is reasonably applicable to the 2.6.18 kernel, we prefer getting > it through that tree. Second choice would be to get it through the > pv-ops one, pointing us to the relevant commits. Third choice (we > actually did so only very few times thus far, and we're going to be > reluctant to take anything that could go through either of the > earlier paths) is to give us the patch on top of our HEAD/master > tree, accompanied by sufficient information on what the change > does and how was tested (so we can judge how likely regressions > from the patch might be). Jan: but if I understood Pasi, he claims there are no pvscsi drivers included in the pv-ops tree at all because it was not ported so far. But your opensuse pv-ops kernel definitely includes pvscsi drivers - does this part exist only in suse kernel tree ? Sam