From: Tao Xu <tao3.xu@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "lvivier@redhat.com" <lvivier@redhat.com>,
"thuth@redhat.com" <thuth@redhat.com>,
"Du, Fan" <fan.du@intel.com>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"sw@weilnetz.de" <sw@weilnetz.de>,
"jonathan.cameron@huawei.com" <jonathan.cameron@huawei.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"mdroth@linux.vnet.ibm.com" <mdroth@linux.vnet.ibm.com>,
"Liu, Jingqi" <jingqi.liu@intel.com>,
"imammedo@redhat.com" <imammedo@redhat.com>
Subject: Re: [PATCH RESEND v20 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT)
Date: Thu, 19 Dec 2019 09:08:46 +0800 [thread overview]
Message-ID: <b667ded5-1461-1a16-0685-cd85966e0eab@intel.com> (raw)
In-Reply-To: <20191213050619-mutt-send-email-mst@kernel.org>
On 12/13/2019 6:06 PM, Michael S. Tsirkin wrote:
> On Fri, Dec 13, 2019 at 09:19:21AM +0800, Tao Xu wrote:
>> This series of patches will build Heterogeneous Memory Attribute Table (HMAT)
>> according to the command line. The ACPI HMAT describes the memory attributes,
>> such as memory side cache attributes and bandwidth and latency details,
>> related to the Memory Proximity Domain.
>> The software is expected to use HMAT information as hint for optimization.
>>
>> In the linux kernel, the codes in drivers/acpi/hmat/hmat.c parse and report
>> the platform's HMAT tables.
>>
>> The V19 patches link:
>> https://patchwork.kernel.org/cover/11265525/
>
> Looks good to me, I'll queue it for merge after the release. If possible
> please ping me after the release to help make sure it didn't get
> dropped.
>
Hi Michael,
I am wondering if these patches can be merged this week, because QEMU
5.0 developing tree is open and next week may be the holidays.
Thank you very much!
Tao Xu
prev parent reply other threads:[~2019-12-19 1:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 1:19 [PATCH RESEND v20 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT) Tao Xu
2019-12-13 1:19 ` [PATCH RESEND v20 1/8] numa: Extend CLI to provide initiator information for numa nodes Tao Xu
2019-12-13 1:19 ` [PATCH RESEND v20 2/8] numa: Extend CLI to provide memory latency and bandwidth information Tao Xu
2019-12-13 9:40 ` Igor Mammedov
2019-12-13 1:19 ` [PATCH RESEND v20 3/8] numa: Extend CLI to provide memory side cache information Tao Xu
2019-12-13 9:40 ` Igor Mammedov
2019-12-13 1:19 ` [PATCH RESEND v20 4/8] hmat acpi: Build Memory Proximity Domain Attributes Structure(s) Tao Xu
2019-12-13 1:19 ` [PATCH RESEND v20 5/8] hmat acpi: Build System Locality Latency and Bandwidth Information Structure(s) Tao Xu
2019-12-13 1:19 ` [PATCH RESEND v20 6/8] hmat acpi: Build Memory Side Cache " Tao Xu
2019-12-13 1:19 ` [PATCH RESEND v20 7/8] tests/numa: Add case for QMP build HMAT Tao Xu
2019-12-13 9:46 ` Igor Mammedov
2019-12-13 1:19 ` [PATCH RESEND v20 8/8] tests/bios-tables-test: add test cases for ACPI HMAT Tao Xu
2019-12-13 10:06 ` [PATCH RESEND v20 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT) Michael S. Tsirkin
2019-12-16 1:03 ` Tao Xu
2019-12-19 1:08 ` Tao Xu [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=b667ded5-1461-1a16-0685-cd85966e0eab@intel.com \
--to=tao3.xu@intel.com \
--cc=armbru@redhat.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=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 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).