From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a + (XEN) mm.c:845:d20 Error getting mfn jd (pfn 84fd) from L1 entry 800000000246d467 for l1e_owner=20, pg_owner=32753 Date: Tue, 1 Dec 2009 11:14:40 -0500 Message-ID: <20091201161440.GA13941@phenom.dumpdata.com> References: <481249.38422.qm@web25602.mail.ukl.yahoo.com> <4A78CA69.3090105@goop.org> <0E87C0E865217944860BB378D2898000E1467F@srv-mail.apnos.int> <0E87C0E865217944860BB378D2898000E146B1@srv-mail.apnos.int> <4A7B306D.5080108@goop.org> <20091109235051.GA20408@phenom.dumpdata.com> <20091201031120.GA11230@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline 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: Markus Armbruster Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, JBeulich@novell.com, Ian.Campbell@eu.citrix.com, Olivier NOEL , keir.fraser@eu.citrix.com List-Id: xen-devel@lists.xenproject.org > I recommend against 3). > > 2.6.18's xenfb doesn't rely on deferred I/O, because that didn't exist > then. It rolls its own code to do pretty much the same. The code is > hairy (it took us a few iterations to get it working reliably), and > there's still a race left in it[*]. It makes much more sense to solve > such a hairy problem in just one place (fb_defio.c), and make that > sufficiently capable for all uses. Moreover, I'd wager that in-tree > fb_defio.c has been reviewed much more thoroughly than the out-of-tree > 2.6.18 xenfb.c. Wow. Thanks for saving me from going into that rat-hole! Will definitly look at the 1a) solution.