From: David Gibson <david@gibson.dropbear.id.au>
To: agraf@suse.de
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH 4/5] pseries: Remove extraneous prints
Date: Tue, 31 Jul 2012 16:09:04 +1000 [thread overview]
Message-ID: <1343714945-20726-5-git-send-email-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <1343714945-20726-1-git-send-email-david@gibson.dropbear.id.au>
The pseries machine prints several messages to stderr whenever it starts up
and another whenever the vm is reset. It's not normal for qemu machines to
do this though, so this patch removes them. We can put them back
conditional on a DEBUG symbol if we really need them in future.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
hw/spapr.c | 18 ------------------
1 file changed, 18 deletions(-)
diff --git a/hw/spapr.c b/hw/spapr.c
index bf38823..693441e 100644
--- a/hw/spapr.c
+++ b/hw/spapr.c
@@ -540,8 +540,6 @@ static void spapr_reset(void *opaque)
{
sPAPREnvironment *spapr = (sPAPREnvironment *)opaque;
- fprintf(stderr, "sPAPR reset\n");
-
/* flush out the hash table */
memset(spapr->htab, 0, spapr->htab_size);
@@ -771,14 +769,6 @@ static void ppc_spapr_init(ram_addr_t ram_size,
exit(1);
}
- fprintf(stderr, "sPAPR memory map:\n");
- fprintf(stderr, "RTAS : 0x%08lx..%08lx\n",
- (unsigned long)spapr->rtas_addr,
- (unsigned long)(spapr->rtas_addr + spapr->rtas_size - 1));
- fprintf(stderr, "FDT : 0x%08lx..%08lx\n",
- (unsigned long)spapr->fdt_addr,
- (unsigned long)(spapr->fdt_addr + FDT_MAX_SIZE - 1));
-
if (kernel_filename) {
uint64_t lowaddr = 0;
@@ -794,8 +784,6 @@ static void ppc_spapr_init(ram_addr_t ram_size,
kernel_filename);
exit(1);
}
- fprintf(stderr, "Kernel : 0x%08x..%08lx\n",
- KERNEL_LOAD_ADDR, KERNEL_LOAD_ADDR + kernel_size - 1);
/* load initrd */
if (initrd_filename) {
@@ -810,8 +798,6 @@ static void ppc_spapr_init(ram_addr_t ram_size,
initrd_filename);
exit(1);
}
- fprintf(stderr, "Ramdisk : 0x%08lx..%08lx\n",
- (long)initrd_base, (long)(initrd_base + initrd_size - 1));
} else {
initrd_base = 0;
initrd_size = 0;
@@ -825,10 +811,6 @@ static void ppc_spapr_init(ram_addr_t ram_size,
exit(1);
}
g_free(filename);
- fprintf(stderr, "Firmware load : 0x%08x..%08lx\n",
- 0, fw_size);
- fprintf(stderr, "Firmware runtime : 0x%08lx..%08lx\n",
- load_limit, (unsigned long)spapr->fdt_addr);
spapr->entry_point = 0x100;
--
1.7.10.4
next prev parent reply other threads:[~2012-07-31 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 6:09 [Qemu-devel] [0/5] Assorted pseries fixes and updates David Gibson
2012-07-31 6:09 ` [Qemu-devel] [PATCH 1/5] pseries: Update SLOF David Gibson
2012-07-31 6:09 ` [Qemu-devel] [PATCH 2/5] pseries: Instantiate USB if requested David Gibson
2012-07-31 7:35 ` Benjamin Herrenschmidt
2012-07-31 7:36 ` Benjamin Herrenschmidt
2012-08-04 7:34 ` Li Zhang
2012-07-31 6:09 ` [Qemu-devel] [PATCH 3/5] pseries: Add support for -vga option David Gibson
2012-07-31 6:09 ` David Gibson [this message]
2012-07-31 6:09 ` [Qemu-devel] [PATCH 5/5] pseries: Add support for new KVM hash table control call David Gibson
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=1343714945-20726-5-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).