All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Tao Xu <tao3.xu@intel.com>
Cc: lvivier@redhat.com, thuth@redhat.com, ehabkost@redhat.com,
	mst@redhat.com, jonathan.cameron@huawei.com, sw@weilnetz.de,
	fan.du@intel.com, mdroth@linux.vnet.ibm.com,
	qemu-devel@nongnu.org, jingqi.liu@intel.com, imammedo@redhat.com,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH v18 1/8] numa: Extend CLI to provide initiator information for numa nodes
Date: Wed, 27 Nov 2019 10:40:22 +0100	[thread overview]
Message-ID: <87muchfyih.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20191127082613.22903-2-tao3.xu@intel.com> (Tao Xu's message of "Wed, 27 Nov 2019 16:26:06 +0800")

Tao Xu <tao3.xu@intel.com> writes:

> In ACPI 6.3 chapter 5.2.27 Heterogeneous Memory Attribute Table (HMAT),
> The initiator represents processor which access to memory. And in 5.2.27.3
> Memory Proximity Domain Attributes Structure, the attached initiator is
> defined as where the memory controller responsible for a memory proximity
> domain. With attached initiator information, the topology of heterogeneous
> memory can be described.
>
> Extend CLI of "-numa node" option to indicate the initiator numa node-id.
> In the linux kernel, the codes in drivers/acpi/hmat/hmat.c parse and report
> the platform's HMAT tables.

Please mention new machine property "hmat".

> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> Reviewed-by: Jingqi Liu <jingqi.liu@intel.com>
> Suggested-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Tao Xu <tao3.xu@intel.com>

QAPI part looks good to me.



  reply	other threads:[~2019-11-27  9:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27  8:26 [PATCH v18 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT) Tao Xu
2019-11-27  8:26 ` [PATCH v18 1/8] numa: Extend CLI to provide initiator information for numa nodes Tao Xu
2019-11-27  9:40   ` Markus Armbruster [this message]
2019-11-27  8:26 ` [PATCH v18 2/8] numa: Extend CLI to provide memory latency and bandwidth information Tao Xu
2019-11-27  9:48   ` Markus Armbruster
2019-11-27  8:26 ` [PATCH v18 3/8] numa: Extend CLI to provide memory side cache information Tao Xu
2019-11-27  9:56   ` Markus Armbruster
2019-11-28  2:46     ` Tao Xu
2019-11-28  4:49       ` Tao Xu
2019-11-27  8:26 ` [PATCH v18 4/8] hmat acpi: Build Memory Proximity Domain Attributes Structure(s) Tao Xu
2019-11-27  8:26 ` [PATCH v18 5/8] hmat acpi: Build System Locality Latency and Bandwidth Information Structure(s) Tao Xu
2019-11-27  8:26 ` [PATCH v18 6/8] hmat acpi: Build Memory Side Cache " Tao Xu
2019-11-27  8:26 ` [PATCH v18 7/8] tests/numa: Add case for QMP build HMAT Tao Xu
2019-11-27  8:26 ` [PATCH v18 8/8] tests/bios-tables-test: add test cases for ACPI HMAT Tao Xu
2019-11-27  8:51 ` [PATCH v18 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT) no-reply

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=87muchfyih.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=fan.du@intel.com \
    --cc=imammedo@redhat.com \
    --cc=jingqi.liu@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=lvivier@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    --cc=tao3.xu@intel.com \
    --cc=thuth@redhat.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.