|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: mm.c:777:d2 Non-privileged (2) attempt to map I/O sp
To: |
Markus Armbruster <armbru@xxxxxxxxxx> |
Subject: |
Re: [Xen-devel] 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 |
From: |
Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> |
Date: |
Tue, 1 Dec 2009 11:14:40 -0500 |
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, JBeulich@xxxxxxxxxx, Ian.Campbell@xxxxxxxxxxxxx, Olivier NOEL <ONOEL@xxxxxxxxxxxxxx>, keir.fraser@xxxxxxxxxxxxx |
Delivery-date: |
Tue, 01 Dec 2009 08:17:30 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<m3skbvkptu.fsf@xxxxxxxxxxxxxxxxxxxxx> |
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: |
<481249.38422.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A78CA69.3090105@xxxxxxxx> <0E87C0E865217944860BB378D2898000E1467F@xxxxxxxxxxxxxxxxxx> <0E87C0E865217944860BB378D2898000E146B1@xxxxxxxxxxxxxxxxxx> <4A7B306D.5080108@xxxxxxxx> <20091109235051.GA20408@xxxxxxxxxxxxxxxxxxx> <20091201031120.GA11230@xxxxxxxxxxxxxxxxxxx> <m3skbvkptu.fsf@xxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.5.19 (2009-01-05) |
> 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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|