From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
qemu-devel@nongnu.org, "Eduardo Habkost" <eduardo@habkost.net>,
"Liu Jingqi" <jingqi.liu@intel.com>, "Tao Xu" <tao3.xu@intel.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Yanan Wang" <wangyanan55@huawei.com>
Subject: Re: [PATCH] hmat acpi: Don't require initiator value in -numa when hmat=on
Date: Thu, 23 Jun 2022 12:24:57 +0100 [thread overview]
Message-ID: <20220623122457.0000646b@Huawei.com> (raw)
In-Reply-To: <7eb4ef82-1e03-1135-2160-9673d2576849@inria.fr>
On Tue, 21 Jun 2022 12:49:09 +0200
Brice Goglin <Brice.Goglin@inria.fr> wrote:
> Le 20/06/2022 à 18:05, Igor Mammedov a écrit :
> > On Mon, 20 Jun 2022 17:24:18 +0200
> > Brice Goglin <Brice.Goglin@inria.fr> wrote:
> >
> >> Le 20/06/2022 à 15:27, Igor Mammedov a écrit Machine (2966MB total) +
> >> Package P#0
> >>>> NUMANode P#2 (979MB)
> >>>> Group0
> >>>> NUMANode P#0 (980MB)
> >>>> Core P#0 + PU P#0
> >>>> Core P#1 + PU P#1
> >>>> Group0
> >>>> NUMANode P#1 (1007MB)
> >>>> Core P#2 + PU P#2
> >>>> Core P#3 + PU P#3
> >>> here should be a dis-assembled dump of generated HMAT table
> >>
> >> Hello
> >>
> >> Like what I added at the end of
> >> https://github.com/bgoglin/qemu/commit/d9b3f5cb1514adafa644afcc2a363f2dc9795a32
> >> ?
> > yep, only full version including headers.
>
>
> Thanks,
>
> I split the patch adding the new test in 3 patches, reduced memory to
> 128M total, etc.
>
> I am not sure I understood what I am supposed to put in commit messages.
> Can you check the 4 patches on top of
> https://github.com/bgoglin/qemu/commits/hmat-noinitiator before I resend
> them to the list?
>
> Brice
>
I left a couple of trivial comments on github, but basically looks good
to me.
Jonathan
prev parent reply other threads:[~2022-06-23 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:29 [PATCH] hmat acpi: Don't require initiator value in -numa when hmat=on Brice Goglin
2022-04-06 13:44 ` Jonathan Cameron via
2022-06-17 15:59 ` Brice Goglin
2022-06-20 13:27 ` Igor Mammedov
2022-06-20 15:24 ` Brice Goglin
2022-06-20 16:05 ` Igor Mammedov
2022-06-21 10:49 ` Brice Goglin
2022-06-23 11:24 ` Jonathan Cameron via [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=20220623122457.0000646b@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Brice.Goglin@inria.fr \
--cc=Jonathan.Cameron@Huawei.com \
--cc=eduardo@habkost.net \
--cc=f4bug@amsat.org \
--cc=imammedo@redhat.com \
--cc=jingqi.liu@intel.com \
--cc=tao3.xu@intel.com \
--cc=wangyanan55@huawei.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).