linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: alistair@popple.id.au
Subject: Re: [PATCH v2] powerpc/powernv: Initialise nest mmu
Date: Mon, 5 Dec 2016 17:32:13 +1100	[thread overview]
Message-ID: <dd699260-28a9-ccf3-3159-c127e819724f@gmail.com> (raw)
In-Reply-To: <1480903162-1986-1-git-send-email-mpe@ellerman.id.au>



On 05/12/16 12:59, Michael Ellerman wrote:
> From: Alistair Popple <alistair@popple.id.au>
> 
> POWER9 contains an off core mmu called the nest mmu (NMMU). This is used
> by other hardware units on the chip to translate virtual addresses into
> real addresses. The unit attempting an address translation provides the
> majority of the context required for the translation request except for
> the base address of the partition table (ie. the PTCR) which needs to be
> programmed into the NMMU.
> 
> This patch adds a call to OPAL to set the PTCR for the nest mmu in
> opal_init().
> 
> Signed-off-by: Alistair Popple <alistair@popple.id.au>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---

Reviewed-by: Balbir Singh <bsingharora@gmail.com>

  reply	other threads:[~2016-12-05  6:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05  1:59 [PATCH v2] powerpc/powernv: Initialise nest mmu Michael Ellerman
2016-12-05  6:32 ` Balbir Singh [this message]
2016-12-05  7:23 ` Aneesh Kumar K.V
  -- strict thread matches above, loose matches on Subject: below --
2016-12-02  5:29 Alistair Popple
2016-12-02  9:24 ` Michael Ellerman
2016-12-03  0:08   ` Alistair Popple
2016-12-03  1:33   ` Tyrel Datwyler
2016-12-02 11:04 ` Balbir Singh
2016-12-03 10:56   ` Michael Ellerman
2016-12-03 11:40     ` Michael Ellerman
2016-12-05  0:02       ` Alistair Popple

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=dd699260-28a9-ccf3-3159-c127e819724f@gmail.com \
    --to=bsingharora@gmail.com \
    --cc=alistair@popple.id.au \
    --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).