From: Tao Xu <tao3.xu@intel.com>
To: Eric Blake <eblake@redhat.com>, mst@redhat.com, imammedo@redhat.com
Cc: ehabkost@redhat.com, jingqi.liu@intel.com, qemu-devel@nongnu.org,
pbonzini@redhat.com, danmei.wei@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2 4/9] Extend the command-line to provide memory latency and bandwidth information
Date: Mon, 28 Jan 2019 17:42:54 +0800 [thread overview]
Message-ID: <d4fef646-8c95-aa60-b116-8f54ed2ce71e@intel.com> (raw)
In-Reply-To: <e781ace4-b415-2325-d74f-88f586de6dda@redhat.com>
On 1/22/2019 1:09 AM, Eric Blake wrote:
> On 1/21/19 12:03 AM, Tao Xu wrote:
>
>>>> #
>>>> +# @hmat-lb: memory latency and bandwidth information (Since: 2.13)
>>> s/2.13/4.0/ (probably in multiple spots in your series)
>> Hi Eric,
>>
>> Thank you for your comments. The spell mistakes in patches 1/9 to 6/9
>> have been corrected in patch 7/9. Because patches 1/9 to 6/9 are jingqi's
>> initial V1 patchesand7/9 to 9/9 are the changes compared withV1.
>
> Still, it's better to rebase the series to avoid the mistakes in the
> first place, instead of having churn with a mistake early in the series
> corrected only later in the series. Even if the mistake is corrected by
> a different author than the bulk of the patch, as long as there are
> Signed-off-by lines for both the original author and the person making
> the spelling correction, then proper attribution has been made.
>
>>
>> About s/2.13/4.0/,do you mean ACPI HMAT will not be merged before QEMU
>> 4.0?
>
> Correct - 4.0 is the next release planned. There was no 2.13 release;
> after 2.12 was the 3.0 release; the current release is 3.1, and the next
> release is 4.0; for more details, see
> https://www.qemu.org/2018/08/15/qemu-3-0-0/ for a description of the
> current version numbering scheme. And even making it in time for 4.0
> means polishing this by mid-March: https://wiki.qemu.org/Planning/4.0
>
>>
>> In addition, do you have any other comments about these patches?
>
> I was commenting on the high-level user interface issues, but will leave
> the bulk of the technical review to those more familiar with the code
> being added.
>
Hi Eric, I am sorry for asking you so frequently and don't mean to rush
you. Could you tell me when I can know this comments on the high-level
user interface issues? So that I can improve my patch in the next
version. Thank you and looking forward to your reply!
next prev parent reply other threads:[~2019-01-28 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 15:34 [Qemu-devel] [PATCH v2 0/9] Build ACPI Heterogeneous Memory Attribute Table (HMAT) Tao Xu
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 1/9] hmat acpi: Build Memory Subsystem Address Range Structure(s) in ACPI HMAT Tao Xu
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 2/9] hmat acpi: Build System Locality Latency and Bandwidth Information " Tao Xu
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 3/9] hmat acpi: Build Memory Side Cache " Tao Xu
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 4/9] Extend the command-line to provide memory latency and bandwidth information Tao Xu
2019-01-14 19:38 ` Eric Blake
2019-01-21 6:03 ` Tao Xu
2019-01-21 17:09 ` Eric Blake
2019-01-28 9:42 ` Tao Xu [this message]
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 5/9] numa: Extend the command-line to provide memory side cache information Tao Xu
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 6/9] hmat acpi: Implement _HMA method to update HMAT at runtime Tao Xu
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 7/9] hmat acpi: fix some coding style and small issues Tao Xu
2019-01-21 17:11 ` Eric Blake
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 8/9] hmat acpi: move some function inside of the caller Tao Xu
2019-01-11 15:34 ` [Qemu-devel] [PATCH v2 9/9] acpi: rewrite the _FIT method to use it in _HMA method Tao Xu
2019-01-13 19:07 ` [Qemu-devel] [PATCH v2 0/9] 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=d4fef646-8c95-aa60-b116-8f54ed2ce71e@intel.com \
--to=tao3.xu@intel.com \
--cc=danmei.wei@intel.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jingqi.liu@intel.com \
--cc=mst@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).