Re: [Qemu-devel] [RFC PATCH] spapr-vty: workaround "reg" property for old kernels

2013-10-15 Thread Anthony Liguori
On Tue, Oct 15, 2013 at 3:47 PM, Alexey Kardashevskiy wrote: > On 10/16/2013 02:03 AM, Alexander Graf wrote: >> On 10/15/2013 10:50 AM, Alexey Kardashevskiy wrote: >>> Old kernels (< 3.1) handle hvcX devices different in different parts. >>> Sometime the kernel assumes that the hvc device numbers

Re: [Qemu-devel] [RFC PATCH] spapr-vty: workaround "reg" property for old kernels

2013-10-15 Thread Alexey Kardashevskiy
On 10/16/2013 02:03 AM, Alexander Graf wrote: > On 10/15/2013 10:50 AM, Alexey Kardashevskiy wrote: >> Old kernels (< 3.1) handle hvcX devices different in different parts. >> Sometime the kernel assumes that the hvc device numbers start from zero >> and if there is just one hvc, then it is hvc0.

Re: [Qemu-devel] [RFC PATCH] spapr-vty: workaround "reg" property for old kernels

2013-10-15 Thread Alexander Graf
On 10/15/2013 10:50 AM, Alexey Kardashevskiy wrote: Old kernels (< 3.1) handle hvcX devices different in different parts. Sometime the kernel assumes that the hvc device numbers start from zero and if there is just one hvc, then it is hvc0. However kernel's add_preferred_console() uses the very

[Qemu-devel] [RFC PATCH] spapr-vty: workaround "reg" property for old kernels

2013-10-15 Thread Alexey Kardashevskiy
Old kernels (< 3.1) handle hvcX devices different in different parts. Sometime the kernel assumes that the hvc device numbers start from zero and if there is just one hvc, then it is hvc0. However kernel's add_preferred_console() uses the very last byte of the VTY's "reg" property as an hvc number