From: Igor Mammedov <imammedo@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/2] qemu-options.hx: Document hmat-lb and hmat-cache order
Date: Tue, 16 Jun 2020 14:01:58 +0200 [thread overview]
Message-ID: <20200616140158.5ceaee74@redhat.com> (raw)
In-Reply-To: <5bd3f4a03227658cbdb1d184518c7805c1c0122f.1591794890.git.mprivozn@redhat.com>
On Wed, 10 Jun 2020 15:17:35 +0200
Michal Privoznik <mprivozn@redhat.com> wrote:
> To simplify internal implementation the hmat-cache parsing code
> expects hmat-lb to be already parsed. This means, that hmat-lb
> arguments must come before hmat-cache. Document this restriction
> so that management applications can follow it.
>
> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> qemu-options.hx | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/qemu-options.hx b/qemu-options.hx
> index b1a399079a..3fe9e6d6a0 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -319,6 +319,9 @@ SRST
> 'none/direct(direct-mapped)/complex(complex cache indexing)'. policy
> is the write policy. line is the cache Line size in bytes.
>
> + Please note, that due to internal implementation, '\ ``hmat-cache``\ '
> + must be configured only after '\ ``hmat-lb``\ ' option.
> +
> For example, the following options describe 2 NUMA nodes. Node 0 has
> 2 cpus and a ram, node 1 has only a ram. The processors in node 0
> access memory in node 0 with access-latency 5 nanoseconds,
prev parent reply other threads:[~2020-06-16 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:17 [PATCH v2 0/2] A pair of HMAT docs fixes Michal Privoznik
2020-06-10 13:17 ` [PATCH v2 1/2] qemu-options.hx: Mark all hmat-cache attributes required Michal Privoznik
2020-06-15 8:00 ` Markus Armbruster
2020-06-16 6:52 ` Michal Privoznik
2020-06-16 12:00 ` Igor Mammedov
2020-06-10 13:17 ` [PATCH v2 2/2] qemu-options.hx: Document hmat-lb and hmat-cache order Michal Privoznik
2020-06-15 8:02 ` Markus Armbruster
2020-06-16 6:46 ` Michal Privoznik
2020-06-22 8:12 ` Markus Armbruster
2020-06-16 12:01 ` Igor Mammedov [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=20200616140158.5ceaee74@redhat.com \
--to=imammedo@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).