From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Stodden Subject: RE: Domain 0 stop response on frequently reboot VMS Date: Tue, 26 Oct 2010 02:09:52 -0700 Message-ID: <1288084192.2221.175.camel@ramone> References: ,,, ,, ,,<1287436670.23170.43.camel@agari.van.xensource.com> , ,<1287899811.4575.32.camel@ramone> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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: MaoXiaoyun Cc: xen devel List-Id: xen-devel@lists.xenproject.org On Tue, 2010-10-26 at 04:16 -0400, MaoXiaoyun wrote: > > Well, where can I start if I want to maintain the current > kernel(2.6.31), and only update the blktap2? > As I go throught the git branch of > xen/dom0/backend/blktap2, I found wait_queue.c is removed. > It looks like blktap2 has changed a lot, right? > So I am courious the difference between the new and the old one. > Could you share some brief explainations, that would be very > helpful. > Thanks in advance. For brief explanations but nothing particular I can only refer you to the commit messages. Because there have been plenty of them. :) They're all still backward compatible as far as the userspace ABI for older tapdisk2s goes. My recommendation would be replacing that whole blktap/ directory, because I can't support you with more than that. If you choose to do so: You might need some patches fixing request queue accesses, there might be slight differences to 2.6.32, that's a bit of a moving target sometimes. But it's not a big deal. Daniel