Bug 858 - OProfile-viewer connect issue to oprofile-server running on qemux86-64
Summary: OProfile-viewer connect issue to oprofile-server running on qemux86-64
Status: RESOLVED FIXED
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: kernel-configuration (show other bugs)
Version: 1.0
Hardware: x86 x86_64
: Medium normal
Target Milestone: 1.1
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-03-12 16:22 UTC by Jessica
Modified: 2011-05-02 19:31 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica 2011-03-12 16:22:17 UTC
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)
Comment 1 Lianhao Lu 2011-03-13 01:56:45 UTC
Is this caused by bug#859? This message shows the "opcontrol" failed on the target qemux86-64.
Comment 2 Jessica 2011-03-13 19:10:18 UTC
One is latency top missing config in qemux86-64 kernel, this one is for oprofile, are they related?
Comment 3 Lianhao Lu 2011-03-13 19:43:10 UTC
(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.
Comment 4 Dexuan Cui 2011-03-13 19:44:38 UTC
(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.
Comment 5 Lianhao Lu 2011-03-13 22:12:49 UTC
This is caused by the missing configuration of CONFIG_OPROFILE in x86_64 kernel configuration.
Comment 6 Dexuan Cui 2011-03-14 00:54:02 UTC
(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
Comment 7 Jessica 2011-03-14 15:27:49 UTC
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        = ""
Comment 8 Darren Hart 2011-03-14 15:54:16 UTC
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.
Comment 9 Darren Hart 2011-03-14 16:55:33 UTC
Temp fix until Bruce can commit to linux-yocto.

http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=dvhart/kernel&id=cc3e525fdb480d6b86637afa7b4c8d947d32304b
Comment 11 Jessica 2011-05-02 19:31:58 UTC
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