Kaigai, You should NOT configure crbce. This is an extended classification engine to drive up data to an user level daemon.
Stick with RBCE and you are fine. As for the CPU scheduler .. I will upload a new scheduler later tonight, that patch is outdated. Please read the Documentation/cpusched to see how to turn it on. Mem controller and I/O controller Chandra and Shailabh can attest to. Regards .. Hubertus. Kaigai Kohei wrote: > Hi, > > I tryed to build 2.6.8.1 kernel + E.16 CKRM patches on i686. > But I faced to the following problems. > Any comments or suggestion please. > > o On applying the four patches and relayfs. > * I applied relayfs-patch because CONFIG_CKRM_CRBCE depends on relayfs. > But there is no attention about it. Is it unkindness? > > * When I applied the cpu.ckrm-e16.v7.patch, patching to kernel/ckrm/Makefile > failed. > cpu.ckrm-e16.v7.patch describes as follows: > : > obj-$(CONFIG_CKRM_RES_LISTENAQ) += ckrm_laq.o > + obj-$(CONFIG_CKRM_CPU_SCHEDULE) += ckrm_cpu_class.o > ckrm_cpu_monitor.o > > But 'ckrm_laq.o' is wrong, it is 'ckrm_listenaq.o' actually. > I modified the patching command line because of this. > % cat ../E16/cpu.ckrm-e16.v7.patch | sed 's/ckrm_laq.o/ckrm_listenaq.o/g' > | patch -p1 > > * When I applied the mem.ckrm-e16.v3.patch after cpu.ckrm-e16.v7.patch and > io.ckrm-e16.v1.patch, > patching to kernel/ckrm/Makefile also failed. > mem.ckrm-e16.v3.patch describes as follows: > : > obj-$(CONFIG_CKRM_RES_LISTENAQ) += ckrm_listenaq.o > + obj-$(CONFIG_CKRM_RES_MEM) += ckrm_mem.o > But 'obj-$(CONFIG_CKRM_CPU_SCHEDULE) += ckrm_cpu_class.o > ckrm_cpu_monitor.o' had be inserted > under the '... + ckrm_listenaq.o' by 'cpu.ckrm-e16.v7.patch'. I modified > this line by hand. > > > o On Building up the patched kernel. > * The definition of GET_MEM_CLASS() is wrong. > It is defined as 'ckrm_get_res_class(tsk->taskclass, mem_rcbs.resid, > ckrm_mem_res_t)' > But tsk->taskclass is not ckrm_core_class_t type pointer. Should it be > defined as > 'ckrm_get_res_class((ckrm_core_class_t *)tsk->taskclass, mem_rcbs.resid, > ckrm_mem_res_t)' ? > I know Chandra fixed the above as that came up through the PlanetLab discussion. > * The declarations of cki_tsk_icls and cki_tsk_ioprio in > include/linux/ckrm-io.h are contradictory. > I commented out it, then I could build it. > drivers/block/ckrm-io.c:97: error: 'cki_tsk_icls' redeclared as different > kind of symbol > include/linux/ckrm-io.h:36: error: previous declaration of 'cki_tsk_icls' was > here > drivers/block/ckrm-io.c:97: error: 'cki_tsk_icls' redeclared as different > kind of symbol > include/linux/ckrm-io.h:36: error: previous declaration of 'cki_tsk_icls' was > here > drivers/block/ckrm-io.c:98: error: 'cki_tsk_ioprio' redeclared as different > kind of symbol > include/linux/ckrm-io.h:37: error: previous declaration of 'cki_tsk_ioprio' > was here > drivers/block/ckrm-io.c:98: error: 'cki_tsk_ioprio' redeclared as different > kind of symbol > include/linux/ckrm-io.h:37: error: previous declaration of 'cki_tsk_ioprio' > was here > Shailabh ? > > o On Booting up the kernel. > I faced to kernel panic on generic_file_aio_write_nolock(). > EIP = 0xc0148950, it means include/linux/mm.h:381. > ------------------------------------------------------------ > Linux version 2.6.8.1-test ([EMAIL PROTECTED]) (gcc version 3.3.3 20040412 > (Red Hat Linux 3.3.3-7)) #1 Wed Nov 24 24 > BIOS-provided physical RAM map: > BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) > BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) > BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) > BIOS-e820: 0000000000100000 - 000000001dff0000 (usable) > BIOS-e820: 000000001dff0000 - 000000001dff8000 (ACPI data) > BIOS-e820: 000000001dff8000 - 000000001e000000 (ACPI NVS) > BIOS-e820: 00000000fec00000 - 00000000fed00000 (reserved) > BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved) > BIOS-e820: 00000000ffee0000 - 00000000fff0ffff (reserved) > BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved) > 0MB HIGHMEM available. > 479MB LOWMEM available. > DMI 2.3 present. > ACPI: RSDP (v000 AMI ) @ 0x000fa220 > ACPI: RSDT (v001 AMIINT SiS645XX 0x00000010 MSFT 0x0100000b) @ 0x1dff0000 > ACPI: FADT (v001 AMIINT SiS645XX 0x00000011 MSFT 0x0100000b) @ 0x1dff0030 > ACPI: DSDT (v001 SiS 645 0x00001000 MSFT 0x0100000d) @ 0x00000000 > ACPI: PM-Timer IO Port: 0x808 > Built 1 zonelists > Kernel command line: ro root=LABEL=ROOT rhgb console=ttyS0,115200 > Initializing CPU#0 > PID hash table entries: 2048 (order 11: 16384 bytes) > CKRM Initialization > ...... Initializing ClassType<taskclass> ........ > ...... Initializing ClassType<socketclass> ........ > CKRM Initialization done > Detected 2391.408 MHz processor. > Using pmtmr for high-res timesource > Console: colour VGA+ 80x25 > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > Memory: 482628k/491456k available (1952k kernel code, 8092k reserved, 664k > data, 160k init, 0k highmem) > Checking if this processor honours the WP bit even in supervisor mode... Ok. > Calibrating delay loop... 4734.97 BogoMIPS > Security Scaffold v1.0.0 initialized > SELinux: Initializing. > SELinux: Starting in permissive mode > There is already a security framework initialized, register_security failed. > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 512 (order: 0, 4096 bytes) > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 128K > Intel machine check architecture supported. > Intel machine check reporting enabled on CPU#0. > CPU0: Intel P4/Xeon Extended MCE MSRs (12) available > CPU: Intel(R) Celeron(R) CPU 2.40GHz stepping 09 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Checking 'hlt' instruction... OK. > checking if image is initramfs...it isn't (no cpio magic); looks like an > initrd > Unable to handle kernel NULL pointer dereference at virtual address 00000064 > printing eip: > c0148950 > *pde = 00000000 > Oops: 0002 [#1] > Modules linked in: > CPU: 0 > EIP: 0060:[<c0148950>] Not tainted > EFLAGS: 00010002 (2.6.8.1-test) > EIP is at __pagevec_lru_add+0xf0/0x420 > eax: 00000001 ebx: 00000000 ecx: c0337a28 edx: ffffffff > esi: c1436d94 edi: 00000000 ebp: ddf8e718 esp: c14b3dfc > ds: 007b es: 007b ss: 0068 > Process swapper (pid: 1, threadinfo=c14b2000 task=c14b1830) > Stack: c14369c8 0000000f ddf8e71c c14369c8 c0337a04 00000000 c14b3eb4 c14369c8 > 0000000f 00000000 ddf8e718 c0140ffd 000000d0 00000006 00000003 00000001 > 00000008 00000008 00000005 00000004 00000004 00000006 00001000 00000000 > Call Trace: > [<c0140ffd>] generic_file_aio_write_nolock+0x6cd/0x9d0 > [<c014135a>] generic_file_write_nolock+0x5a/0x80 > [<c01b2919>] selinux_file_permission+0x119/0x160 > [<c0141475>] generic_file_write+0x55/0x70 > [<c015bcf1>] vfs_write+0xd1/0x120 > [<c015be07>] sys_write+0x47/0x80 > [<c03955a0>] populate_rootfs+0xb0/0x100 > [<c01003f0>] init+0x0/0x100 > [<c0100410>] init+0x20/0x100 > [<c0104298>] kernel_thread_helper+0x0/0x18 > [<c010429d>] kernel_thread_helper+0x5/0x18 > Code: ff 44 83 60 89 d8 e8 d5 c4 fe ff 85 c0 74 5a ff 43 3c 83 7b > <0>Kernel panic: Attempted to kill init! > ------------------------------------------------------------ > Related Kconfig is as follows: > > # > # Class Based Kernel Resource Management > # > CONFIG_CKRM=y > CONFIG_RCFS_FS=y > CONFIG_CKRM_TYPE_TASKCLASS=y > CONFIG_CKRM_RES_NUMTASKS=y > CONFIG_CKRM_CPU_SCHEDULE=y > CONFIG_CKRM_RES_BLKIO=y > CONFIG_CKRM_RES_MEM=y > CONFIG_CKRM_MEM_LRUORDER_CHANGE=y > CONFIG_CKRM_TYPE_SOCKETCLASS=y > # CONFIG_CKRM_RBCE is not set > CONFIG_CKRM_CRBCE=y > CONFIG_SYSCTL=y > CONFIG_AUDIT=y > CONFIG_AUDITSYSCALL=y > CONFIG_LOG_BUF_SHIFT=17 > CONFIG_HOTPLUG=y > # CONFIG_IKCONFIG is not set > # CONFIG_EMBEDDED is not set > CONFIG_DELAY_ACCT=y > : > # > # Pseudo filesystems > # > : > CONFIG_RELAYFS_FS=y > # CONFIG_KLOG_CHANNEL is not set > > Thanks. Overall, we made a bunch of bug changes internally. It is time we move these up to form E17. Shailabh, could you start doing that, this seems like a pretty good time to do it ? -- Hubertus ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
