Displaying 4 results from an estimated 4 matches for "printk_start_of_lin".
Did you mean:
printk_start_of_line
2013 Aug 16
7
[PATCH v2] xen/console: buffer and show origin of guest PV writes
...}
- spin_unlock_irq(&console_lock);
-
guest_handle_add_offset(buffer, kcount);
count -= kcount;
}
@@ -504,12 +547,12 @@ static int printk_prefix_check(char *p, char **pp)
((loglvl < upper_thresh) && printk_ratelimit()));
}
-static void printk_start_of_line(void)
+static void printk_start_of_line(const char *prefix)
{
struct tm tm;
char tstr[32];
- __putstr("(XEN) ");
+ __putstr(prefix);
if ( !opt_console_timestamps )
return;
@@ -524,12 +567,11 @@ static void printk_start_of_line(void)
__putstr(tstr);...
2013 Sep 09
0
[PATCH v3] xen/console: buffer and show origin of guest PV writes
...}
- spin_unlock_irq(&console_lock);
-
guest_handle_add_offset(buffer, kcount);
count -= kcount;
}
@@ -504,12 +547,12 @@ static int printk_prefix_check(char *p, char **pp)
((loglvl < upper_thresh) && printk_ratelimit()));
}
-static void printk_start_of_line(void)
+static void printk_start_of_line(const char *prefix)
{
struct tm tm;
char tstr[32];
- __putstr("(XEN) ");
+ __putstr(prefix);
if ( !opt_console_timestamps )
return;
@@ -524,12 +567,11 @@ static void printk_start_of_line(void)
__putstr(tstr);...
2012 Oct 18
3
[PATCH 1/1] keep iommu disabled until iommu_setup is called
......) is called that got introduced with
patch "x86-64: detect processors subject to AMD erratum #121 and refuse to
boot." since xen 4.1.3 and results in the following stacktrace:
find_iommu_for_device
amd_iommu_ioapic_update_ire
timer_interrupt
enable_8259_A_irq
do_IRQ
printk_start_of_line
acpi_os_printf
io_apic_write
__ioapic_write_entry
ioapic_write_entry
__clear_IO_APIC_pin
clear_IO_APIC
disable_IO_APIC
__stop_this_cpu
smp_send_stop
machine_restart
panic
tasklet_schedule_on_cpu
display_cacheinfo
init_amd
generic_identify
identify_cp...
2012 Oct 18
0
[PATCH 0/1] fix xen-crash at panic()-call during boot
...ocessors subject to AMD erratum
#121 and refuse to boot."
Instead of the actual panic-message from the patch the following stacktrace
appears (i typed it down from screen, so it might contain typos)
find_iommu_for_device
amd_iommu_ioapic_update_ire
timer_interrupt
enable_8259_A_irq
do_IRQ
printk_start_of_line
acpi_os_printf
io_apic_write
__ioapic_write_entry
ioapic_write_entry
__clear_IO_APIC_pin
clear_IO_APIC
disable_IO_APIC
__stop_this_cpu
smp_send_stop
machine_restart
panic
tasklet_schedule_on_cpu
display_cacheinfo
init_amd
generic_identify
identify_cpu
_start_xen
_high_start
Panic on CPU 0:
Xen BU...