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

[Xen-devel] Re: [PATCH 2/3] fbdev: Make deferred I/O work as advertized

To: "Markus Armbruster" <armbru@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 2/3] fbdev: Make deferred I/O work as advertized
From: "Jaya Kumar" <jayakumar.lkml@xxxxxxxxx>
Date: Tue, 26 Feb 2008 10:01:16 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, linux-fbdev-devel@xxxxxxxxxxxxxxxxxxxxx, dmitry.torokhov@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, linux-input@xxxxxxxxxxxxxxx, adaplas@xxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 27 Feb 2008 08:19:06 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=W1XBWzQ5nQy2THiVR4LitQMPzInCkV5MUQY60/nE10s=; b=w36P/y46lg4om7OpzyoTiC3gDaOPDcEGucs/eulI1C2UWQDXLD3W5DzqofBypw0G4c/Vq+e0dXy9tyPQPuw65F0iQq2rVnTBfu87MWgdcH9pKM94P70Agu9ljsNb1RrQI03hY1Vw8QGonp6bFAB3u8BkmRY5Z+ileRy+y3h3CBo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QhMJsW5yCeSguRpZmHhuLLonCwfc7AqFFVdb3vS+WZoCp/UtahpUWR4sBOu6SyjP4QBZcVBaOafFzS2KGoaEQJgMUvnyG7plXf5uSxVDe8bpDozShxZqFDXrc0fVUhNOsSlbNCYgHYQQRm0WfGajLVrQpd563RP/re29yC3xggw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <871w6z6ajs.fsf@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <87tzjx6vj3.fsf@xxxxxxxxxxxxxxxxx> <87k5kt6vd3.fsf@xxxxxxxxxxxxxxxxx> <45a44e480802260611l5a8d0bc9k9cc967bc73b88fac@xxxxxxxxxxxxxx> <871w6z6ajs.fsf@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Feb 26, 2008 at 9:45 AM, Markus Armbruster <armbru@xxxxxxxxxx> wrote:
>
>  What about pushing the fb_defio fixes independently of any new
>  fb_defio users?  If fb_defio was worth merging into Linus's tree, it
>  should be worth fixing there, whether new users are in shape already
>  or not.

I think that Andrew's message is saying that there may be a race
condition in the defio patch itself as opposed to the defio user
patch.

If there is no race condition or other problems, then I think it would
make sense to merge the defio patch independent of metronomefb or
other new patches that use defio.

Thanks,
jaya

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