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

Re: [Xen-devel] xen.git branch reorg / success with 2.6.30-rc3 pv_ops do

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] xen.git branch reorg / success with 2.6.30-rc3 pv_ops dom0
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Tue, 9 Jun 2009 16:37:52 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 09 Jun 2009 08:38:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090609145311.GO24960@xxxxxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <1244217948.27370.213.camel@xxxxxxxxxxxxxxxxxxxxxx> <1244218353.27370.216.camel@xxxxxxxxxxxxxxxxxxxxxx> <20090605181925.GC24960@xxxxxxxxxxxxxxx> <1244475935.27370.309.camel@xxxxxxxxxxxxxxxxxxxxxx> <1244476858.27370.325.camel@xxxxxxxxxxxxxxxxxxxxxx> <20090608161329.GG24960@xxxxxxxxxxxxxxx> <1244477865.27370.329.camel@xxxxxxxxxxxxxxxxxxxxxx> <20090608162146.GH24960@xxxxxxxxxxxxxxx> <20090608170543.GJ24960@xxxxxxxxxxxxxxx> <20090608191141.GL24960@xxxxxxxxxxxxxxx> <20090609145311.GO24960@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2009-06-09 at 10:53 -0400, Pasi Kärkkäinen wrote:
> 
> 
> And here's one with only the second patch applied:
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-log-07-with-highpte-no-swap-with-debug5.txt
> 
> Now Xen is complaining again.. does that sound correct?

Well, it suggests my theory around pte locking and split pte locks may
be invalid... I guess even without split pte locks the call to
kmap_atomic_pte from page_check_address() is still outside
mm->page_table_lock and hence subject to the race.

Without redoing the core locking rules I'm not sure what we could do
about that. Perhaps as a workaround always doing kmap_atomic_pte as a
read only mapping would be sufficient (it seems to be in this particular
call chain which never writes the pte but I didn't check them all and I
guess some of them must want to write).

Does this patch (without any of the others) make any difference to you?

--- a/arch/x86/xen/mmu.c
+++ b/arch/x86/xen/mmu.c
@@ -1522,7 +1522,7 @@ static void *xen_kmap_atomic_pte(struct page *page, enum 
km_type type)
 {
        pgprot_t prot = PAGE_KERNEL;
 
-       if (PagePinned(page))
+       if (1 || PagePinned(page))
                prot = PAGE_KERNEL_RO;
 
        if (0 && PageHighMem(page))


Ian.



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

<Prev in Thread] Current Thread [Next in Thread>