qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] ramblock: add new hmp command "info ramblock"
Date: Fri, 28 Apr 2017 12:07:41 +0100	[thread overview]
Message-ID: <20170428110740.GF2085@work-vm> (raw)
In-Reply-To: <20170428103950.GF22801@pxdev.xzpeter.org>

* Peter Xu (peterx@redhat.com) wrote:
> On Fri, Apr 28, 2017 at 06:21:30PM +0800, Peter Xu wrote:
> > On Thu, Apr 27, 2017 at 12:23:14PM +0100, Dr. David Alan Gilbert wrote:
> 
> [...]
> 
> > > > +void ram_block_dump(Monitor *mon)
> > > > +{
> > > > +    RAMBlock *block;
> > > > +
> > > > +    rcu_read_lock();
> > > > +    monitor_printf(mon, "%24s %8s  %18s %18s %18s\n",
> > > > +                   "Block Name", "PSize", "Offset", "Used", "Total");
> > > > +    RAMBLOCK_FOREACH(block) {
> > > > +        monitor_printf(mon, "%24s %8s  0x%016" PRIx64 " 0x%016" PRIx64
> > > > +                       " 0x%016" PRIx64 "\n", block->idstr,
> > > > +                       page_size_to_str(block->page_size),
> > > > +                       (uint64_t)block->offset,
> > > > +                       (uint64_t)block->used_length,
> > > > +                       (uint64_t)block->max_length);
> > > > +    }
> > > 
> > > Yes that should work, I remember there's a RAM_ADDR_FMT macro that's
> > > supposed to be usable for ram_addr_t, but that's fine.
> > 
> > That looks better. Will switch to that. Thanks!
> 
> Oh, I found that RAM_ADDR_FMT didn't allow me to do the formatting
> with width ("%016..."). So maybe I'll still use current way for now.

Oh then just stick to the PRIx64 and the case; it's fine.

Dave

> -- 
> Peter Xu
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

      reply	other threads:[~2017-04-28 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27  9:58 [Qemu-devel] [PATCH v3 0/2] ramblock: add hmp command "info ramblock" Peter Xu
2017-04-27  9:58 ` [Qemu-devel] [PATCH v3 1/2] ramblock: add RAMBLOCK_FOREACH() Peter Xu
2017-04-27 10:49   ` Dr. David Alan Gilbert
2017-04-27  9:58 ` [Qemu-devel] [PATCH v3 2/2] ramblock: add new hmp command "info ramblock" Peter Xu
2017-04-27 11:23   ` Dr. David Alan Gilbert
2017-04-28 10:21     ` Peter Xu
2017-04-28 10:39       ` Peter Xu
2017-04-28 11:07         ` Dr. David Alan Gilbert [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=20170428110740.GF2085@work-vm \
    --to=dgilbert@redhat.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@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).