search for: vprintk

...xb0 [<c012037d>] do_softirq+0x4d/0x50 [<c010d062>] do_IRQ+0x22/0x30 [<c01048a0>] evtchn_do_upcall+0x70/0xa0 [<c0108c48>] hypervisor_callback+0x2c/0x34 [<c010482c>] force_evtchn_callback+0xc/0x10 [<c011bdde>] release_console_sem+0x5e/0xd0 [<c011bc07>] vprintk+0x197/0x260 [<c011bc07>] vprintk+0x197/0x260 [<c010d062>] do_IRQ+0x22/0x30 [<c01048a0>] evtchn_do_upcall+0x70/0xa0 [<c0108c48>] hypervisor_callback+0x2c/0x34 [<c011ba67>] printk+0x17/0x20 [<c01546d5>] show_swap_cache_info+0x45/0x80 [<c0142173>] show_...

...rted+0x37/0x40 [<c0450293>] ? warn_slowpath_fmt_taint+0x33/0x40 [<c0477e67>] ? mark_hardware_unsupported+0x37/0x40 [<c08056eb>] ? early_init_centaur+0xd/0x2d [<c0a49835>] ? early_cpu_init+0x11a/0x13e [<c0a453b3>] ? setup_arch+0x38/0xb90 [<c0450d3e>] ? vprintk+0x1ae/0x490 [<c080ba2a>] ? printk+0x17/0x1d [<c0a5a4ee>] ? cgroup_init_subsys+0xcf/0xdb [<c0a406da>] ? start_kernel+0xca/0x3a4 ---[ end trace a7919e7f17c0a725 ]--- Disabling lock debugging due to kernel taint I traced it down to this code, which is not in the standard ker...

...ave_callable_console(void) * printf(3) */ +extern void lguest_vprint(const char *fmt, va_list ap); asmlinkage int printk(const char *fmt, ...) { va_list args; + va_list lgargs; int r; va_start(args, fmt); + va_copy(lgargs, args); + lguest_vprint(fmt, lgargs); + va_end(lgargs); r = vprintk(fmt, args); va_end(args); --

...ave_callable_console(void) * printf(3) */ +extern void lguest_vprint(const char *fmt, va_list ap); asmlinkage int printk(const char *fmt, ...) { va_list args; + va_list lgargs; int r; va_start(args, fmt); + va_copy(lgargs, args); + lguest_vprint(fmt, lgargs); + va_end(lgargs); r = vprintk(fmt, args); va_end(args); --

(Moving from offlist discussion.) I''m interested in opinions... Assume there are four single vcpu domains A, B, C, D, running on a 2-CPU physical machine. We wish to test for time skew on domain A. Assuming B, C, and D are all running some workload that attempts to fully saturate the (single) cpu. 1) Should the affect on domain A be essentially the same regardless of what load

...le_drivers+0x75/0x90 Sep 17 15:26:18 box6 kernel: [ 1948.826066] [<ffffffff8106704a>] _call_console_drivers+0x4a/0x80 Sep 17 15:26:18 box6 kernel: [ 1948.826070] [<ffffffff810673dd>] release_console_sem+0xbd/0x220 Sep 17 15:26:18 box6 kernel: [ 1948.826073] [<ffffffff810679e3>] vprintk+0x1c3/0x470 Sep 17 15:26:18 box6 kernel: [ 1948.826078] [<ffffffffa00e7385>] ? vga16fb_imageblit+0x25/0x30 [vga16fb] Sep 17 15:26:18 box6 kernel: [ 1948.826084] [<ffffffff81557efa>] printk +0x41/0x47 Sep 17 15:26:18 box6 kernel: [ 1948.826088] [<ffffffff8155c0ae>] ? perf_event_...

Hello, I have Ubuntu installed as a domU on the debian dom0, and connect via VNC in dom0. This is great for doing installs, and seeing the console output. However the VNC session doesn''t seem to keep the active connection during a domU reboot. Has anyone got this working? If so, how? -- John _______________________________________________ Xen-users mailing list

Dear Sirs and Madams, I run a small visual effects production company, Hammerhead Productions. We'd like to have an easily extensible inexpensive relatively high-performance storage network using open-source components. I was hoping that OCFS2 would be that system. I have a half-dozen 2 TB fileservers I'd like the rest of the network to see as a single 12 TB disk, with the aggregate

...n disk and force a filesystem check on the next boot. - */ -NORET_TYPE void ext3_panic (struct super_block * sb, const char * function, - const char * fmt, ...) -{ - va_list args; - - va_start(args, fmt); - printk(KERN_CRIT "EXT3-fs error (device %s): %s: ",sb->s_id, function); - vprintk(fmt, args); - printk("\n"); - va_end(args); - - /* this is to prevent panic from syncing this filesystem */ - /* AKPM: is this sufficient? */ - sb->s_flags |= MS_RDONLY; - panic ("EXT3-fs panic forced\n"); -} - void ext3_warning (struct super_block * sb, const char * functio...

...printf(1,2) __cold void vringh_bad(const char *fmt, ...) +{ + static DEFINE_RATELIMIT_STATE(vringh_rs, + DEFAULT_RATELIMIT_INTERVAL, + DEFAULT_RATELIMIT_BURST); + if (__ratelimit(&vringh_rs)) { + va_list ap; + va_start(ap, fmt); + printk(KERN_NOTICE "vringh:"); + vprintk(fmt, ap); + va_end(ap); + } +} + +/* Returns vring->num if empty, -ve on error. */ +static inline int __vringh_get_head(const struct vringh *vrh, + int (*getu16)(u16 *val, const u16 *p), + u16 *last_avail_idx) +{ + u16 avail_idx, i, head; + int err; + + err = getu16(&avail_idx...

...printf(1,2) __cold void vringh_bad(const char *fmt, ...) +{ + static DEFINE_RATELIMIT_STATE(vringh_rs, + DEFAULT_RATELIMIT_INTERVAL, + DEFAULT_RATELIMIT_BURST); + if (__ratelimit(&vringh_rs)) { + va_list ap; + va_start(ap, fmt); + printk(KERN_NOTICE "vringh:"); + vprintk(fmt, ap); + va_end(ap); + } +} + +/* Returns vring->num if empty, -ve on error. */ +static inline int __vringh_get_head(const struct vringh *vrh, + int (*getu16)(u16 *val, const u16 *p), + u16 *last_avail_idx) +{ + u16 avail_idx, i, head; + int err; + + err = getu16(&avail_idx...

Hello. log of the crashing boot process: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-14-xen331-linux-2.6.29-rc6-crash.txt 2.6.29-rc5 based pv_ops dom0 works on the same computer.. with the same Xen version. I tried with and without pci=nomsi. adding ''noapic'' doesn''t seem to help (I need that with 2.6.29-rc5 to make it work). Any ideas

Hi, I have a problem with a dom0 which is unable to launch my domU : all my dom0 are Debian Lenny amd64 with Debian kernel 2.6.26-2-xen-amd64 and xen-hypervisor-3.2-1-amd64. Then all domU (PV) are Debian Lenny amd64 too, with vanilla kernel 2.6.29.6. So, this new dom0 can''t launch any domU which are working on an other dom0. Software is same on both dom0, and hardware is near the

This introduces vringh, which are generic accessors for virtio rings (host side). There's a host-side implementation in vhost, but it assumes that the rings are in userspace, and is tied to the vhost implementation. I have patches to adapt it to use vringh, but I'm pushing this in the next merge window for Sjur, who has CAIF patches which need it. This also includes a test program in

This introduces vringh, which are generic accessors for virtio rings (host side). There's a host-side implementation in vhost, but it assumes that the rings are in userspace, and is tied to the vhost implementation. I have patches to adapt it to use vringh, but I'm pushing this in the next merge window for Sjur, who has CAIF patches which need it. This also includes a test program in

...se) printf("XEN: CPU %u has VCPU ID %u\n", i, pc->pc_vcpu_id); @@ -790,6 +812,31 @@ xen_hvm_cpu_init(void) DPCPU_SET(vcpu_info, vcpu_info); } +/*----------------------------- Debug functions ------------------------------*/ +#define PRINTK_BUFSIZE 1024 +static int +vprintk(const char *fmt, __va_list ap) +{ + int retval, len; + static char buf[PRINTK_BUFSIZE]; + + retval = vsnprintf(buf, PRINTK_BUFSIZE - 1, fmt, ap); + buf[retval] = 0; + len = strlen(buf); + retval = HYPERVISOR_console_io(CONSOLEIO_write, len, (char *)buf); + return retval; +} + +void +xen_early_print...

...static int acquire_console_semaphore_for_printk(unsigned int cpu) +static int console_trylock_for_printk(unsigned int cpu) __releases(&logbuf_lock) { int retval = 0; - if (!try_acquire_console_sem()) { + if (console_trylock()) { retval = 1; /* @@ -827,12 +827,12 @@ asmlinkage int vprintk(const char *fmt, va_list args) * actual magic (print out buffers, wake up klogd, * etc). * - * The acquire_console_semaphore_for_printk() function + * The console_trylock_for_printk() function * will release 'logbuf_lock' regardless of whether it * actually gets the semaph...

...static int acquire_console_semaphore_for_printk(unsigned int cpu) +static int console_trylock_for_printk(unsigned int cpu) __releases(&logbuf_lock) { int retval = 0; - if (!try_acquire_console_sem()) { + if (console_trylock()) { retval = 1; /* @@ -827,12 +827,12 @@ asmlinkage int vprintk(const char *fmt, va_list args) * actual magic (print out buffers, wake up klogd, * etc). * - * The acquire_console_semaphore_for_printk() function + * The console_trylock_for_printk() function * will release 'logbuf_lock' regardless of whether it * actually gets the semaph...

...static int acquire_console_semaphore_for_printk(unsigned int cpu) +static int console_trylock_for_printk(unsigned int cpu) __releases(&logbuf_lock) { int retval = 0; - if (!try_acquire_console_sem()) { + if (console_trylock()) { retval = 1; /* @@ -827,12 +827,12 @@ asmlinkage int vprintk(const char *fmt, va_list args) * actual magic (print out buffers, wake up klogd, * etc). * - * The acquire_console_semaphore_for_printk() function + * The console_trylock_for_printk() function * will release 'logbuf_lock' regardless of whether it * actually gets the semaph...