[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-devel] Questions with Xenoprofile
- To: zhouye <zhouyejoe@xxxxxxxxxxx>
- From: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
- Date: Tue, 20 Oct 2009 04:34:39 +0000
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Mon, 19 Oct 2009 21:35:34 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcpRL1kz0u9kcE77QMqB98LpWZeyZgACaQJA
- Thread-topic: [Xen-devel] Questions with Xenoprofile
You really do not need to use modules. Actually if
you are using passive domain profiling you will not be able to get module
profiles for domU, It would be better to use builtin
drivers.
In that case, you can get fuction level profiles with
XenoOprofile which can give you enough detail to identify virtual block device
costs. You will need to identify which functions in the profile
are related to virtual block device, but this should not be hard looking at the
virtual block device source code files or symbol table of the
associated "*.o" files.
Renato
Nowadays I am troubling with
Xenoprofile!I want to use Xenoprofile to get the exact cost of xen
block-device backend/frontend driver ,so I can find the bottleneck and
improve on it.But with the manual of xenoprofile, driver is in the layer
operating system.If we wanna to test the driver cost, we must compile
the driver in modules but not in the kernel.After I compile the driver in
modules, I can't make the domainU started and it said that can't find block
device because when domainU is being started, there is no driver to read the
block device.
How can I solve this problem?
------------------
Best Regarding!
Ye Zhou
--------------------------------------------------------
Cluster and Grid Computing Lab
Services Computing Technology and System Lab
Department of Computer Science
Huazhong University of Science and Technology Wuhan, 430074, China
Mobile:+86-13437170320
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|