search for: bitmap_copy

...u.bitmap[bit/8], &cfg); coding style violations above. you need spaces around ops like / and *. Please run checkpatch.pl > + if (cfg & (1 << (bit % 8))) > + set_bit(bit, bits); what if not set? does something clear the mask? > + } doesn't above just implement bitmap_copy or bitmap_or? Will it hurt to just do virtio_cread_bytes into a temporary buffer and then invoke bitmap ops? Looks like the buffer is at most 256 bytes: too large to be on stack, but you can allocate it at probe time. > +} > + > +static void virtinput_cfg_abs(struct virtio_input *vi, in...

...u.bitmap[bit/8], &cfg); coding style violations above. you need spaces around ops like / and *. Please run checkpatch.pl > + if (cfg & (1 << (bit % 8))) > + set_bit(bit, bits); what if not set? does something clear the mask? > + } doesn't above just implement bitmap_copy or bitmap_or? Will it hurt to just do virtio_cread_bytes into a temporary buffer and then invoke bitmap ops? Looks like the buffer is at most 256 bytes: too large to be on stack, but you can allocate it at probe time. > +} > + > +static void virtinput_cfg_abs(struct virtio_input *vi, in...

...ns above. you need spaces around ops like / and *. > Please run checkpatch.pl > > > + if (cfg & (1 << (bit % 8))) > > + set_bit(bit, bits); > > what if not set? does something clear the mask? kzalloc? > > + } > > doesn't above just implement bitmap_copy or bitmap_or? Not fully sure how bitmaps are defined. virtio has a stream of bytes, first byte carries bits 0-7, second 8-15 etc. linux kernel bitmaps ops are operating on longs, and native byteorder longs would be something else ... > > + size = virtinput_cfg_select(vi, VIRTIO_INPUT_CFG_...

...ns above. you need spaces around ops like / and *. > Please run checkpatch.pl > > > + if (cfg & (1 << (bit % 8))) > > + set_bit(bit, bits); > > what if not set? does something clear the mask? kzalloc? > > + } > > doesn't above just implement bitmap_copy or bitmap_or? Not fully sure how bitmaps are defined. virtio has a stream of bytes, first byte carries bits 0-7, second 8-15 etc. linux kernel bitmaps ops are operating on longs, and native byteorder longs would be something else ... > > + size = virtinput_cfg_select(vi, VIRTIO_INPUT_CFG_...

...+ set_bit(bit, bits); > > > > what if not set? does something clear the mask? > > kzalloc? So you are really just reading in array of bytes? All this set bit trickery is just to convert things from LE? > > > + } > > > > doesn't above just implement bitmap_copy or bitmap_or? > > Not fully sure how bitmaps are defined. virtio has a stream of bytes, > first byte carries bits 0-7, second 8-15 etc. linux kernel bitmaps ops > are operating on longs, and native byteorder longs would be something > else ... This still looks too complex. At lea...

...+ set_bit(bit, bits); > > > > what if not set? does something clear the mask? > > kzalloc? So you are really just reading in array of bytes? All this set bit trickery is just to convert things from LE? > > > + } > > > > doesn't above just implement bitmap_copy or bitmap_or? > > Not fully sure how bitmaps are defined. virtio has a stream of bytes, > first byte carries bits 0-7, second 8-15 etc. linux kernel bitmaps ops > are operating on longs, and native byteorder longs would be something > else ... This still looks too complex. At lea...

...mi_known_vm_events); + + bitmap_zero(Kvmi_known_vcpu_events, KVMI_NUM_EVENTS); + + bitmap_or(Kvmi_known_events, Kvmi_known_vm_events, + Kvmi_known_vcpu_events, KVMI_NUM_EVENTS); } int kvmi_init(void) @@ -121,6 +129,8 @@ alloc_kvmi(struct kvm *kvm, const struct kvm_introspection_hook *hook) bitmap_copy(kvmi->cmd_allow_mask, Kvmi_always_allowed_commands, KVMI_NUM_COMMANDS); + atomic_set(&kvmi->ev_seq, 0); + kvmi->kvm = kvm; return kvmi; @@ -377,3 +387,33 @@ int kvmi_ioctl_command(struct kvm *kvm, mutex_unlock(&kvm->kvmi_lock); return err; } + +static bool kv...

...sr/include/linux/bitmap.h:110: error: `BITS_PER_LONG' undeclared (first use in this function) /usr/include/linux/bitmap.h: In function `bitmap_fill': /usr/include/linux/bitmap.h:125: error: `BITS_PER_LONG' undeclared (first use in this function) /usr/include/linux/bitmap.h: In function `bitmap_copy': /usr/include/linux/bitmap.h:131: error: `BITS_PER_LONG' undeclared (first use in this function) /usr/include/linux/bitmap.h: In function `bitmap_and': /usr/include/linux/bitmap.h:142: error: `BITS_PER_LONG' undeclared (first use in this function) /usr/include/linux/bitmap.h: In fu...

...Global data */ extern bitmap_element bitmap_zero_bits; /* Zero bitmap element */ extern bitmap_obstack bitmap_default_obstack; /* Default bitmap obstack */ /* Clear a bitmap by freeing up the linked list. */ extern void bitmap_clear (bitmap); /* Copy a bitmap to another bitmap. */ extern void bitmap_copy (bitmap, bitmap); /* True if two bitmaps are identical. */ extern bool bitmap_equal_p (bitmap, bitmap); /* True if the bitmaps intersect (their AND is non-empty). */ extern bool bitmap_intersect_p (bitmap, bitmap); /* True if the complement of the second intersects the first (their AND_COMP...

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; https://lists.gnu.org/archive/html/qemu-devel/2015-03/threads.html#03973 Gerd Hoffmann (1): Add virtio-input driver. 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; https://lists.gnu.org/archive/html/qemu-devel/2015-03/threads.html#03973 Gerd Hoffmann (1): Add virtio-input driver. drivers/virtio/Kconfig | 10 ++

The KVM introspection subsystem provides a facility for applications running on the host or in a separate VM, to control the execution of other VMs (pause, resume, shutdown), query the state of the vCPUs (GPRs, MSRs etc.), alter the page access bits in the shadow page tables (only for the hardware backed ones, eg. Intel's EPT) and receive notifications when events of interest have taken place