From: "Andreas Färber" <afaerber@suse.de>
To: Hu Tao <hutao@cn.fujitsu.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix some printf errors when debug is enabled
Date: Thu, 13 Jun 2013 13:10:04 +0200 [thread overview]
Message-ID: <51B9A88C.3080105@suse.de> (raw)
In-Reply-To: <1371120709-18923-1-git-send-email-hutao@cn.fujitsu.com>
Am 13.06.2013 12:51, schrieb Hu Tao:
> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
> ---
> cputlb.c | 4 ++--
> hw/acpi/piix4.c | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/cputlb.c b/cputlb.c
> index 86666c8..1230e9e 100644
> --- a/cputlb.c
> +++ b/cputlb.c
> @@ -262,8 +262,8 @@ void tlb_set_page(CPUArchState *env, target_ulong vaddr,
>
> #if defined(DEBUG_TLB)
> printf("tlb_set_page: vaddr=" TARGET_FMT_lx " paddr=0x" TARGET_FMT_plx
> - " prot=%x idx=%d pd=0x%08lx\n",
> - vaddr, paddr, prot, mmu_idx, pd);
> + " prot=%x idx=%d\n",
> + vaddr, paddr, prot, mmu_idx);
> #endif
>
> address = vaddr;
> diff --git a/hw/acpi/piix4.c b/hw/acpi/piix4.c
> index e6525ac..eafa76f 100644
> --- a/hw/acpi/piix4.c
> +++ b/hw/acpi/piix4.c
> @@ -518,7 +518,7 @@ static uint64_t gpe_readb(void *opaque, hwaddr addr, unsigned width)
> PIIX4PMState *s = opaque;
> uint32_t val = acpi_gpe_ioport_readb(&s->ar, addr);
>
> - PIIX4_DPRINTF("gpe read %x == %x\n", addr, val);
> + PIIX4_DPRINTF("gpe read %lx == %x\n", addr, val);
You need HWADDR_PRIx as seen below, because it might be %llx on some
platforms. While touching it, changing %x to PRIx32 would be even better.
> return val;
> }
>
> @@ -530,7 +530,7 @@ static void gpe_writeb(void *opaque, hwaddr addr, uint64_t val,
> acpi_gpe_ioport_writeb(&s->ar, addr, val);
> pm_update_sci(s);
>
> - PIIX4_DPRINTF("gpe write %x <== %d\n", addr, val);
> + PIIX4_DPRINTF("gpe write %lx <== %lu\n", addr, val);
HWADDR_PRIx, PRIx64
Regards,
Andreas
> }
>
> static const MemoryRegionOps piix4_gpe_ops = {
> @@ -579,7 +579,7 @@ static void pci_write(void *opaque, hwaddr addr, uint64_t data,
> switch (addr) {
> case PCI_EJ_BASE - PCI_HOTPLUG_ADDR:
> acpi_piix_eject_slot(opaque, (uint32_t)data);
> - PIIX4_DPRINTF("pciej write %" HWADDR_PRIx " <== % " PRIu64 "\n",
> + PIIX4_DPRINTF("pciej write %" HWADDR_PRIx " <== %" PRIu64 "\n",
> addr, data);
> break;
> default:
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-06-13 11:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 10:51 [Qemu-devel] [PATCH] fix some printf errors when debug is enabled Hu Tao
2013-06-13 10:51 ` [Qemu-devel] [PATCH] fix typo: apci -> acpi Hu Tao
2013-06-13 11:05 ` Andreas Färber
2013-06-17 2:08 ` Hu Tao
2013-06-17 6:20 ` Michael Tokarev
2013-06-13 10:51 ` [Qemu-devel] [PATCH] remove call to type_initialize in object_new_with_type Hu Tao
2013-06-14 7:09 ` Hu Tao
2013-06-14 13:06 ` Peter Crosthwaite
2013-06-14 13:02 ` Peter Crosthwaite
2013-06-13 11:10 ` Andreas Färber [this message]
2013-06-13 11:13 ` [Qemu-devel] [PATCH] fix some printf errors when debug is enabled Andreas Färber
2013-06-14 6:52 ` Hu Tao
2013-06-14 7:11 ` [Qemu-devel] [PATCH v2] piix: " Hu Tao
2013-06-14 7:19 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2013-06-14 10:27 ` Michael Tokarev
2013-06-17 2:09 ` Hu Tao
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=51B9A88C.3080105@suse.de \
--to=afaerber@suse.de \
--cc=hutao@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).