search for: __refdata

...ister_pirq and xen_unplug_emulated_devices functions. xen_register_pirq makes reference to acpi_sci_override_gsi in init.data section; marking xen_register_pirq with __init is not feasible since calls are made to it from acpi_register_gsi in non-init contexts. So marking it __refdata based on assumption that when acpi_sci_override_gsi is referenced, it is in early stages where it is alive. -------------------------- Raghavendra Prabhu GPG Id : 0xD72BE977 Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977 www: wnohang.net -------------- next part ------------...

...ister_pirq and xen_unplug_emulated_devices functions. xen_register_pirq makes reference to acpi_sci_override_gsi in init.data section; marking xen_register_pirq with __init is not feasible since calls are made to it from acpi_register_gsi in non-init contexts. So marking it __refdata based on assumption that when acpi_sci_override_gsi is referenced, it is in early stages where it is alive. -------------------------- Raghavendra Prabhu GPG Id : 0xD72BE977 Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977 www: wnohang.net -------------- next part ------------...

...ister_pirq and xen_unplug_emulated_devices functions. xen_register_pirq makes reference to acpi_sci_override_gsi in init.data section; marking xen_register_pirq with __init is not feasible since calls are made to it from acpi_register_gsi in non-init contexts. So marking it __refdata based on assumption that when acpi_sci_override_gsi is referenced, it is in early stages where it is alive. -------------------------- Raghavendra Prabhu GPG Id : 0xD72BE977 Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977 www: wnohang.net -------------- next part ------------...

...d on device removal, I think, otherwise the vdev pointer will go stale. > +} > + > + Two empty lines :) > static int __devinit virtblk_probe(struct virtio_device *vdev) > { > struct virtio_blk *vblk; > @@ -508,27 +566,47 @@ static unsigned int features[] = { > * Use __refdata to avoid this warning. > */ > static struct virtio_driver __refdata virtio_blk = { > - .feature_table = features, > - .feature_table_size = ARRAY_SIZE(features), > - .driver.name = KBUILD_MODNAME, > - .driver.owner = THIS_MODULE, > - .id_table = id_table, > - .probe = vir...

...d on device removal, I think, otherwise the vdev pointer will go stale. > +} > + > + Two empty lines :) > static int __devinit virtblk_probe(struct virtio_device *vdev) > { > struct virtio_blk *vblk; > @@ -508,27 +566,47 @@ static unsigned int features[] = { > * Use __refdata to avoid this warning. > */ > static struct virtio_driver __refdata virtio_blk = { > - .feature_table = features, > - .feature_table_size = ARRAY_SIZE(features), > - .driver.name = KBUILD_MODNAME, > - .driver.owner = THIS_MODULE, > - .id_table = id_table, > - .probe = vir...

...oc_serial_features[] = { +}; + #ifdef CONFIG_PM static int virtcons_freeze(struct virtio_device *vdev) { @@ -1922,6 +2018,20 @@ static struct virtio_driver virtio_console = { #endif }; +/* + * virtio_rproc_serial refers to __devinit function which causes + * section mismatch warnings. So use __refdata to silence warnings. + */ +static struct virtio_driver __refdata virtio_rproc_serial = { + .feature_table = rproc_serial_features, + .feature_table_size = ARRAY_SIZE(rproc_serial_features), + .driver.name = "virtio_rproc_serial", + .driver.owner = THIS_MODULE, + .id_table = rproc_serial_i...

...oc_serial_features[] = { +}; + #ifdef CONFIG_PM static int virtcons_freeze(struct virtio_device *vdev) { @@ -1922,6 +2018,20 @@ static struct virtio_driver virtio_console = { #endif }; +/* + * virtio_rproc_serial refers to __devinit function which causes + * section mismatch warnings. So use __refdata to silence warnings. + */ +static struct virtio_driver __refdata virtio_rproc_serial = { + .feature_table = rproc_serial_features, + .feature_table_size = ARRAY_SIZE(rproc_serial_features), + .driver.name = "virtio_rproc_serial", + .driver.owner = THIS_MODULE, + .id_table = rproc_serial_i...

...issues which the LLVMLinux project is attempting to fix in the Linux > Kernel code base and pushed upstream: > > * The use of variable length arrays in structs (VLAIS) > * Kbuild support for Clang (currently Kbuild is gcc specific) > * Use of explicit register variables > * Extra __refdata annotations needed to overcome segment reference errors > * EXPORT_SYMBOL of inline functions > > However, there are some things in Clang/LLVM which also need to be > addressed in order to make a Clang compiled Linux Kernel possible. > Amongst other things these are: > > * The...

...oc_serial_features[] = { +}; + #ifdef CONFIG_PM static int virtcons_freeze(struct virtio_device *vdev) { @@ -1922,6 +2061,20 @@ static struct virtio_driver virtio_console = { #endif }; +/* + * virtio_rproc_serial refers to __devinit function which causes + * section mismatch warnings. So use __refdata to silence warnings. + */ +static struct virtio_driver __refdata virtio_rproc_serial = { + .feature_table = rproc_serial_features, + .feature_table_size = ARRAY_SIZE(rproc_serial_features), + .driver.name = "virtio_rproc_serial", + .driver.owner = THIS_MODULE, + .id_table = rproc_serial_i...

...oc_serial_features[] = { +}; + #ifdef CONFIG_PM static int virtcons_freeze(struct virtio_device *vdev) { @@ -1922,6 +2061,20 @@ static struct virtio_driver virtio_console = { #endif }; +/* + * virtio_rproc_serial refers to __devinit function which causes + * section mismatch warnings. So use __refdata to silence warnings. + */ +static struct virtio_driver __refdata virtio_rproc_serial = { + .feature_table = rproc_serial_features, + .feature_table_size = ARRAY_SIZE(rproc_serial_features), + .driver.name = "virtio_rproc_serial", + .driver.owner = THIS_MODULE, + .id_table = rproc_serial_i...

...tio_blk *vblk; struct request_queue *q; @@ -963,7 +963,7 @@ static unsigned int features[] = { /* * virtio_blk causes spurious section mismatch warning by - * simultaneously referring to a __devinit and a __devexit function. + * simultaneously referring to a and a __devexit function. * Use __refdata to avoid this warning. */ static struct virtio_driver __refdata virtio_blk = { diff --git a/drivers/block/xsysace.c b/drivers/block/xsysace.c index d925121..cc49230 100644 --- a/drivers/block/xsysace.c +++ b/drivers/block/xsysace.c @@ -961,7 +961,7 @@ static const struct block_device_operations...

...tio_blk *vblk; struct request_queue *q; @@ -963,7 +963,7 @@ static unsigned int features[] = { /* * virtio_blk causes spurious section mismatch warning by - * simultaneously referring to a __devinit and a __devexit function. + * simultaneously referring to a and a __devexit function. * Use __refdata to avoid this warning. */ static struct virtio_driver __refdata virtio_blk = { diff --git a/drivers/block/xsysace.c b/drivers/block/xsysace.c index d925121..cc49230 100644 --- a/drivers/block/xsysace.c +++ b/drivers/block/xsysace.c @@ -961,7 +961,7 @@ static const struct block_device_operations...

...piled with Clang; these are issues which the LLVMLinux project is attempting to fix in the Linux Kernel code base and pushed upstream: * The use of variable length arrays in structs (VLAIS) * Kbuild support for Clang (currently Kbuild is gcc specific) * Use of explicit register variables * Extra __refdata annotations needed to overcome segment reference errors * EXPORT_SYMBOL of inline functions However, there are some things in Clang/LLVM which also need to be addressed in order to make a Clang compiled Linux Kernel possible. Amongst other things these are: * The Linux kernel currently uses com...

This patch-set introduces a new virtio type "rproc_serial" for communicating with remote processors over shared memory. The driver depends on the the remoteproc framework. As preparation for introducing "rproc_serial" I've done a refactoring of the transmit buffer handling. NOTE: These two patches are identical to first two patches of the V8 patch-set, but are rebased to

This patch-set introduces a new virtio type "rproc_serial" for communicating with remote processors over shared memory. The driver depends on the the remoteproc framework. As preparation for introducing "rproc_serial" I've done a refactoring of the transmit buffer handling. NOTE: These two patches are identical to first two patches of the V8 patch-set, but are rebased to

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces a new virtio type "rproc_serial" for communicating with remote processors over shared memory. The driver depends on the the remoteproc framework. As preparation for introducing "rproc_serial" I've done a refactoring of the transmit buffer handling. Changes since v7: - Rebased to

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces a new virtio type "rproc_serial" for communicating with remote processors over shared memory. The driver depends on the the remoteproc framework. As preparation for introducing "rproc_serial" I've done a refactoring of the transmit buffer handling. Changes since v7: - Rebased to

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> I thought rebasing rproc_serial to linux-next was going to be trivial. But when starting the merge I realized that I had to refactor the the patches from Masami Hiramatsu. The splice support has the same issue as I faced, with different type of buffers in the out_vq. So I ended up refactoring the splice functionality. The code size

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> I thought rebasing rproc_serial to linux-next was going to be trivial. But when starting the merge I realized that I had to refactor the the patches from Masami Hiramatsu. The splice support has the same issue as I faced, with different type of buffers in the out_vq. So I ended up refactoring the splice functionality. The code size

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces a new virtio type "rproc_serial" for communicating with remote processors over shared memory. The driver depends on the the remoteproc framework. As preparation for introducing "rproc_serial" I've done a refactoring of the transmit buffer handling. This patch-set is a rework of the