linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Hong H. Pham" <hong.pham@windriver.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	linux-stable <stable@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v3] powerpc: Fix PTE page address mismatch in pgtable ctor/dtor
Date: Sun, 15 Dec 2013 13:59:33 +0100	[thread overview]
Message-ID: <20131215125933.GB31090@linutronix.de> (raw)
In-Reply-To: <1386425193-24015-1-git-send-email-hong.pham@windriver.com>

* Hong H. Pham | 2013-12-07 09:06:33 [-0500]:

>On PPC32, only SMP kernels are affected.
>
>On PPC64, only SMP kernels with 4K page size are affected.

$ uname -a
Linux mpc8536-1 3.12.1-rt3-00281-g9de268d #76 SMP PREEMPT RT Fri Nov 22 16:53:05 CET 2013 ppc GNU/Linux
$ uptime
 22:01:10 up 22 days, 21:01,  1 user,  load average: 443.08, 563.59, 586.20

This is from a mpc8536 box. The high load comes from a hackbench that was
running for quite some time. Are Book-E (CONFIG_PPC_BOOK3E_MMU without
CONFIG_PPC_BOOK3E set) not affected or is this bug not present if a SMP
kernel is booted on a UP machine?

Sebastian

      parent reply	other threads:[~2013-12-15 13:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 15:54 [PATCH] powerpc: Fix PTE page address mismatch in pgtable ctor/dtor Hong H. Pham
2013-12-06 10:38 ` Aneesh Kumar K.V
2013-12-06 16:15   ` Hong H. Pham
2013-12-07 14:05     ` Hong H. Pham
2013-12-06 16:17   ` [PATCH v2] " Hong H. Pham
2013-12-07 14:06   ` [PATCH v3] " Hong H. Pham
2013-12-07 20:27     ` Benjamin Herrenschmidt
2013-12-07 20:32       ` Benjamin Herrenschmidt
2013-12-09  8:41       ` Aneesh Kumar K.V
2013-12-09  8:42     ` Aneesh Kumar K.V
2013-12-15 12:59     ` Sebastian Andrzej Siewior [this message]

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=20131215125933.GB31090@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=hong.pham@windriver.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=stable@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).