linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linuxarm <linuxarm@huawei.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Brice Goglin <Brice.Goglin@inria.fr>,
	Sean V Kelley <sean.v.kelley@linux.intel.com>,
	Linux API <linux-api@vger.kernel.org>,
	Borislav Petkov <bp@alien8.de>, Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH v12 0/6] ACPI: Support Generic Initiator proximity domains
Date: Fri, 2 Oct 2020 18:55:06 +0200	[thread overview]
Message-ID: <CAJZ5v0hUPk6Geh3MG+948Q_LmHNEYBoJgBKLFb7jH7RCbPv5PQ@mail.gmail.com> (raw)
In-Reply-To: <20200930140547.840251-1-Jonathan.Cameron@huawei.com>

On Wed, Sep 30, 2020 at 4:07 PM Jonathan Cameron
<Jonathan.Cameron@huawei.com> wrote:
>
> It would be very nice to finally merge this support during the next cycle,
> so please take a look.
>
> I think we need acks covering x86, ARM and ACPI.  Rafael took a look back
> in November at v5 and was looking for x86 and ARM acks.  Whilst there is
> no ARM specific code left we probably still need an Ack.  If anyone is
> missing from the cc list, please add them.
>
> Introduces a new type of NUMA node for cases where we want to represent
> the access characteristics of a non CPU initiator of memory requests,
> as these differ from all those for existing nodes containing CPUs and/or
> memory.
>
> These Generic Initiators are presented by the node access0 class in
> sysfs in the same way as a CPU. It seems likely that there will be
> usecases in which the best 'CPU' is desired and Generic Initiators
> should be ignored.  The final few patches in this series introduced
> access1 which is a new performance class in the sysfs node description
> which presents only CPU to memory relationships.  Test cases for this
> are described below.

The whole series has been applied as 5.10 material.

If anyone has concerns or objections, please let me know ASAP.

Thanks!

      parent reply	other threads:[~2020-10-02 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 14:05 [PATCH v12 0/6] ACPI: Support Generic Initiator proximity domains Jonathan Cameron
2020-09-30 14:05 ` [PATCH v12 1/6] ACPI: Support Generic Initiator only domains Jonathan Cameron
2020-09-30 14:05 ` [PATCH v12 2/6] x86: Support Generic Initiator only proximity domains Jonathan Cameron
2020-09-30 15:51   ` Borislav Petkov
2020-09-30 14:05 ` [PATCH v12 3/6] ACPI: Let ACPI know we support Generic Initiator Affinity Structures Jonathan Cameron
2020-09-30 14:05 ` [PATCH v12 4/6] ACPI: HMAT: Fix handling of changes from ACPI 6.2 to ACPI 6.3 Jonathan Cameron
2020-09-30 14:05 ` [PATCH v12 5/6] node: Add access1 class to represent CPU to memory characteristics Jonathan Cameron
2020-09-30 14:05 ` [PATCH v12 6/6] docs: mm: numaperf.rst Add brief description for access class 1 Jonathan Cameron
2020-10-02 16:55 ` Rafael J. Wysocki [this message]

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=CAJZ5v0hUPk6Geh3MG+948Q_LmHNEYBoJgBKLFb7jH7RCbPv5PQ@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=Brice.Goglin@inria.fr \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxarm@huawei.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mingo@redhat.com \
    --cc=sean.v.kelley@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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
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).