From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] x86: hold mm->page_table_lock while doing vmalloc_sync
Date: Thu, 21 Oct 2010 14:34:37 -0700
Message-ID: <4CC0B1ED.4050607@goop.org>
References: <4CB76E8B.2090309@goop.org> <4CC0AB73.8060609@goop.org> <4CC0B006.7040008@zytor.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <4CC0B006.7040008@zytor.com>
Sender: linux-kernel-owner@vger.kernel.org
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: the arch/x86 maintainers <x86@kernel.org>, "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Ian Campbell <Ian.Campbell@citrix.com>, Jan Beulich <JBeulich@novell.com>
List-Id: xen-devel@lists.xenproject.org

 On 10/21/2010 02:26 PM, H. Peter Anvin wrote:
> On 10/21/2010 02:06 PM, Jeremy Fitzhardinge wrote:
>>  Ping?  Have you had any thoughts about possible x86-64 problems with this?
>>
>> Thanks,
>>     J
> I didn't find any, so I already committed your patch to tip:x86/mm two
> days ago.

Oh, thanks!  I didn't see the tip commit.

> Now, it's worth noting that Linus has asked us to get rid of
> vmalloc_sync_all() completely, which would be a good thing in the longer
> term.

Fine by me.

    J