LinuxPPC-Dev Archive on lore.kernel.org
 help / color / Atom feed
From: Thomas Falcon <tlfalcon@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/9] Fixes and Enablement of ibm,drc-info property
Date: Tue, 5 Nov 2019 11:03:42 -0600
Message-ID: <6958da5b-c518-64c2-50e3-db3f169d2337@linux.ibm.com> (raw)
In-Reply-To: <1572967453-9586-1-git-send-email-tyreld@linux.ibm.com>


On 11/5/19 9:24 AM, Tyrel Datwyler wrote:

Hi, just pointing out a few typos...
> There was a previous effort to add support for the PAPR
> architected ibm,drc-info property. This property provides a more
> memory compact representation of a paritions Dynamic Reconfig
s/paritions/partition's
> Connectors (DRC). These can otherwise be thought of as currently
> partitioned, or available but yet to be partitioned system resources
> such as cpus, memory, and physical/logical IOA devices.
>
> The initial implementation proved buggy and was fully turned of by

s/turned of/turned off

> disabling the bit in the appropriate CAS support vector. We now have
> PowerVM firmware in the field that supports this new property, and
> further to suppport partitions with 24TB+ of possible memory this
s/suppport/support
> property is required to perform platform migration.
>
> This serious fixs the short comings of the previous submission

Either "seriously fixes the shortcomings", or "fixes the serious 
shortcomings?"

Thanks,

Tom

> in the areas of general implementation, cpu hotplug, and IOA hotplug.
>
> Tyrel Datwyler (9):
>    powerpc/pseries: Fix bad drc_index_start value parsing of drc-info
>      entry
>    powerpc/pseries: Fix drc-info mappings of logical cpus to drc-index
>    powerpc/pseries: Add cpu DLPAR support for drc-info property
>    PCI: rpaphp: Fix up pointer to first drc-info entry
>    PCI: rpaphp: Don't rely on firmware feature to imply drc-info support
>    PCI: rpaphp: Add drc-info support for hotplug slot registration
>    PCI: rpaphp: annotate and correctly byte swap DRC properties
>    PCI: rpaphp: Correctly match ibm,my-drc-index to drc-name when using
>      drc-info
>    powerpc/pseries: Enable support for ibm,drc-info property
>
>   arch/powerpc/kernel/prom_init.c                 |   2 +-
>   arch/powerpc/platforms/pseries/hotplug-cpu.c    | 101 ++++++++++++++++---
>   arch/powerpc/platforms/pseries/of_helpers.c     |   8 +-
>   arch/powerpc/platforms/pseries/pseries_energy.c |  23 ++---
>   drivers/pci/hotplug/rpaphp_core.c               | 124 +++++++++++++++++-------
>   5 files changed, 187 insertions(+), 71 deletions(-)
>

  parent reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 15:24 Tyrel Datwyler
2019-11-05 15:24 ` [PATCH 1/9] powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry Tyrel Datwyler
2019-11-05 15:24 ` [PATCH 2/9] powerpc/pseries: Fix drc-info mappings of logical cpus to drc-index Tyrel Datwyler
2019-11-05 15:24 ` [PATCH 3/9] powerpc/pseries: Add cpu DLPAR support for drc-info property Tyrel Datwyler
2019-11-05 16:55   ` Thomas Falcon
2019-11-06 20:15     ` Tyrel Datwyler
2019-11-07 11:35   ` Michael Ellerman
2019-11-05 15:24 ` [PATCH 4/9] PCI: rpaphp: Fix up pointer to first drc-info entry Tyrel Datwyler
2019-11-05 15:24 ` [PATCH 5/9] PCI: rpaphp: Don't rely on firmware feature to imply drc-info support Tyrel Datwyler
2019-11-05 15:24 ` [PATCH 6/9] PCI: rpaphp: Add drc-info support for hotplug slot registration Tyrel Datwyler
2019-11-05 15:24 ` [PATCH 7/9] PCI: rpaphp: annotate and correctly byte swap DRC properties Tyrel Datwyler
2019-11-07 11:40   ` Michael Ellerman
2019-11-05 15:24 ` [PATCH 8/9] PCI: rpaphp: Correctly match ibm, my-drc-index to drc-name when using drc-info Tyrel Datwyler
2019-11-05 15:24 ` [PATCH 9/9] powerpc/pseries: Enable support for ibm, drc-info property Tyrel Datwyler
2019-11-07 11:38   ` Michael Ellerman
2019-11-05 17:03 ` Thomas Falcon [this message]
2019-11-06 20:12   ` [PATCH 0/9] Fixes and Enablement of ibm,drc-info property Tyrel Datwyler
2019-11-07 11:26     ` Michael Ellerman

Reply instructions:

You may reply publically 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=6958da5b-c518-64c2-50e3-db3f169d2337@linux.ibm.com \
    --to=tlfalcon@linux.ibm.com \
    --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

LinuxPPC-Dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linuxppc-dev/0 linuxppc-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linuxppc-dev linuxppc-dev/ https://lore.kernel.org/linuxppc-dev \
		linuxppc-dev@lists.ozlabs.org linuxppc-dev@ozlabs.org
	public-inbox-index linuxppc-dev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.ozlabs.lists.linuxppc-dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git