similar to: [PATCH] xen/hvc: Fix polling mode to work with kdb/kgdb

From: Andrew Melnychenko <andrew at daynix.com> If there is a lot(more then 16) of virtio-console devices or virtio_console module is reloaded - buffers 'vtermnos' and 'cons_ops' are overflowed. In older kernels it overruns spinlock which leads to kernel freezing: https://bugzilla.redhat.com/show_bug.cgi?id=1786239 To reproduce the issue, you can try simple script that

From: Andrew Melnychenko <andrew at daynix.com> If there is a lot(more then 16) of virtio-console devices or virtio_console module is reloaded - buffers 'vtermnos' and 'cons_ops' are overflowed. In older kernels it overruns spinlock which leads to kernel freezing: https://bugzilla.redhat.com/show_bug.cgi?id=1786239 Signed-off-by: Andrew Melnychenko <andrew at

(Amit pointed out that the patches never went out. This is a resend of the series meant to go out on 11/2/2011; I've marked it "v2".) This patchset applies to linux-next/next-20111102. This series implements support for multiple virtio_consoles using KVM. This patchset addresses several issues associated with trying to establish multiple virtio consoles. I'm trying to

(Amit pointed out that the patches never went out. This is a resend of the series meant to go out on 11/2/2011; I've marked it "v2".) This patchset applies to linux-next/next-20111102. This series implements support for multiple virtio_consoles using KVM. This patchset addresses several issues associated with trying to establish multiple virtio consoles. I'm trying to

(Amit pointed out that the patches never went out. This was a resend of the series meant to go out on 11/2/2011; Now it's a resend of the mail this morning, with everyone copied on the same mail. So sorry for the spam! This is v3.) This patchset applies to linux-next/next-20111102. This series implements support for multiple virtio_consoles using KVM. This patchset addresses several issues

(Amit pointed out that the patches never went out. This was a resend of the series meant to go out on 11/2/2011; Now it's a resend of the mail this morning, with everyone copied on the same mail. So sorry for the spam! This is v3.) This patchset applies to linux-next/next-20111102. This series implements support for multiple virtio_consoles using KVM. This patchset addresses several issues

(Amit pointed out that the patches never went out. This was a resend of the series meant to go out on 11/2/2011; Now it's a resend of the mail this morning, with everyone copied on the same mail. So sorry for the spam! This is v3.) This patchset applies to linux-next/next-20111102. This series implements support for multiple virtio_consoles using KVM. This patchset addresses several issues

(Amit pointed out that the patches never went out. This is a resend of the series meant to go out on 11/2/2011; I''ve marked it "v2".) This patchset applies to linux-next/next-20111102. This series implements support for multiple virtio_consoles using KVM. This patchset addresses several issues associated with trying to establish multiple virtio consoles. I''m

Hey Rusty, This series adds support for generic ports with each port getting two vqs: one for input and one for output. The host notifies us via the config space of the max. number of ports that can be added for a particular device. As a result of that change, the buffer management for find_readbufs and send_bufs is moved to the vqs. Only one outbuf per port is used so we bide away some time in

Hey Rusty, This series adds support for generic ports with each port getting two vqs: one for input and one for output. The host notifies us via the config space of the max. number of ports that can be added for a particular device. As a result of that change, the buffer management for find_readbufs and send_bufs is moved to the vqs. Only one outbuf per port is used so we bide away some time in

Does anyone happen to know the correct version of kgdb to use for debugging the 2.6.9 kernel? Version 2.4 is apparently for the 2.6.15 kernel, and version 2.2 is for the 2.6.13 kernel, but I've read all the way through the documentation and nowhere does it say which kgdb goes with which kernel. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi ! I reproduced it on the file init/main.c The invocation, log and main.i / main.s is attached. -- Dipl.-Ing. Jan-Simon Möller jansimon.moeller at gmx.de Am Freitag, 16. Mai 2014, 14:25:47 schrieb Renato Golin: > On 16 May 2014 14:01, Jan-Simon Möller <dl9pf at gmx.de> wrote: > > A bisection points to > > > > git-svn-id:

Hi everyone, I''m pleased to announce that a Git mirror repository is now available (and up-to-date). This one contains several branches: * master --> xen-unstable.hg * staging --> staging/xen-unstable.hg * stable-4.0 --> xen-4.0-testing.hg * stable-4.1 --> xen-4.1-testing.hg http://xenbits.xen.org/gitweb/?p=xen.git git://xenbits.xen.org/xen.git Regards, --

Before I get to entrenched in the ACPI code - I thought I''d ping the community to make sure nobody else has investigated this already - Can we present cores vs sockets for guest VCPUs? Right now, the number of total processors can be specified, but can we specify cores per socket? I see this potentially being an hvmloader function, as part of its acpi build code. Could this be

Migrate the last TSC values for more accurate timekeeping during live migration Signed-off-by: Dave Winchell <dwinchell@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Jan, I was given a machine to diagnose a boot problem on xen 4.3, that used to work on 4.2, and have bisected to the following changeset: commit d0d4635d034f202bb401a6efa3ba61530f3854ab Author: Jan Beulich <jbeulich@suse.com> Date: Thu Nov 22 10:47:58 2012 +0100 implement vmap() ... and use it as basis for a proper ioremap() on x86. Signed-off-by: Jan Beulich

Jan (or others), I'm seeing an issue with the EHCI debug port functionality, that I'm wondering whether it is a known limitation of the hardware, or if this is a bug. On a particular system that I had limited debug capabilities in the past (Dell Inspiron 15 i3) I am seeing the debug messages abruptly stop during boot, followed by garbage that looks like an uninitialized serial port:

Intercept guest reads of MSR_IA32_MCG_CAP and limit the number of memory banks reported to one. This prevents us from trying to read status of non-existent banks when migrated to a machine with fewer banks. Signed-off-by: Ben Guthro Signed-off-by: David Lively <dlively@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I'll look. On May 16, 2014 8:01 AM, "Jan-Simon Möller" <dl9pf at gmx.de> wrote: > The unrecognized junk is (path shortened, so don't worry): > > .Ldebug_range: > .file 1 "/src/linux/include/linux" "export.h" > .file 2 "/src/linux/init" "main.c" > .file 3

When in SYS_STATE_suspend, and going through the cpu_disable_scheduler path, save a copy of the current cpu affinity, and mark a flag to restore it later. Later, in the resume process, when enabling nonboot cpus restore these affinities. v2: Fix formatting problems. remove early return in cpu_disable_scheduler() path. v3: Fix remaining errant tab Move restore_vcpu_affinity() to thaw_domains(),