From: Brice Goglin <brice.goglin@gmail.com>
To: Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: "Tao Xu" <tao3.xu@intel.com>, "Linux MM" <linux-mm@kvack.org>,
"Linux ACPI" <linux-acpi@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"X86 ML" <x86@kernel.org>, "Keith Busch" <keith.busch@intel.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Linuxarm <linuxarm@huawei.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH V5 1/4] ACPI: Support Generic Initiator only domains
Date: Mon, 18 Nov 2019 18:18:23 +0100 [thread overview]
Message-ID: <d0106281-f65c-369f-ef0f-11afc5f60048@gmail.com> (raw)
In-Reply-To: <CAPcyv4jrXvPOvoBCW8H42_og1wJ_t9_=5N4C7-OugYyNzdqBLA@mail.gmail.com>
Le 16/11/2019 à 21:45, Dan Williams a écrit :
>
>> My feeling is that any existing users of access0 are definitely not going
>> to be expecting generic initiators, so we might want to do this the other
>> way around. access0 is only CPUs and memory, access1 is including
>> generic initiators. If there are no GIs don't expose access1 at all?
> There are no consumers of the information that I know of, so I do not
> see the risk of regression.
hwloc already reads access0/initiators/ node symlinks (mostly useful for
finding which CPUs are local to kmem dax devices). If I understand
correctly the changes you propose, we would get an empty list of CPUs in
the access0/initiators/ nodes? If it only occurs on platforms with GI
(when are those coming to market?), I'd say it's not a big deal for us,
we'll manage to have users upgrade their hwloc.
Brice
next prev parent reply other threads:[~2019-11-18 17:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 11:43 [PATCH V5 0/4] ACPI: Support Generic Initiator proximity domains Jonathan Cameron
2019-10-04 11:43 ` [PATCH V5 1/4] ACPI: Support Generic Initiator only domains Jonathan Cameron
2019-10-18 10:18 ` Rafael J. Wysocki
2019-10-18 12:46 ` Jonathan Cameron
2019-11-07 14:54 ` Rafael J. Wysocki
2019-11-12 17:07 ` Jonathan Cameron
2019-11-12 17:55 ` Dan Williams
2019-11-13 9:47 ` Jonathan Cameron
2019-11-13 13:57 ` Tao Xu
2019-11-13 16:52 ` Dan Williams
2019-11-13 17:56 ` Jonathan Cameron
2019-11-13 17:48 ` Jonathan Cameron
2019-11-13 23:20 ` Dan Williams
2019-11-14 11:26 ` Jonathan Cameron
2019-11-16 20:45 ` Dan Williams
2019-11-18 17:18 ` Brice Goglin [this message]
2019-10-04 11:43 ` [PATCH V5 2/4] arm64: " Jonathan Cameron
2019-10-04 11:43 ` [PATCH V5 3/4] x86: Support Generic Initiator only proximity domains Jonathan Cameron
2019-10-07 14:55 ` Ingo Molnar
2019-10-08 11:17 ` Jonathan Cameron
2019-10-04 11:43 ` [PATCH V5 4/4] ACPI: Let ACPI know we support Generic Initiator Affinity Structures 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=d0106281-f65c-369f-ef0f-11afc5f60048@gmail.com \
--to=brice.goglin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jglisse@redhat.com \
--cc=jonathan.cameron@huawei.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=rjw@rjwysocki.net \
--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 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).