qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thorsten Kohfeldt <thorsten.kohfeldt@gmx.de>,
	armbru@redhat.com, lcapitulino@redhat.com,
	alex.williamson@redhat.com, peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hmp: Improve 'info mtree' with optional parm for mapinfo
Date: Thu, 15 Sep 2016 11:52:47 +0200	[thread overview]
Message-ID: <b9b00660-59a8-b839-875c-6e343144c50e@redhat.com> (raw)
In-Reply-To: <4ccdfc3c-4796-cf1f-61a1-724ac560aa37@gmx.de>



On 07/09/2016 02:48, Thorsten Kohfeldt wrote:
> From: Thorsten Kohfeldt <mailto__qemu-devel@nongnu.org>
> Date: Wed, 31 Aug 2016 22:43:14 +0200
> Subject: [PATCH] hmp: Improve 'info mtree' with optional parm for mapinfo
> 
> Motivation
> When 'tuning' 'quirks' for VFIO imported devices, it is not easy to
> directly grasp the implications of the priorisation algorithms in place
> for the 'layered mapping' of memory regions.
> Even though there are rules (documented in docs/memory.txt), once in a
> while one might question the correctness of the actual implementation of
> the rules.
> Particularly, I believe I have uncovered a divergence of (sub-)region
> priorisation/order/visibility in a corner case of importing a device
> (which requires a 'quirk') with mmap enabled vs. mmap disabled.
> This modification provides a means of visualising the ACTUAL
> mapping/visibility/occlusion of subregions within regions, whereas the
> current info mtree command only lists the tree of regions (all, visible
> and invisible ones).
> It is primarily intended to provide support for easy presentation of my
> cause, but I strongly believe this modification also has general purpose
> advantages.

It is a useful addition, but I think a simpler presentation is also
fine.  What about "info mtree -f" which would visit the FlatView instead
of the tree?  The patch would probably be much shorter.

Thanks,

Paolo

  reply	other threads:[~2016-09-15  9:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  0:48 [Qemu-devel] [PATCH] hmp: Improve 'info mtree' with optional parm for mapinfo Thorsten Kohfeldt
2016-09-15  9:52 ` Paolo Bonzini [this message]
2016-09-16 17:06   ` Laszlo Ersek
2016-09-20  0:16   ` Thorsten Kohfeldt
2016-09-20  0:51     ` Laszlo Ersek
2016-09-20  7:56       ` Paolo Bonzini
2016-09-20 18:29         ` Thorsten Kohfeldt
2016-09-21 15:06           ` Paolo Bonzini
2016-09-20 18:23       ` Thorsten Kohfeldt
2016-09-20 18:46         ` Laszlo Ersek
2016-09-20 20:18           ` Thorsten Kohfeldt
2016-09-22 19:43       ` [Qemu-devel] [PATCH v2] vfio: Add support for mmapping sub-page MMIO BARs Thorsten Kohfeldt

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=b9b00660-59a8-b839-875c-6e343144c50e@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=armbru@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thorsten.kohfeldt@gmx.de \
    /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).