All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: Alistair Popple <alistair@popple.id.au>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
	benh@kernel.crashing.org, stewart@linux.vnet.ibm.com,
	mpe@ellerman.id.au
Subject: Re: [PATCH] powerpc/powernv: Initialise nest mmu
Date: Tue, 16 Aug 2016 14:22:33 +1000	[thread overview]
Message-ID: <a405f24b-2a80-4828-cf65-a40824130f5e@gmail.com> (raw)
In-Reply-To: <1989530.M5axb7bib9@new-mexico>



On 16/08/16 10:37, Alistair Popple wrote:
> Balbir,
> 
> <snip>
>  
>>> +	/* Update partition table control register on all Nest MMUs */
>>> +	opal_nmmu_set_ptcr(-1UL, __pa(partition_tb) | (PATB_SIZE_SHIFT - 12));
>>> +
>>
>> Just wondering if
>>
>> 1. Instead of using -1 for all cpus, we should do
>> 	for_each_online_cpu() {
>> 		opal_numm_set_ptcr(...)
>> 	}
> 
> Good question, but I don't think it makes sense to do that. The NMMU is
> per-chip/socket rather than per-cpu so it shouldn't be tied to
> onlining/offlining of individual CPUs.
> 
>> 2. In cpu hotplug path do the same when onlining and set to NULL on
>> offlining?
> 
> Again, the nmmu isn't tied to a specific CPU but rather a chip/socket. So in
> theory at least it's possible that all CPUs in a chip could be offline but
> other units on the chip could still be using the nmmu so we wouldn't want to
> disable the nmmu at that point.

Fair enough

Balbir Singh.

  reply	other threads:[~2016-08-16  4:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15  6:51 [PATCH] powerpc/powernv: Initialise nest mmu Alistair Popple
2016-08-15  7:22 ` Balbir Singh
2016-08-16  0:37   ` Alistair Popple
2016-08-16  4:22     ` Balbir Singh [this message]
2016-09-14  5:02 ` Alistair Popple
2016-11-08 23:36   ` Balbir Singh

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=a405f24b-2a80-4828-cf65-a40824130f5e@gmail.com \
    --to=bsingharora@gmail.com \
    --cc=alistair@popple.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=stewart@linux.vnet.ibm.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 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.