From: holmes <albert.holmes@163.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re:Re: how to debug xen
Date: Tue, 1 Feb 2011 04:39:07 +0800 (CST) [thread overview]
Message-ID: <21dae07b.21d.12dddcce17a.Coremail.albert.holmes@163.com> (raw)
In-Reply-To: <20110131201858.GD2754@reaktio.net>
Hi Pasi,
Thank you! Can you tell me how to log the activities here? Give me few codes or hints?
BTW, can I use printf or what else to do the log thing?
Thanks!
At 2011-01-31 15:18:58,"Pasi Kärkkäinen" <pasik@iki.fi> wrote:
>On Tue, Feb 01, 2011 at 03:41:02AM +0800, holmes wrote:
>> Hi all,
>> I am new to Xen. I want to debug xen. So I have few questions here. If
>> anybody can help me, I'd appreciate it.
>> 1: My system is ubuntu 8.04. I download the xen-3.4.2 source code from xen
>> website. After I "make world", it will download the linux-2.6.18-xen.hg
>> (kernel?). Also it will make many other folders (./dist). I found
>> blkfront.c in both ./linux-2.6.18-xen.hg/drivers/xen/blkfront folder and
>> ./dist/install/lib/modules/2.6.18.8-xen/source/drivers/xen/blkfront/
>> folder. So, what's the difference of the two folders and what are they
>> doing?
>
>
>dist/ is the directory where stuff lands after successful build,
>ie. you can copy from dist/ to / to install xen.
>
>
>> 2: if I want to log the activities (read/write block) information in
>> domU(winxp), how do I log it? For example, if domU read a block, I
>> therefore print a information into a log file (like "domU read"). Should I
>> change something in blkfront.c file? If so, which one should I change,
>> because there are two blkfront.c.
>> 3: if I want to log the information, I GUESS (not sure) I should use
>> log.debug (or else) to log the info. into some log files. How should I do?
>> Can anyone give me suggestion?
>>
>
>blkfront is the *frontend* driver for Linux, so a Linux domU running 2.6.18-xen
>would use it to access the virtual disks.
>
>You need to check blkback (blkbk) driver! That's the one running in dom0
>providing virtual disks for vms.
>
>-- Pasi
>
next prev parent reply other threads:[~2011-01-31 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 19:41 how to debug xen holmes
2011-01-31 20:18 ` Pasi Kärkkäinen
2011-01-31 20:39 ` holmes [this message]
2011-02-01 16:09 ` Jiang Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21dae07b.21d.12dddcce17a.Coremail.albert.holmes@163.com \
--to=albert.holmes@163.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).