From: Michael Ellerman <mpe@ellerman.id.au>
To: Paul Mackerras <paulus@au1.ibm.com>, linuxppc-dev@ozlabs.org
Subject: Re: [1/2] Revert "Use the POWER8 Micro Partition Prefetch Engine in KVM HV on POWER8"
Date: Wed, 21 Oct 2015 22:42:32 +1100 (AEDT) [thread overview]
Message-ID: <20151021114232.E770A14076E@ozlabs.org> (raw)
In-Reply-To: <20151021050314.GA17764@fergus.ozlabs.ibm.com>
On Wed, 2015-21-10 at 05:03:14 UTC, Paul Mackerras wrote:
> This reverts commit 9678cdaae93932473f696fdea5debf3eee1e1260 because
> the original commit had multiple, partly self-cancelling bugs, that
> could cause occasional memory corruption. In fact the logmpp instruction
> was using register r0 as the source of the buffer address and operation
> code, and depending on what was in r0, it would either do nothing or
> corrupt the 64k page pointed to by r0. The logmpp instruction encoding
> and the operation code definitions could be corrected, but then there is
> the problem that there is no clearly defined way to know when the
> hardware has finished writing to the buffer. The original commit
> attempted to work around this by aborting the write-out before starting
> the prefetch, but this is ineffective in the case where the virtual
> core is now executing on a different physical core from the one where
> the write-out was initiated.
>
> These problems plus advice from the hardware designers not to use the
> function (since the measured performance improvement from using the
> feature was actually mostly negative), mean that reverting the code is
> the best option.
>
> Signed-off-by: Paul Mackerras <paulus@samba.org>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/23316316c1af0677a041c81f
cheers
prev parent reply other threads:[~2015-10-21 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 5:03 [PATCH 1/2] Revert "Use the POWER8 Micro Partition Prefetch Engine in KVM HV on POWER8" Paul Mackerras
2015-10-21 11:42 ` Michael Ellerman [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=20151021114232.E770A14076E@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@au1.ibm.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 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).