search for: borntr

...owing architectures to define their own > implementation of the 'READ_ONCE()' macro, move the generic > '{READ,WRITE}_ONCE()' definitions out of the unwieldy 'linux/compiler.h' > and into a new 'rwonce.h' header under 'asm-generic'. Adding Christian Borntr?ger to Cc, he originally added the READ_ONCE()/WRITE_ONCE() code. I wonder if it would be appropriate now to revert back to a much simpler version of these helpers for any modern compiler. As I understand, only gcc-4.6 and gcc4.7 actually need the song-and-dance version with the union and switch/c...

...owing architectures to define their own > implementation of the 'READ_ONCE()' macro, move the generic > '{READ,WRITE}_ONCE()' definitions out of the unwieldy 'linux/compiler.h' > and into a new 'rwonce.h' header under 'asm-generic'. Adding Christian Borntr?ger to Cc, he originally added the READ_ONCE()/WRITE_ONCE() code. I wonder if it would be appropriate now to revert back to a much simpler version of these helpers for any modern compiler. As I understand, only gcc-4.6 and gcc4.7 actually need the song-and-dance version with the union and switch/c...

On Mon, Nov 11, 2019 at 9:10 AM Christian Borntraeger <borntraeger at de.ibm.com> wrote: > On 08.11.19 20:57, Arnd Bergmann wrote: > > On Fri, Nov 8, 2019 at 6:01 PM Will Deacon <will at kernel.org> wrote: > >> > >> In preparation for allowing architectures to define their own > >> implementation of...

...define their own >> implementation of the 'READ_ONCE()' macro, move the generic >> '{READ,WRITE}_ONCE()' definitions out of the unwieldy 'linux/compiler.h' >> and into a new 'rwonce.h' header under 'asm-generic'. > > Adding Christian Borntr?ger to Cc, he originally added the > READ_ONCE()/WRITE_ONCE() > code. > > I wonder if it would be appropriate now to revert back to a much simpler version > of these helpers for any modern compiler. As I understand, only gcc-4.6 and > gcc4.7 actually need the song-and-dance versi...

...g /sbin/hotplug as a bash script takes far longer than the interval between hotplug events. Attaching more than 300 devices at once will cause an out-of-memory condition and the kernel starts killing random processes. Running only udev instead of hotplug from the kernel is fast enough. Christian Borntr?ger was so kind to reimplement the Gregs hotplug shell script in C and verify that this solves the problem. The shell version currently does: > DIR="/etc/hotplug.d" > for I in "${DIR}/$1/"*.hotplug "${DIR}/"default/*.hotplug ; do > if [ -f $I ]; then...

Hello Rusty, this is a result of a two month internship about virtio testing. From: Adrian Schneider <adrian.schneider at de.ibm.com> From: Tim Hofmann <tim.hofmann at de.ibm.com> From: Christian Ehrhardt <ehrhardt at de.ibm.com> From: Christian Borntraeger <borntraeger at de.ibm.com> This patch introduces a prototype for a virtio_test module. This module can be bound to any virtio device via sysfs bind/unbind feature, e.g: $ echo virtio1 > /sys/bus/virtio/drivers/virtio_rng/unbind $ modprobe virtio_test On probe this module registers...

Hello Rusty, this is a result of a two month internship about virtio testing. From: Adrian Schneider <adrian.schneider at de.ibm.com> From: Tim Hofmann <tim.hofmann at de.ibm.com> From: Christian Ehrhardt <ehrhardt at de.ibm.com> From: Christian Borntraeger <borntraeger at de.ibm.com> This patch introduces a prototype for a virtio_test module. This module can be bound to any virtio device via sysfs bind/unbind feature, e.g: $ echo virtio1 > /sys/bus/virtio/drivers/virtio_rng/unbind $ modprobe virtio_test On probe this module registers...

Hi all, Although [smp_]read_barrier_depends() became part of READ_ONCE() in commit 76ebbe78f739 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()"), it still limps on in the Linux memory model with the sinister hope of attracting innocent new users so that it becomes impossible to remove altogether. Let's strike before it's too late: there's only