search for: __initcall

__initcall is for things which are always built into the kernel. Kconfig says netfront is tristate (although without a module_exit, the module won''t be unloadable). Trivial fix, Rusty. --- linux-2.6.10-xen-sparse/drivers/xen/netfront/netfront.c.~1~ 2005-01-11 15:35:59.000000000 +1100 +++ linux-2.6....

...y *d; + initrd_blob.data = (char *)initrd_start; + initrd_blob.size = initrd_end - initrd_start; + + if (!do_retain_initrd) + return 0; + + if (!initrd_start) + return 0; + + d = debugfs_create_blob("initrd", S_IFREG, NULL, &initrd_blob); + + if (!d) + return 1; + + return 0; +} + +__initcall(export_initrd); +#endif

...id) diff --git a/arch/x86/vdso/vdso32-setup.c b/arch/x86/vdso/vdso32-setup.c index 02b442e..36df991 100644 --- a/arch/x86/vdso/vdso32-setup.c +++ b/arch/x86/vdso/vdso32-setup.c @@ -374,7 +374,7 @@ int arch_setup_additional_pages(struct linux_binprm *bprm, int uses_interp) #ifdef CONFIG_X86_64 -__initcall(sysenter_setup); +subsys_initcall(sysenter_setup); #ifdef CONFIG_SYSCTL /* Register vsyscall32 into the ABI table */ diff --git a/arch/x86/vdso/vma.c b/arch/x86/vdso/vma.c index ac74869..43456ee 100644 --- a/arch/x86/vdso/vma.c +++ b/arch/x86/vdso/vma.c @@ -74,7 +74,7 @@ static int __init init_...

...c_vmi_root) { + e = create_proc_entry("info", 0, proc_vmi_root); + if (e) + e->proc_fops = &proc_vmi_info_operations; + e = create_proc_entry("annotations", 0, proc_vmi_root); + if (e) + e->proc_fops = &proc_vmi_annotations_operations; + } + return 0; +} + +__initcall(proc_vmi_init); Index: linux-2.6.16-rc5/arch/i386/mach-vmi/Makefile =================================================================== --- linux-2.6.16-rc5.orig/arch/i386/mach-vmi/Makefile 2006-03-08 11:02:43.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/mach-vmi/Makefile 2006-03-08 11:03:12.0000...

...c_vmi_root) { + e = create_proc_entry("info", 0, proc_vmi_root); + if (e) + e->proc_fops = &proc_vmi_info_operations; + e = create_proc_entry("annotations", 0, proc_vmi_root); + if (e) + e->proc_fops = &proc_vmi_annotations_operations; + } + return 0; +} + +__initcall(proc_vmi_init); Index: linux-2.6.16-rc5/arch/i386/mach-vmi/Makefile =================================================================== --- linux-2.6.16-rc5.orig/arch/i386/mach-vmi/Makefile 2006-03-08 11:02:43.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/mach-vmi/Makefile 2006-03-08 11:03:12.0000...

...vcpu0/dom0 */ + vcpu_unpause(v); + + thaw_domains(); } static int __init acpi_sleep_init(void) @@ -268,6 +377,8 @@ static int __init acpi_sleep_init(void) sleep_states[i] = 0; } printk(")\n"); + + open_softirq(PM_SOFTIRQ, pm_softirq); return 0; } __initcall(acpi_sleep_init); diff -r 1539f5a2b3ba xen/include/asm-x86/smp.h --- a/xen/include/asm-x86/smp.h Tue Jun 26 18:05:22 2007 -0400 +++ b/xen/include/asm-x86/smp.h Tue Jun 26 18:05:22 2007 -0400 @@ -69,6 +69,8 @@ extern void enable_nonboot_cpus(void); extern void enable_nonboot_cpus(void); #else sta...

Hi all, I am using Xen 2.0.7. I have Broadcom NetXtreme BCM5704 Gigabit Ethernet (rev 02) cards which support frames greater than 1500. However when I boot into Xen and try to set the MTU to anything higher than 1500 (e.g., 4000, 8000 etc) I get a segmentation fault. After this fault, every command fails with a segmentation fault. I saw a similar bug report posted here:

...printk("heap[%d][%d][%d]-> %lu pages\n", + i, j, k, total); + } +} + +static __init int register_heap_trigger(void) +{ + register_keyhandler(''H'', dump_heap, "dump heap info"); + return 0; +} +__initcall(register_heap_trigger); + static __init int page_scrub_init(void) { diff -r e87b07e5fddd xen/include/xen/mm.h --- a/xen/include/xen/mm.h Tue Aug 15 11:36:36 2006 -0500 +++ b/xen/include/xen/mm.h Tue Aug 15 11:37:51 2006 -0500 @@ -45,7 +45,8 @@ void end_boot_allocator(void); /* Generic allocato...

...+ ctrl_if_send_response(msg); +} + +static int __init setup_vcpu_hotplug_event(void) +{ + struct vcpu_hotplug_handler_t *handler = &vcpu_hotplug_handler; + + handler->fn = NULL; + ctrl_if_register_receiver(CMSG_VCPU_HOTPLUG, vcpu_hotplug_event_handler, 0); + + return 0; +} + +__initcall(setup_vcpu_hotplug_event); + #else /* ... !CONFIG_HOTPLUG_CPU */ int __cpu_disable(void) { diff -urN a/tools/python/xen/lowlevel/xu/xu.c b/tools/python/xen/lowlevel/xu/xu.c --- a/tools/python/xen/lowlevel/xu/xu.c 2005-06-06 22:05:28.000000000 -0500 +++ b/tools/python/xen/lowlevel/xu/xu.c 2005-06...

...a, b; - a = *(unsigned int *)p; - b = *(unsigned int *)q; - if (a > b) - return 1; - if (a < b) - return -1; - return 0; -} - -static int __init init_sys32_ioctl(void) -{ - sort(ioctl_pointer, ARRAY_SIZE(ioctl_pointer), sizeof(*ioctl_pointer), - init_sys32_ioctl_cmp, NULL); - return 0; -} -__initcall(init_sys32_ioctl); -- 2.20.0

Hi Jens, James and Martin, This series concludes the work I did for linux-5.5 on the compat_ioctl() cleanup, killing off fs/compat_ioctl.c and block/compat_ioctl.c by moving everything into drivers. Overall this would be a reduction both in complexity and line count, but as I'm also adding documentation the overall number of lines increases in the end. My plan was originally to keep the

...a, b; - a = *(unsigned int *)p; - b = *(unsigned int *)q; - if (a > b) - return 1; - if (a < b) - return -1; - return 0; -} - -static int __init init_sys32_ioctl(void) -{ - sort(ioctl_pointer, ARRAY_SIZE(ioctl_pointer), sizeof(*ioctl_pointer), - init_sys32_ioctl_cmp, NULL); - return 0; -} -__initcall(init_sys32_ioctl); -- 2.20.0

..."); + for (i = 0; i < ACPI_S_STATE_COUNT; i++) + { + if (i == ACPI_STATE_S3) + { + sleep_states[i] = 1; + printk(" S%d", i); + } + else + sleep_states[i] = 0; + } + printk(")\n"); + return 0; +} +__initcall(acpi_sleep_init); diff -r 9261686d840c xen/arch/x86/acpi/suspend.c --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/xen/arch/x86/acpi/suspend.c Tue Jun 26 21:39:59 2007 -0400 @@ -0,0 +1,82 @@ +/* + * Suspend support specific for i386. + * + * Distribute under GPLv2 + * + * Copyright (c) 2002 Pave...

...< ACPI_S_STATE_COUNT; i++) { + if (i == ACPI_STATE_S3){ + sleep_states[i] = 1; + printk(" S%d", i); + } + else{ + sleep_states[i] = 0; + } + } + printk(")\n"); + + acpi_reserve_bootmem(); + return 0; +} +__initcall(acpi_sleep_init); diff -r 13e258a58044 xen/arch/x86/x86_32/acpi/Makefile --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/xen/arch/x86/x86_32/acpi/Makefile Wed Feb 14 11:13:40 2007 +0800 @@ -0,0 +1,2 @@ +obj-y += wakeup.o +obj-y += sleep.o diff -r 13e258a58044 xen/arch/x86/x86_32/power/Makefile -...

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct. However, I would greatly appreciate a second opinion on the

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct (given the available information Xen has), and that the

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends