: Clean up boot time console messages
Subsystems (4)
cover : Clean up boot time console messages
Here's a series of patches that removes a bunch of console messages during PPC boot. They are moved to KERN_DEBUG instead, which means that:
1. They will still be in dmesg.
2. If needed for debugging, they can be enabled by adding "loglevel=8" to the boot command line.
But for most uses, I don't see how these messages really add value to the user. The information is normally available at other places, and mostly needed when trying to figure out why something doesn't work right.
Since these are all janitorial, I'd appreciate them being queued for 2.6.18.
-Olof
PATCH 1/10 : Quiet HVSI boot output
There's no real need to print the number of found HVSI devices on the console at every boot.
drivers/char/hvsi.c +1 -1
@@ -1179,7 +1179,7 @@ static int __init hvsi_init(void)if (tty_register_driver (hvsi_driver))panic ("Couldn't register hvsi console driver\n" ); -printk (KERN_INFO "HVSI: registered %i devices\n" , hvsi_count); +printk (KERN_DEBUG "HVSI: registered %i devices\n" , hvsi_count);return 0 ; }
PATCH 2/10 : Quiet time init output
In reply to Olof JohanssonMove time_init console output to KERN_DEBUG prink level. No need to print it at every boot.
arch/powerpc/kernel/time.c +2 -2
@@ -945,9 +945,9 @@ void __init time_init(void) }else {/* Normal PowerPC with timebase register */ ppc_md.calibrate_decr (); -printk (KERN_INFO "time_init: decrementer frequency = %lu.%.6lu MHz\n" , +printk (KERN_DEBUG "time_init: decrementer frequency = %lu.%.6lu MHz\n" , ppc_tb_freq /1000000 , ppc_tb_freq %1000000 ); -printk (KERN_INFO "time_init: processor frequency = %lu.%.6lu MHz\n" , +printk (KERN_DEBUG "time_init: processor frequency = %lu.%.6lu MHz\n" , ppc_proc_freq /1000000 , ppc_proc_freq %1000000 ); tb_last_stamp = tb_last_jiffy =get_tb (); }
PATCH 3/10 : Quiet page order output
In reply to Olof JohanssonNo need to always print page orders.
arch/powerpc/mm/hash_utils_64.c +1 -1
@@ -319,7 +319,7 @@ static void __init htab_init_page_sizes( mmu_virtual_psize =MMU_PAGE_64K ;#endif -printk (KERN_INFO "Page orders: linear mapping = %d, others = %d\n" , +printk (KERN_DEBUG "Page orders: linear mapping = %d, others = %d\n" , mmu_psize_defs[mmu_linear_psize].shift, mmu_psize_defs[mmu_virtual_psize].shift);
PATCH 4/10 : Quiet VETH version printk
In reply to Olof Johanssonibmveth_printk() is only used to print the driver version when the module initializes, which means on all machines as long as it's compiled in.
If it's really only needed for debugging, boot with loglevel=8, or get it from dmesg instead.
drivers/net/ibmveth.c +1 -1
@@ -61,7 +61,7 @@#undef DEBUG #define ibmveth_printk(fmt, args...) \ - printk(KERN_INFO "%s: " fmt, __FILE__, ## args) + printk(KERN_DEBUG "%s: " fmt, __FILE__, ## args) #define ibmveth_error_printk(fmt, args...) \ printk(KERN_ERR "(%s:%3.3d ua:%x) ERROR: " fmt, __FILE__, __LINE__ , adapter->vdev->unit_address, ## args)
PATCH 5/10 : Don't print chosen idle loop at every boot
In reply to Olof JohanssonNo need to write out what idle loop is used on every boot.
arch/powerpc/platforms/maple/setup.c +1 -1
@@ -189,7 +189,7 @@ void __init maple_setup_arch(void) conswitchp = &dummy_con;#endif -printk (KERN_INFO "Using native/NAP idle loop\n" ); +printk (KERN_DEBUG "Using native/NAP idle loop\n" ); }/*
arch/powerpc/platforms/iseries/setup.c +2 -2
@@ -535,10 +535,10 @@ static void __init iSeries_setup_arch(vo {if (get_lppaca ()->shared_proc) { ppc_md.idle_loop = iseries_shared_idle; -printk (KERN_INFO "Using shared processor idle loop\n" ); +printk (KERN_DEBUG "Using shared processor idle loop\n" ); }else { ppc_md.idle_loop = iseries_dedicated_idle; -printk (KERN_INFO "Using dedicated idle loop\n" ); +printk (KERN_DEBUG "Using dedicated idle loop\n" ); }/* Setup the Lp Event Queue */
arch/powerpc/platforms/powermac/feature.c +1 -1
@@ -2510,7 +2510,7 @@ found:if (get_property (np,"flush-on-lock" ,NULL ))break ; powersave_nap =1 ; -printk (KERN_INFO "Processor NAP mode on idle enabled.\n" ); +printk (KERN_DEBUG "Processor NAP mode on idle enabled.\n" );break ; }
arch/powerpc/platforms/pseries/setup.c +3 -3
@@ -235,14 +235,14 @@ static void __init pSeries_setup_arch(voif (firmware_has_feature (FW_FEATURE_SPLPAR )) {vpa_init (boot_cpuid);if (get_lppaca ()->shared_proc) { -printk (KERN_INFO "Using shared processor idle loop\n" ); +printk (KERN_DEBUG "Using shared processor idle loop\n" ); ppc_md.power_save = pseries_shared_idle_sleep; }else { -printk (KERN_INFO "Using dedicated idle loop\n" ); +printk (KERN_DEBUG "Using dedicated idle loop\n" ); ppc_md.power_save = pseries_dedicated_idle_sleep; } }else { -printk (KERN_INFO "Using default idle loop\n" ); +printk (KERN_DEBUG "Using default idle loop\n" ); }if (firmware_has_feature (FW_FEATURE_LPAR ))
PATCH 6/10 : Less verbose mem configuration output
In reply to Olof JohanssonQuieten some of the debug ram config output. we already print out available memory at KERN_INFO level.
arch/powerpc/mm/mem.c +3 -3
@@ -299,9 +299,9 @@ void __init paging_init(void) kmap_prot =PAGE_KERNEL ;#endif /* CONFIG_HIGHMEM */ -printk (KERN_INFO "Top of RAM: 0x%lx, Total RAM: 0x%lx\n" , +printk (KERN_DEBUG "Top of RAM: 0x%lx, Total RAM: 0x%lx\n" , top_of_ram, total_ram); -printk (KERN_INFO "Memory hole size: %ldMB\n" , +printk (KERN_DEBUG "Memory hole size: %ldMB\n" , (top_of_ram - total_ram) >>20 );/* * All pages are DMA-able so we put them all in the DMA zone.
@@ -380,7 +380,7 @@ void __init mem_init(void) totalhigh_pages++; } totalram_pages += totalhigh_pages; -printk (KERN_INFO "High memory: %luk\n" , +printk (KERN_DEBUG "High memory: %luk\n" , totalhigh_pages << (PAGE_SHIFT -10 )); }#endif /* CONFIG_HIGHMEM */
arch/powerpc/mm/numa.c +4 -4
@@ -465,9 +465,9 @@ static void __init setup_nonnuma(void)unsigned long total_ram =lmb_phys_mem_size ();unsigned int i; -printk (KERN_INFO "Top of RAM: 0x%lx, Total RAM: 0x%lx\n" , +printk (KERN_DEBUG "Top of RAM: 0x%lx, Total RAM: 0x%lx\n" , top_of_ram, total_ram); -printk (KERN_INFO "Memory hole size: %ldMB\n" , +printk (KERN_DEBUG "Memory hole size: %ldMB\n" , (top_of_ram - total_ram) >>20 );for (i =0 ; i < lmb.memory.cnt; ++i)
@@ -485,7 +485,7 @@ void __init dump_numa_cpu_topology(void)return ;for_each_online_node (node) { -printk (KERN_INFO "Node %d CPUs:" , node); +printk (KERN_DEBUG "Node %d CPUs:" , node); count =0 ;/*
@@ -521,7 +521,7 @@ static void __init dump_numa_memory_topofor_each_online_node (node) {unsigned long i; -printk (KERN_INFO "Node %d Memory:" , node); +printk (KERN_DEBUG "Node %d Memory:" , node); count =0 ;
PATCH 7/10 : Lack of ISA interrupts on XICS isn't dangerous
In reply to Olof JohanssonThis isn't really a dangerous thing any more; most systems lack ISA interrupt controllers.
arch/powerpc/platforms/pseries/xics.c +1 -1
@@ -522,7 +522,7 @@ nextnode: np =of_find_node_by_type (NULL ,"interrupt-controller" );if (!np) { -printk (KERN_WARNING "xics: no ISA interrupt controller\n" ); +printk (KERN_DEBUG "xics: no ISA interrupt controller\n" ); xics_irq_8259_cascade_real =-1 ; xics_irq_8259_cascade =-1 ; }else {
PATCH 8/10 : Quiet PCI init printouts
In reply to Olof JohanssonQuiet some of the more debug related output from the pci probe routines.
arch/powerpc/kernel/pci_64.c +5 -5
@@ -605,7 +605,7 @@ static int __init pcibios_init(void)iSeries_pcibios_init ();#endif -printk ("PCI: Probing PCI hardware\n" ); +printk (KERN_DEBUG "PCI: Probing PCI hardware\n" );/* Scan all of the recorded PCI controllers. */ list_for_each_entry_safe (hose, tmp, &hose_list, list_node) {
@@ -630,14 +630,14 @@ static int __init pcibios_init(void)/* Cache the location of the ISA bridge (if we have one) */ ppc64_isabridge_dev =pci_get_class (PCI_CLASS_BRIDGE_ISA <<8 ,NULL );if (ppc64_isabridge_dev !=NULL ) -printk ("ISA bridge at %s\n" ,pci_name (ppc64_isabridge_dev)); +printk (KERN_DEBUG "ISA bridge at %s\n" ,pci_name (ppc64_isabridge_dev));#ifdef CONFIG_PPC_MULTIPLATFORM /* map in PCI I/O space */ phbs_remap_io ();#endif -printk ("PCI: Probing PCI hardware done\n" ); +printk (KERN_DEBUG "PCI: Probing PCI hardware done\n" );return 0 ; }
@@ -804,7 +804,7 @@ static pgprot_t __pci_mmap_set_pgprot(stelse prot |= _PAGE_GUARDED; -printk ("PCI map for %s:%lx, prot: %lx\n" ,pci_name (dev), rp->start, +printk (KERN_DEBUG "PCI map for %s:%lx, prot: %lx\n" ,pci_name (dev), rp->start, prot);return __pgprot (prot);
@@ -1212,7 +1212,7 @@ int remap_bus_range(struct pci_bus *bus)return 1 ;if (start_phys ==0 )return 1 ; -printk ("mapping IO %lx -> %lx, size: %lx\n" , start_phys, start_virt, size); +printk (KERN_DEBUG "mapping IO %lx -> %lx, size: %lx\n" , start_phys, start_virt, size);if (__ioremap_explicit (start_phys, start_virt, size, _PAGE_NO_CACHE | _PAGE_GUARDED))return 1 ;
PATCH 9/10 : Quiet rtasd output at boot
In reply to Olof JohanssonMost users won't really know the difference between a started RTAS daemon and a missing event-scan. Move it to debug levels.
arch/powerpc/platforms/pseries/rtasd.c +3 -3
@@ -348,7 +348,7 @@ static int enable_surveillance(int timeoreturn 0 ;if (error == -EINVAL ) { -printk (KERN_INFO "rtasd: surveillance not supported\n" ); +printk (KERN_DEBUG "rtasd: surveillance not supported\n" );return 0 ; }
@@ -440,7 +440,7 @@ static int rtasd(void *unused) goto error; } -printk (KERN_INFO "RTAS daemon started\n" ); +printk (KERN_DEBUG "RTAS daemon started\n" );DEBUG ("will sleep for %d milliseconds\n" , (30000 /rtas_event_scan_rate));
@@ -487,7 +487,7 @@ static int __init rtas_init(void)/* No RTAS */ if (rtas_token ("event-scan" ) ==RTAS_UNKNOWN_SERVICE ) { -printk (KERN_INFO "rtasd: no event-scan on system\n" ); +printk (KERN_DEBUG "rtasd: no event-scan on system\n" );return 1 ; }
PATCH 10/10 : Quiet oprofile output at boot
In reply to Olof JohanssonNo need to always print out which performance monitoring type is used on the console at every boot.
arch/powerpc/oprofile/common.c +1 -1
@@ -162,7 +162,7 @@ int __init oprofile_arch_init(struct opr ops->stop = op_powerpc_stop; ops->backtrace = op_powerpc_backtrace; -printk (KERN_INFO "oprofile: using %s performance monitoring.\n" , +printk (KERN_DEBUG "oprofile: using %s performance monitoring.\n" , ops->cpu_type);return 0 ;