On 03/19/2015 08:25 AM, Peter Zijlstra wrote:
On Thu, Mar 19, 2015 at 11:12:42AM +0100, Peter Zijlstra wrote:
So I was now thinking of hashing the lock pointer; let me go and quickly
put something together.
A little something like so; ideally we'd allocate the hashtable since
NR_CPUS is kinda
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and forwarding
incoming events to the linux input layer.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/virtio/Kconfig| 10 ++
Hi,
This patch adds a virtio driver for input devices.
Specification:
https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input
https://www.kraxel.org/virtio/virtio-v1.0-csprd03-virtio-input.html#x1-2640007
Qemu patches;
On Wed, Mar 18, 2015 at 10:45:55PM -0400, Waiman Long wrote:
On 03/16/2015 09:16 AM, Peter Zijlstra wrote:
I do have some concern about this call site patching mechanism as the
modification is not atomic. The spin_unlock() calls are in many places in
the kernel. There is a possibility that a
On 19/03/2015 17:33, Michael S. Tsirkin wrote:
On Thu, Mar 19, 2015 at 03:46:44PM +0100, Gerd Hoffmann wrote:
Latest. As far I know there never ever have been incompatible changes
to the interface, and given this is userspace/kernel abi I don't expect
that to happen in the future.
More
On Thu, Mar 19, 2015 at 01:25:36PM +0100, Peter Zijlstra wrote:
+static struct qspinlock **pv_hash(struct qspinlock *lock)
+{
+ u32 hash = hash_ptr(lock, PV_LOCK_HASH_BITS);
+ struct pv_hash_bucket *hb, *end;
+
+ if (!hash)
+ hash = 1;
+
+ hb =
On Thu, Mar 19, 2015 at 10:13:10AM +0100, Gerd Hoffmann wrote:
Hi,
This patch adds a virtio driver for input devices.
Specification:
https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input
https://www.kraxel.org/virtio/virtio-v1.0-csprd03-virtio-input.html#x1-2640007
OK, I
On Thu, Mar 19, 2015 at 06:01:34PM +, David Vrabel wrote:
This seems work for me, but I've not got time to give it a more thorough
testing.
You can fold this into your series.
Thanks!
There doesn't seem to be a way to disable QUEUE_SPINLOCKS when supported by
the arch, is this
On Do, 2015-03-19 at 14:35 +0100, Michael S. Tsirkin wrote:
On Thu, Mar 19, 2015 at 10:13:10AM +0100, Gerd Hoffmann wrote:
Hi,
This patch adds a virtio driver for input devices.
Specification:
https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input
pci core now disables msi on probe automatically,
drop this from device-specific code.
Cc: Bjorn Helgaas bhelg...@google.com
Cc: linux-...@vger.kernel.org
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/virtio/virtio_pci_common.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
On 03/19/2015 06:01 AM, Peter Zijlstra wrote:
On Wed, Mar 18, 2015 at 10:45:55PM -0400, Waiman Long wrote:
On 03/16/2015 09:16 AM, Peter Zijlstra wrote:
I do have some concern about this call site patching mechanism as the
modification is not atomic. The spin_unlock() calls are in many places
On Thu, Mar 19, 2015 at 01:29:49PM +0100, David Herrmann wrote:
Hi
(CC: Dmitry)
On Thu, Mar 19, 2015 at 10:13 AM, Gerd Hoffmann kra...@redhat.com wrote:
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and
Hi
(CC: Dmitry)
On Thu, Mar 19, 2015 at 10:13 AM, Gerd Hoffmann kra...@redhat.com wrote:
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and forwarding
incoming events to the linux input layer.
Signed-off-by:
On Thu, Mar 19, 2015 at 03:46:44PM +0100, Gerd Hoffmann wrote:
On Do, 2015-03-19 at 14:35 +0100, Michael S. Tsirkin wrote:
On Thu, Mar 19, 2015 at 10:13:10AM +0100, Gerd Hoffmann wrote:
Hi,
This patch adds a virtio driver for input devices.
Specification:
14 matches
Mail list logo