All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <brice.goglin@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-mm@kvack.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, x86@kernel.org
Cc: Keith Busch <keith.busch@intel.com>,
	jglisse@redhat.com, "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	linuxarm@huawei.com, Andrew Morton <akpm@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Tao Xu <tao3.xu@intel.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH V6 0/7] ACPI: Support Generic Initiator proximity domains
Date: Wed, 18 Dec 2019 12:32:06 +0100	[thread overview]
Message-ID: <dc5f5502-09c6-d476-db0e-0af3412bb031@gmail.com> (raw)
In-Reply-To: <20191216153809.105463-1-Jonathan.Cameron@huawei.com>

Le 16/12/2019 à 16:38, Jonathan Cameron a écrit :
> 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.


Hello Jonathan

If I want to test this with a fake GI, what are the minimal set of
changes I should put in my ACPI tables? Can I just specify a dummy GI in
SRAT? What handle should I use there?

Thanks

Brice



WARNING: multiple messages have this Message-ID (diff)
From: Brice Goglin <brice.goglin@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-mm@kvack.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, x86@kernel.org
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Tao Xu <tao3.xu@intel.com>, Sudeep Holla <sudeep.holla@arm.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	linuxarm@huawei.com, Keith Busch <keith.busch@intel.com>,
	jglisse@redhat.com, Hanjun Guo <guohanjun@huawei.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH V6 0/7] ACPI: Support Generic Initiator proximity domains
Date: Wed, 18 Dec 2019 12:32:06 +0100	[thread overview]
Message-ID: <dc5f5502-09c6-d476-db0e-0af3412bb031@gmail.com> (raw)
In-Reply-To: <20191216153809.105463-1-Jonathan.Cameron@huawei.com>

Le 16/12/2019 à 16:38, Jonathan Cameron a écrit :
> 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.


Hello Jonathan

If I want to test this with a fake GI, what are the minimal set of
changes I should put in my ACPI tables? Can I just specify a dummy GI in
SRAT? What handle should I use there?

Thanks

Brice



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-12-18 11:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 15:38 [PATCH V6 0/7] ACPI: Support Generic Initiator proximity domains Jonathan Cameron
2019-12-16 15:38 ` Jonathan Cameron
2019-12-16 15:38 ` [PATCH V6 1/7] ACPI: Support Generic Initiator only domains Jonathan Cameron
2019-12-16 15:38   ` Jonathan Cameron
2019-12-16 15:38 ` [PATCH V6 2/7] arm64: " Jonathan Cameron
2019-12-16 15:38   ` Jonathan Cameron
2019-12-16 15:38 ` [PATCH V6 3/7] x86: Support Generic Initiator only proximity domains Jonathan Cameron
2019-12-16 15:38   ` Jonathan Cameron
2019-12-16 15:38 ` [PATCH V6 4/7] ACPI: Let ACPI know we support Generic Initiator Affinity Structures Jonathan Cameron
2019-12-16 15:38   ` Jonathan Cameron
2019-12-16 15:38 ` [PATCH V6 5/7] ACPI: HMAT: Fix handling of changes from ACPI 6.2 to ACPI 6.3 Jonathan Cameron
2019-12-16 15:38   ` Jonathan Cameron
2019-12-16 15:38 ` [PATCH V6 6/7] node: Add access1 class to represent CPU to memory characteristics Jonathan Cameron
2019-12-16 15:38   ` Jonathan Cameron
2019-12-16 15:38 ` [PATCH V6 7/7] docs: mm: numaperf.rst Add brief description for access class 1 Jonathan Cameron
2019-12-16 15:38   ` Jonathan Cameron
2019-12-18 11:34   ` Brice Goglin
2019-12-18 11:34     ` Brice Goglin
2019-12-18 14:37     ` Jonathan Cameron
2019-12-18 14:37       ` Jonathan Cameron
2019-12-18 11:32 ` Brice Goglin [this message]
2019-12-18 11:32   ` [PATCH V6 0/7] ACPI: Support Generic Initiator proximity domains Brice Goglin
2019-12-18 14:50   ` Jonathan Cameron
2019-12-18 14:50     ` Jonathan Cameron
2019-12-20 21:40     ` Brice Goglin
2019-12-20 21:40       ` Brice Goglin
2020-01-02 15:27       ` Jonathan Cameron
2020-01-02 15:27         ` Jonathan Cameron
2020-01-02 21:37         ` Brice Goglin
2020-01-02 21:37           ` Brice Goglin
2020-01-03 10:09           ` Jonathan Cameron
2020-01-03 10:09             ` Jonathan Cameron
2020-01-03 12:18             ` Brice Goglin
2020-01-03 12:18               ` Brice Goglin
2020-01-03 13:08               ` Jonathan Cameron
2020-01-03 13:08                 ` Jonathan Cameron

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=dc5f5502-09c6-d476-db0e-0af3412bb031@gmail.com \
    --to=brice.goglin@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=guohanjun@huawei.com \
    --cc=jglisse@redhat.com \
    --cc=keith.busch@intel.com \
    --cc=linux-acpi@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=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.com \
    --cc=tao3.xu@intel.com \
    --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 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.