| Summary: | OProfile-viewer connect issue to oprofile-server running on qemux86-64 | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | Jessica <jessica.zhang> |
| Component: | kernel-configuration | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bruce.ashfield, dexuan.cui, dvhart, lianhao.lu, sgw, tom.zanussi, yp.kernel.watcher, yp.sdk.watcher, yp.watcher |
| Version: | 1.0 | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Jessica
2011-03-12 16:22:17 UTC
Is this caused by bug#859? This message shows the "opcontrol" failed on the target qemux86-64. One is latency top missing config in qemux86-64 kernel, this one is for oprofile, are they related? (In reply to comment #2) > One is latency top missing config in qemux86-64 kernel, this one is for > oprofile, are they related? Sorry, I mis-confused oprofile with latencytop. (In reply to comment #0) > While testing oprofile-viewer connecting to oprofile-server running in > qemux86-64, got error "Error whilst spawning: opcontrol exited with error code: > 1. (note: host is 32bit Ubuntu 10.04) In qemux86-64 target, "opcontrol --init" reports: FATAL: Module oprofile not found. FATAL: Module oprofile not found. Kernel doesn't support oprofile BTW: qemux86's workable config: CONFIG_OPROFILE=y # CONFIG_OPROFILE_EVENT_MULTIPLEX is not set CONFIG_HAVE_OPROFILE=y qemux86-64's "bad" config: CONFIG_HAVE_OPROFILE=y So looks qemux86-64 needs CONFIG_OPROFILE=y, too. This is caused by the missing configuration of CONFIG_OPROFILE in x86_64 kernel configuration. (In reply to comment #4) > (In reply to comment #0) > > While testing oprofile-viewer connecting to oprofile-server running in > > qemux86-64, got error "Error whilst spawning: opcontrol exited with error code: > > 1. (note: host is 32bit Ubuntu 10.04) > In qemux86-64 target, "opcontrol --init" reports: > FATAL: Module oprofile not found. > FATAL: Module oprofile not found. > Kernel doesn't support oprofile > BTW: > qemux86's workable config: > CONFIG_OPROFILE=y > # CONFIG_OPROFILE_EVENT_MULTIPLEX is not set > CONFIG_HAVE_OPROFILE=y > qemux86-64's "bad" config: > CONFIG_HAVE_OPROFILE=y > So looks qemux86-64 needs CONFIG_OPROFILE=y, too. BTW: after "bitbake -c menuconfig virtual/linux" and setting CONFIG_OPROFILE=y for qemux86-64, oprofile can work in qemux86-64 target in timer interrupt mode. So I believe qemux86-64 needs CONFIG_OPROFILE=y OE Build Configuration: BB_VERSION = "1.11.0" METADATA_BRANCH = "bernard" METADATA_REVISION = "a33a2cc024f9c9147c92c5da70d8fbb631b968f9" TARGET_ARCH = "x86_64" TARGET_OS = "linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "0.9+snapshot-20110314" TARGET_FPU = "" This is missing from common-pc-64.scc +include features/profiling/profiling.scc We'll have to commit a fragment for qemux86-64 for now. Temp fix until Bruce can commit to linux-yocto. http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=dvhart/kernel&id=cc3e525fdb480d6b86637afa7b4c8d947d32304b Fixed in Master and Bernard http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=50bb373d1b3956cd4877752d3811e45a93ac2e33 verified that the kernel config issue is fixed, but there's no oprofile data collected, I think Dexuan has another bug opened regarding it since below in the comments he said qemux86-64 only works in the timer interrupt mode |