From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Book3S HV: POWER9 more doorbell fixes
Date: Tue, 10 Oct 2017 22:04:51 +1000 [thread overview]
Message-ID: <20171010220451.4ff90328@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20171010101828.5950-1-npiggin@gmail.com>
On Tue, 10 Oct 2017 20:18:28 +1000
Nicholas Piggin <npiggin@gmail.com> wrote:
> - Add another case where msgsync is required.
> - Required barrier sequence for global doorbells is msgsync ; lwsync
> - POWER9 DD1 has a different barrier sequence that we don't implement,
> so remove
This last item was not included in the patch, it slipped past.
I think the changelog can just be changed to remove it.
Fixing up DD1 should be a different patch if we want to bother
with it. Guess either we add the darn sequence for msgsync, or
add support for xive IPIs?
Thanks,
Nick
next prev parent reply other threads:[~2017-10-10 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 10:18 [PATCH] KVM: PPC: Book3S HV: POWER9 more doorbell fixes Nicholas Piggin
2017-10-10 12:04 ` Nicholas Piggin [this message]
2017-10-14 1:24 ` Paul Mackerras
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=20171010220451.4ff90328@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).