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 <mpriv...@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, -- 2.26.2