search for: xenbus_comm

drivers/xen/xenbus/xenbus_comms.c uses full memory barriers to communicate with the other side. For guests compiled with CONFIG_SMP, smp_wmb and smp_mb would be sufficient, so mb() and wmb() here are only needed if a non-SMP guest runs on an SMP host. Switch to virt_xxx barriers which serve this exact purpose. Signed-off-by:...

drivers/xen/xenbus/xenbus_comms.c uses full memory barriers to communicate with the other side. For guests compiled with CONFIG_SMP, smp_wmb and smp_mb would be sufficient, so mb() and wmb() here are only needed if a non-SMP guest runs on an SMP host. Switch to __smp_XXX barriers which serve this exact purpose. Signed-off-by:...

upstream commit 7e96287ddc4f42081e18248b6167041c0908004c Author: Vivek Goyal <vgoyal@in.ibm.com> [PATCH] kdump: introduce "reset_devices" command line option Resetting the devices during driver initialization can be a costly operation in terms of time (especially scsi devices). This option can be used by drivers to know that user forcibly wants the devices to

...with virt, so I do not know if there's more > sites outside of virtio that could use this. > Touching all archs is a tad tedious, but its fairly straight forward. So I looked and I was only able to find other another possible user in Xen. Cc Xen folks. I noticed that drivers/xen/xenbus/xenbus_comms.c uses full memory barriers to communicate with the other side. For example: /* Must write data /after/ reading the consumer index. * */ mb(); memcpy(dst, data, avail); data += avail; len -= avail;...

...with virt, so I do not know if there's more > sites outside of virtio that could use this. > Touching all archs is a tad tedious, but its fairly straight forward. So I looked and I was only able to find other another possible user in Xen. Cc Xen folks. I noticed that drivers/xen/xenbus/xenbus_comms.c uses full memory barriers to communicate with the other side. For example: /* Must write data /after/ reading the consumer index. * */ mb(); memcpy(dst, data, avail); data += avail; len -= avail;...

Keir moved barriers, Competence questions are raised: Correctness withers. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r 067b9aacb6c2 linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_comms.c --- a/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_comms.c Wed Oct 12 09:11:35 2005 +++ b/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_comms.c Thu Oct 13 01:18:26 2005 @@ -130,7 +130,7 @@ wait_event_interruptible(xb_waitq, output_avail(out)); - mb(); + /* Make local copy of header t...

On Thu, Dec 17, 2015 at 02:57:26PM +0100, Peter Zijlstra wrote: > On Thu, Dec 17, 2015 at 03:16:20PM +0200, Michael S. Tsirkin wrote: > > On Thu, Dec 17, 2015 at 11:52:38AM +0100, Peter Zijlstra wrote: > > > On Thu, Dec 17, 2015 at 12:32:53PM +0200, Michael S. Tsirkin wrote: > > > > +static inline void virtio_store_mb(bool weak_barriers, > > > > +

On Thu, Dec 17, 2015 at 02:57:26PM +0100, Peter Zijlstra wrote: > On Thu, Dec 17, 2015 at 03:16:20PM +0200, Michael S. Tsirkin wrote: > > On Thu, Dec 17, 2015 at 11:52:38AM +0100, Peter Zijlstra wrote: > > > On Thu, Dec 17, 2015 at 12:32:53PM +0200, Michael S. Tsirkin wrote: > > > > +static inline void virtio_store_mb(bool weak_barriers, > > > > +

...dlock. This patch series is fixing that issue by deferring the xenbus frontend resume when we are running xenstored in that same domain. Aurelien Chartier (2): xenbus: save xenstore local status for later use xenbus: delay xenbus frontend resume if xenstored is not running drivers/xen/xenbus/xenbus_comms.h | 1 + drivers/xen/xenbus/xenbus_probe.c | 27 ++++++++++----------- drivers/xen/xenbus/xenbus_probe.h | 7 ++++++ drivers/xen/xenbus/xenbus_probe_frontend.c | 36 +++++++++++++++++++++++++++- include/xen/xenbus.h | 1 + 5 files chang...

...hat one). This puts xenstore headers in linux-public. Signed-off-by: Chris Wright <chrisw@osdl.org> --- a/linux-2.6-xen-sparse/drivers/xen/xenbus/Makefile Mon Aug 8 18:43:57 2005 +++ b/linux-2.6-xen-sparse/drivers/xen/xenbus/Makefile Mon Aug 8 15:15:06 2005 @@ -4,7 +4,3 @@ xenbus-objs += xenbus_comms.o xenbus-objs += xenbus_xs.o xenbus-objs += xenbus_probe.o - -XEN_TOOLS_DIR := "../tools" -vpath %.h $(XEN_TOOLS_DIR) -EXTRA_CFLAGS += -I $(XEN_TOOLS_DIR) diff -r 0229efe8ffe4 linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_xs.c --- a/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_xs.c...

...include/asm-generic/barrier.h | 102 ++++++++++++++++++++++++++++++++---- include/linux/virtio_ring.h | 22 +++++--- include/xen/interface/io/ring.h | 16 +++--- arch/ia64/kernel/iosapic.c | 6 +-- drivers/virtio/virtio_ring.c | 15 +++--- drivers/xen/xenbus/xenbus_comms.c | 8 +-- Documentation/memory-barriers.txt | 28 ++++++++-- 23 files changed, 266 insertions(+), 279 deletions(-) -- MST

...include/asm-generic/barrier.h | 102 ++++++++++++++++++++++++++++++++---- include/linux/virtio_ring.h | 22 +++++--- include/xen/interface/io/ring.h | 16 +++--- arch/ia64/kernel/iosapic.c | 6 +-- drivers/virtio/virtio_ring.c | 15 +++--- drivers/xen/xenbus/xenbus_comms.c | 8 +-- Documentation/memory-barriers.txt | 28 ++++++++-- 23 files changed, 266 insertions(+), 279 deletions(-) -- MST

...neric/barrier.h | 95 +++++++++++++++++++++++++++++++++---- include/linux/virtio_ring.h | 48 ++++++++++++++++--- include/xen/interface/io/ring.h | 16 +++---- arch/ia64/kernel/iosapic.c | 6 +-- drivers/virtio/virtio_ring.c | 35 +++++++------- drivers/xen/xenbus/xenbus_comms.c | 8 ++-- Documentation/memory-barriers.txt | 33 +++++++++++-- 23 files changed, 292 insertions(+), 289 deletions(-) -- MST

...neric/barrier.h | 95 +++++++++++++++++++++++++++++++++---- include/linux/virtio_ring.h | 48 ++++++++++++++++--- include/xen/interface/io/ring.h | 16 +++---- arch/ia64/kernel/iosapic.c | 6 +-- drivers/virtio/virtio_ring.c | 35 +++++++------- drivers/xen/xenbus/xenbus_comms.c | 8 ++-- Documentation/memory-barriers.txt | 33 +++++++++++-- 23 files changed, 292 insertions(+), 289 deletions(-) -- MST

...irtio_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 100644 arch/sh/include/asm/cmpxchg-xchg.h

...irtio_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 100644 arch/sh/include/asm/cmpxchg-xchg.h

On 20/12/15 09:25, Michael S. Tsirkin wrote: > > I noticed that drivers/xen/xenbus/xenbus_comms.c uses > full memory barriers to communicate with the other side. > For example: > > /* Must write data /after/ reading the consumer index. * */ > mb(); > > memcpy(dst, data, avail); > data += avail; >...

Hi, since the printk_ratelimit() function shouldn't be used anymore, I replaced it in a few files with printk_ratelimited(). If you wish some more patches I can send more in. Greets, Manu Manuel Zerpies (11): drivers/ide: use printk_ratelimited() instead of printk_ratelimit() drivers/tty: use printk_ratelimited() instead of printk_ratelimit() net/can: use printk_ratelimited() instead

Hi, since the printk_ratelimit() function shouldn't be used anymore, I replaced it in a few files with printk_ratelimited(). If you wish some more patches I can send more in. Greets, Manu Manuel Zerpies (11): drivers/ide: use printk_ratelimited() instead of printk_ratelimit() drivers/tty: use printk_ratelimited() instead of printk_ratelimit() net/can: use printk_ratelimited() instead

Hi, since the printk_ratelimit() function shouldn't be used anymore, I replaced it in a few files with printk_ratelimited(). If you wish some more patches I can send more in. Greets, Manu Manuel Zerpies (11): drivers/ide: use printk_ratelimited() instead of printk_ratelimit() drivers/tty: use printk_ratelimited() instead of printk_ratelimit() net/can: use printk_ratelimited() instead