From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Amit Shah <amit.shah@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
dgilbert@redhat.com, Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH] migration/ram: fix build on 32 bit hosts
Date: Thu, 12 Nov 2015 16:53:48 +0200 [thread overview]
Message-ID: <1447340003-12265-1-git-send-email-mst@redhat.com> (raw)
ram_addr_t must be printed with RAM_ADDR_FMT not %z.
Also, change size print to %zx to match what RAM_ADDR_FMT does.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
migration/ram.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index 62cf42b..80a67bb 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -1184,7 +1184,7 @@ int ram_save_queue_pages(MigrationState *ms, const char *rbname,
}
trace_ram_save_queue_pages(ramblock->idstr, start, len);
if (start+len > ramblock->used_length) {
- error_report("%s request overrun start=%zx len=%zx blocklen=%zx",
+ error_report("%s request overrun start=0x" RAM_ADDR_FMT " len=0x" RAM_ADDR_FMT " blocklen=0x" RAM_ADDR_FMT,
__func__, start, len, ramblock->used_length);
goto err;
}
@@ -1845,7 +1845,7 @@ int ram_discard_range(MigrationIncomingState *mis,
ret = postcopy_ram_discard_range(mis, host_startaddr, length);
} else {
error_report("ram_discard_range: Overrun block '%s' (%" PRIu64
- "/%zu/%zu)",
+ "/%zx/0x" RAM_ADDR_FMT ")",
block_name, start, length, rb->used_length);
}
--
MST
next reply other threads:[~2015-11-12 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 14:53 Michael S. Tsirkin [this message]
2015-11-12 15:28 ` [Qemu-devel] [PATCH] migration/ram: fix build on 32 bit hosts Juan Quintela
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=1447340003-12265-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).