From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Is: [PATCH] x86/paravirt: PTE updates in k(un)map_atomic need to be synchronous, regardless of lazy_mmu mode. Was: Re: [PATCH] x86/paravirt: Partially revert "remove lazy mode in interrupts" Date: Tue, 25 Oct 2011 14:19:54 -0400 Message-ID: <20111025181954.GC2566@phenom.dumpdata.com> References: <1317042797-19975-1-git-send-email-konrad.wilk@oracle.com> <4E80A6BD.3070703@goop.org> <20110926193453.GA9717@phenom.oracle.com> <4E859312.40309@canonical.com> <20111003170401.GD4420@phenom.oracle.com> <4EA6F802.4010902@theshore.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4EA6F802.4010902@theshore.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Christopher S. Aker" Cc: xen devel List-Id: xen-devel@lists.xenproject.org On Tue, Oct 25, 2011 at 01:55:14PM -0400, Christopher S. Aker wrote: > >This patch fixes an outstanding issue that has been reported since > >2.6.37. Under a heavy loaded machine processing "fork()" calls could > >keepover with: > > I noticed this patch is not in Linux 3.1 -- was this fixed some > other way, or is it still in mainline's pipeline somewhere? Hmm, it was in Andrew's tree, but you are right - I am not seeing it in 3.1. Let me double check Andrew's tree. > > Thanks, > -Chris