search for: events_fifo

drivers/xen/events/events_fifo.c uses rmb() to communicate with the other side. For guests compiled with CONFIG_SMP, smp_rmb would be sufficient, so rmb() here is only needed if a non-SMP guest runs on an SMP host. Switch to the virt_rmb barrier which serves this exact purpose. Pull in asm/barrier.h here to make sure the file...

...irtio_balloon.c | 4 +- drivers/virtio/virtio_input.c | 2 +- drivers/virtio/virtio_mmio.c | 2 +- drivers/virtio/virtio_pci_common.c | 4 +- drivers/virtio/virtio_pci_modern.c | 2 +- drivers/virtio/virtio_ring.c | 15 +++-- drivers/xen/events/events_fifo.c | 3 +- drivers/xen/xenbus/xenbus_comms.c | 8 +-- mm/balloon_compaction.c | 4 +- Documentation/memory-barriers.txt | 28 +++++++-- scripts/checkpatch.pl | 33 +++++++++- 44 files changed, 401 insertions(+), 319 deletions(-) create mode 10...

...irtio_balloon.c | 4 +- drivers/virtio/virtio_input.c | 2 +- drivers/virtio/virtio_mmio.c | 2 +- drivers/virtio/virtio_pci_common.c | 4 +- drivers/virtio/virtio_pci_modern.c | 2 +- drivers/virtio/virtio_ring.c | 15 +++-- drivers/xen/events/events_fifo.c | 3 +- drivers/xen/xenbus/xenbus_comms.c | 8 +-- mm/balloon_compaction.c | 4 +- Documentation/memory-barriers.txt | 28 +++++++-- scripts/checkpatch.pl | 33 +++++++++- 44 files changed, 401 insertions(+), 319 deletions(-) create mode 10...

...- > drivers/virtio/virtio_input.c | 2 +- > drivers/virtio/virtio_mmio.c | 2 +- > drivers/virtio/virtio_pci_common.c | 4 +- > drivers/virtio/virtio_pci_modern.c | 2 +- > drivers/virtio/virtio_ring.c | 15 +++-- > drivers/xen/events/events_fifo.c | 3 +- > drivers/xen/xenbus/xenbus_comms.c | 8 +-- > mm/balloon_compaction.c | 4 +- > Documentation/memory-barriers.txt | 28 +++++++-- > scripts/checkpatch.pl | 33 +++++++++- > 44 files changed, 401 insertions(+), 319 del...

...+- include/asm-generic/barrier.h | 106 +++++++++++++++++++++++++++++++++--- include/linux/virtio_ring.h | 21 +++++-- include/xen/interface/io/ring.h | 16 +++--- arch/ia64/kernel/iosapic.c | 6 +- drivers/virtio/virtio_ring.c | 15 +++-- drivers/xen/events/events_fifo.c | 3 +- drivers/xen/xenbus/xenbus_comms.c | 8 +-- Documentation/memory-barriers.txt | 28 ++++++++-- scripts/checkpatch.pl | 31 ++++++++++- 30 files changed, 382 insertions(+), 302 deletions(-) create mode 100644 arch/sh/include/asm/cmpxchg-xchg.h -- MST

...+- include/asm-generic/barrier.h | 106 +++++++++++++++++++++++++++++++++--- include/linux/virtio_ring.h | 21 +++++-- include/xen/interface/io/ring.h | 16 +++--- arch/ia64/kernel/iosapic.c | 6 +- drivers/virtio/virtio_ring.c | 15 +++-- drivers/xen/events/events_fifo.c | 3 +- drivers/xen/xenbus/xenbus_comms.c | 8 +-- Documentation/memory-barriers.txt | 28 ++++++++-- scripts/checkpatch.pl | 31 ++++++++++- 30 files changed, 382 insertions(+), 302 deletions(-) create mode 100644 arch/sh/include/asm/cmpxchg-xchg.h -- MST

Changes since v1: - replaced my asm-generic patch with an equivalent patch already in tip - add wrappers with virt_ prefix for better code annotation, as suggested by David Miller - dropped XXX in patch names as this makes vger choke, Cc all relevant mailing lists on all patches (not personal email, as the list becomes too long then) I parked this in vhost tree for now, but the

Changes since v1: - replaced my asm-generic patch with an equivalent patch already in tip - add wrappers with virt_ prefix for better code annotation, as suggested by David Miller - dropped XXX in patch names as this makes vger choke, Cc all relevant mailing lists on all patches (not personal email, as the list becomes too long then) I parked this in vhost tree for now, but the

This is really trying to cleanup some virt code, as suggested by Peter, who said > You could of course go fix that instead of mutilating things into > sort-of functional state. This work is needed for virtio, so it's probably easiest to merge it through my tree - is this fine by everyone? Arnd, if you agree, could you ack this please? Note to arch maintainers: please don't

This is really trying to cleanup some virt code, as suggested by Peter, who said > You could of course go fix that instead of mutilating things into > sort-of functional state. This work is needed for virtio, so it's probably easiest to merge it through my tree - is this fine by everyone? Arnd, if you agree, could you ack this please? Note to arch maintainers: please don't