From: Balbir Singh <bsingharora@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Anton Blanchard <anton@samba.org>,
Aneesh Kumar KV <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/3] powerpc/mm/book3s64: Make KERN_IO_START a variable
Date: Thu, 3 Aug 2017 08:20:19 +1000 [thread overview]
Message-ID: <CAKTCnzmyPz0yEA5R2DA4qSs5t-QdJfAcn9R1codUV9fKmWiBMQ@mail.gmail.com> (raw)
In-Reply-To: <1501583364-14909-1-git-send-email-mpe@ellerman.id.au>
On Tue, Aug 1, 2017 at 8:29 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> Currently KERN_IO_START is defined as:
>
> #define KERN_IO_START (KERN_VIRT_START + (KERN_VIRT_SIZE >> 1))
>
> Although it looks like a constant, both the components are actually
> variables, to allow us to have a different value between Radix and
> Hash with a single kernel.
>
> However that still requires both Radix and Hash to place the kernel IO
> region at the same location relative to the start and end of the
> kernel virtual region (namely 1/2 way through it), and we'd like to
> change that.
>
> So split KERN_IO_START out into its own variable, and initialise it
> for Radix and Hash. In the medium term we should be able to
> reconsolidate this, by doing a more involved rearrangement of the
> location of the regions.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
Makes sense
Acked-by: Balbir Singh <bsingharora@gmail.com>
next prev parent reply other threads:[~2017-08-02 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 10:29 [PATCH 1/3] powerpc/mm/book3s64: Make KERN_IO_START a variable Michael Ellerman
2017-08-01 10:29 ` [PATCH 2/3] powerpc/mm/slb: Move comment next to the code it's referring to Michael Ellerman
2017-08-02 8:21 ` Aneesh Kumar K.V
2017-08-01 10:29 ` [PATCH 3/3] powerpc/mm/hash64: Make vmalloc 56T on hash Michael Ellerman
2017-08-02 8:19 ` Aneesh Kumar K.V
2017-08-03 0:00 ` Michael Ellerman
2017-08-02 8:20 ` [PATCH 1/3] powerpc/mm/book3s64: Make KERN_IO_START a variable Aneesh Kumar K.V
2017-08-02 22:20 ` Balbir Singh [this message]
2017-08-08 10:55 ` [1/3] " Michael Ellerman
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=CAKTCnzmyPz0yEA5R2DA4qSs5t-QdJfAcn9R1codUV9fKmWiBMQ@mail.gmail.com \
--to=bsingharora@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).