qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, ehabkost@redhat.com, imammedo@redhat.com,
	pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4 0/2] hw/acpi-build: Fix ACPI SRAT Memory Affinity building
Date: Wed, 23 Aug 2017 05:48:17 +0300	[thread overview]
Message-ID: <20170823053601-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1503372250-5092-1-git-send-email-douly.fnst@cn.fujitsu.com>

On Tue, Aug 22, 2017 at 11:24:08AM +0800, Dou Liyang wrote:
> V3 --> v4:
>   -add a new testcase.
> 
> This patchset fixs an ACPI building bug which caused by no RAM
> in the first NUAM node. and also add a new testcase for the bug.

thanks!
Pls remember to ping or repost after release is out.

> Dou Liyang (2):
>   hw/acpi-build: Fix SRAT memory building when there is no memory in
>     node0
>   ACPI/unit-test: Add a new testcase for RAM allocation in numa node
> 
>  hw/i386/acpi-build.c                  |  78 ++++++++++++++++++++++------------
>  tests/acpi-test-data/pc/DSDT.numamem  | Bin 0 -> 6463 bytes
>  tests/acpi-test-data/pc/SLIT.numamem  | Bin 0 -> 48 bytes
>  tests/acpi-test-data/pc/SRAT.numamem  | Bin 0 -> 264 bytes
>  tests/acpi-test-data/q35/DSDT.numamem | Bin 0 -> 9147 bytes
>  tests/acpi-test-data/q35/SLIT.numamem | Bin 0 -> 48 bytes
>  tests/acpi-test-data/q35/SRAT.numamem | Bin 0 -> 264 bytes
>  tests/bios-tables-test.c              |  30 +++++++++++++
>  8 files changed, 80 insertions(+), 28 deletions(-)
>  create mode 100644 tests/acpi-test-data/pc/DSDT.numamem
>  create mode 100644 tests/acpi-test-data/pc/SLIT.numamem
>  create mode 100644 tests/acpi-test-data/pc/SRAT.numamem
>  create mode 100644 tests/acpi-test-data/q35/DSDT.numamem
>  create mode 100644 tests/acpi-test-data/q35/SLIT.numamem
>  create mode 100644 tests/acpi-test-data/q35/SRAT.numamem
> 
> -- 
> 2.5.5
> 
> 

  parent reply	other threads:[~2017-08-23  2:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  3:24 [Qemu-devel] [PATCH v4 0/2] hw/acpi-build: Fix ACPI SRAT Memory Affinity building Dou Liyang
2017-08-22  3:24 ` [Qemu-devel] [PATCH v4 1/2] hw/acpi-build: Fix SRAT memory building when there is no memory in node0 Dou Liyang
2017-08-30 20:55   ` Eduardo Habkost
2017-08-31 10:38     ` Dou Liyang
2017-08-31 12:09       ` Dou Liyang
2017-08-22  3:24 ` [Qemu-devel] [PATCH v4 2/2] ACPI/unit-test: Add a new testcase for RAM allocation in numa node Dou Liyang
2017-08-23  8:40   ` Igor Mammedov
2017-08-23 12:12     ` Dou Liyang
2017-08-23 12:45       ` Igor Mammedov
2017-08-23 13:35         ` Dou Liyang
2017-08-23 17:25           ` Eduardo Habkost
2017-08-24  1:30             ` Dou Liyang
2017-08-23 17:47           ` Igor Mammedov
2017-08-24  1:42             ` Dou Liyang
2017-08-24 12:33               ` Igor Mammedov
2017-08-24 13:20                 ` Dou Liyang
2017-08-24 13:50   ` [Qemu-devel] [PATCH v5 " Dou Liyang
2017-08-23  2:48 ` Michael S. Tsirkin [this message]
2017-08-23  3:47   ` [Qemu-devel] [PATCH v4 0/2] hw/acpi-build: Fix ACPI SRAT Memory Affinity building Dou Liyang

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=20170823053601-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).