From: Michael Ellerman <michael@ellerman.id.au>
To: Paolo Bonzini <pbonzini@redhat.com>, Paul Mackerras <paulus@ozlabs.org>
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org
Subject: Re: [PATCH v2 3/3] powerpc/mm: Speed up computation of base and actual page size for a HPTE
Date: Mon, 12 Sep 2016 13:03:43 +1000 [thread overview]
Message-ID: <877fahrf8w.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <4ba4f3d7-eadc-5d20-534e-afc7075938fc@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 08/09/2016 12:08, Paul Mackerras wrote:
>>> >
>>> > arch/powerpc/include/asm/book3s/64/mmu-hash.h | 37 ++++++++++++
>>> > arch/powerpc/include/asm/kvm_book3s_64.h | 87 +++------------------------
>>> > arch/powerpc/include/asm/mmu.h | 1 +
>>> > arch/powerpc/mm/hash_native_64.c | 42 +------------
>>> > arch/powerpc/mm/hash_utils_64.c | 55 +++++++++++++++++
>> This of course touches two maintainers' areas. Michael and Paolo, how
>> do you want to proceed here? Can this just go through Michael's tree?
>> Or should I make a topic branch off Linus' tree that you can both
>> pull, or should I split the patch into two (i.e. everything except the
>> kvm_book3s_64.h change in the first patch, and the kvm_book3s_64.h
>> change in the second) and get Michael to put the first one in a topic
>> branch that I can then pull and apply the second patch onto?
>
> This patch seems separate from the other two (I can't really tell since
> there wasn't a cover letter on linuxppc-dev).
Yeah. I've merged 1/3 as a fix, and will take 2/3 into next.
> Can you place it in a pull request for both Michael and myself?
Paul and I talked about this offline, he's going to create a topic
branch with this in it.
I'll hold off merging it until closer to the merge window, and I'll
merge it then if we are actually seeing conflicts between the PPC & KVM
trees caused by this.
cheers
next prev parent reply other threads:[~2016-09-12 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160902114759.GA12433@fergus.ozlabs.ibm.com>
2016-09-02 11:50 ` [PATCH 3/3] powerpc/mm: Speed up computation of base and actual page size for a HPTE Paul Mackerras
2016-09-04 11:16 ` Aneesh Kumar K.V
2016-09-05 5:04 ` Aneesh Kumar K.V
2016-09-07 5:07 ` Paul Mackerras
[not found] ` <20160907061709.GD21443@fergus.ozlabs.ibm.com>
2016-09-08 10:08 ` [PATCH v2 " Paul Mackerras
2016-09-08 10:16 ` Paolo Bonzini
2016-09-12 0:58 ` Paul Mackerras
2016-09-12 3:03 ` Michael Ellerman [this message]
2016-09-12 9:45 ` Paolo Bonzini
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=877fahrf8w.fsf@concordia.ellerman.id.au \
--to=michael@ellerman.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.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