All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	npiggin@gmail.com, paulus@samba.org
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/4] powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions
Date: Wed, 25 Sep 2019 21:05:27 +1000 (AEST)	[thread overview]
Message-ID: <46dZwS46Ztz9sPK@ozlabs.org> (raw)
In-Reply-To: <20190924035254.24612-1-aneesh.kumar@linux.ibm.com>

On Tue, 2019-09-24 at 03:52:51 UTC, "Aneesh Kumar K.V" wrote:
> The store ordering vs tlbie issue mentioned in
> commit a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on
> POWER9") is fixed for Nimbus 2.3 and Cumulus 1.3 revisions. We don't need
> to apply the fixup if we are running on them
> 
> We can only do this on PowerNV. On pseries guest with kvm we still don't
> support redoing the feature fixup after migration. So we should be enabling
> all the workarounds needed, because whe can possibly migrate between
> DD 2.3 and DD 2.2
> 
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>

Series applied to powerpc fixes, thanks.

https://git.kernel.org/powerpc/c/677733e296b5c7a37c47da391fc70a43dc40bd67

cheers

      parent reply	other threads:[~2019-09-25 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  3:52 [PATCH 1/4] powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions Aneesh Kumar K.V
2019-09-24  3:52 ` [PATCH 2/4] powerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag Aneesh Kumar K.V
2019-09-24  3:52 ` [PATCH 3/4] powerpc/mm: Fixup tlbie vs mtpidr/mtlpidr ordering issue on POWER9 Aneesh Kumar K.V
2019-09-24  3:52 ` [PATCH 4/4] powerpc/mm/selftest: Add test case for tlbie vs mtpidr ordering issue Aneesh Kumar K.V
2019-09-25 11:05 ` 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=46dZwS46Ztz9sPK@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.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 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.