From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen devel <xen-devel@lists.xensource.com>
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 [thread overview]
Message-ID: <20111025181954.GC2566@phenom.dumpdata.com> (raw)
In-Reply-To: <4EA6F802.4010902@theshore.net>
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
next prev parent reply other threads:[~2011-10-25 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 13:13 [PATCH] x86/paravirt: Partially revert "remove lazy mode in interrupts" Konrad Rzeszutek Wilk
2011-09-26 13:13 ` Konrad Rzeszutek Wilk
2011-09-26 16:22 ` Jeremy Fitzhardinge
2011-09-26 19:34 ` Is: [PATCH] x86/paravirt: PTE updates in k(un)map_atomic need to be synchronous, regardless of lazy_mmu mode. Was: " Konrad Rzeszutek Wilk
2011-09-26 19:34 ` Konrad Rzeszutek Wilk
2011-09-30 9:59 ` Stefan Bader
2011-10-03 16:50 ` Konrad Rzeszutek Wilk
2011-10-03 17:04 ` Konrad Rzeszutek Wilk
2011-10-25 17:55 ` Christopher S. Aker
2011-10-25 18:19 ` Konrad Rzeszutek Wilk [this message]
2011-10-25 18:26 ` Konrad Rzeszutek Wilk
2011-09-30 14:22 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111025181954.GC2566@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=caker@theshore.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.