search for: ovq

...ts, I've become intrigued by the problem of spherical quantizers, so I decided to see if I could come up with something better than PVQ. What I wound up writing is something I call an "octagon quantizer. In two dimensions, PVQ uses a "diamond" (square) shape. An octagon code (OVQ) uses an octagon, which is a much better approximation to the circle. In two dimensions, PVQ uses an octahedron, and OVQ uses a rhombicuboctahedron, which is (again) a much better approximation to the sphere. In OVQ, the resolution parameter K is replaced by two (int) parameters A and B. Quantiz...

The in-vq operations were protected by a lock, but the out-vq operations were not. This caused panics / errors as described in patch 2. Fix that. The first patch renames the existing cvq_lock to c_ivq_lock to match c_ivq. The second patch introduces the c_ovq_lock for the c_ovq. Please apply. I also believe this is a candidate for stable. Amit Shah (2): virtio: console: rename cvq_lock to c_ivq_lock virtio: console: add locking around c_ovq operations drivers/char/virtio_console.c | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+),...

The in-vq operations were protected by a lock, but the out-vq operations were not. This caused panics / errors as described in patch 2. Fix that. The first patch renames the existing cvq_lock to c_ivq_lock to match c_ivq. The second patch introduces the c_ovq_lock for the c_ovq. Please apply. I also believe this is a candidate for stable. Amit Shah (2): virtio: console: rename cvq_lock to c_ivq_lock virtio: console: add locking around c_ovq operations drivers/char/virtio_console.c | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+),...

The in-vq operations were protected by a lock, but the out-vq operations were not. This caused panics / errors as described in patch 2. Fix that. The first patch renames the existing cvq_lock to c_ivq_lock to match c_ivq. The second patch introduces the c_ovq_lock for the c_ovq. Please apply. I also believe this is a candidate for stable. v2: * Use spin_lock instead of spin_lock_irq. Pointed out by Wanlong Gao. Amit Shah (2): virtio: console: rename cvq_lock to c_ivq_lock virtio: console: add locking around c_ovq operations drivers/char/vir...

The in-vq operations were protected by a lock, but the out-vq operations were not. This caused panics / errors as described in patch 2. Fix that. The first patch renames the existing cvq_lock to c_ivq_lock to match c_ivq. The second patch introduces the c_ovq_lock for the c_ovq. Please apply. I also believe this is a candidate for stable. v2: * Use spin_lock instead of spin_lock_irq. Pointed out by Wanlong Gao. Amit Shah (2): virtio: console: rename cvq_lock to c_ivq_lock virtio: console: add locking around c_ovq operations drivers/char/vir...

...n1xSRrUXx?xI5<x^_o`gs-Zudx5-<p`NU zS!yMb%3eWizVF<R!|<dKHm#sr%eXv$+XuN>W3lSEeLm1`1 at NcPSs=ZV&3aGCVhvKl zS^W$NC7zw=7`v=IuT=loVR%0o at eseQs?s2JR=d31rhLPb8A%CZ7D^*1Ud*Eu4{dwJ z%KPn>Z3{Y!BUX4kw4X(n0ycm<jJGW9r54mkPLY?IZpi|V at lQ$d4~mt4PxaSWoKC+< zNnziZR~)2lNsiB}n!r-$)f#`Rx~oVq{~rD)>Wku=0&n!iSYfZ5oa`B4RP at KAL0@mn zJ$KmUBY~i3Eyz{Kz6f6Qz1w?h_IHt1xFL9vNN8#1Xls5hbz|E&9ZI6wSj1r at lG=Cb z=U*fWlyTLyRk>fU0oMYvp8}5 at HQx_yqdD5)@qEPMaURFqrLAWir2)>7Ilcwi7?6d? z_|fI5PKHO}(|V_3*2`$=CM1EOx}ck_`-)^yj#OUxtA$wVVw864rkWS*m$q8vB_@@U z$WWU($nihvdCq6|3I#PBzn7ofci!!%SOFv0T...

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. The code has been updated to reuse the virtio-console device instead of creating a new virtio-serial device. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. There are a few items on my

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. The code has been updated to reuse the virtio-console device instead of creating a new virtio-serial device. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. There are a few items on my

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *