Fwd: how to debug kernel in qemu using ubuntu image
---------- Forwarded message ---------- From: Amirali Shambayati <amirali.shambayati@gmail.com> Date: Tue, May 10, 2011 at 3:11 PM Subject: how to debug kernel in qemu using ubuntu image To: Linux Kernel <linux-kernel@vger.kernel.org> Hello all, I asked my question in "linux kernel" mailing list, and I was suggested to forward it to this mailing list. I'm using linux-0.2.img image(which is a light linux image) to debug kernel using Qemu. I'm working on IO schedulers' optimization. As Qemu boots kernel, IO scheduler sends read requests to disk. Also by entering commands such as 'ls', it sends read requests. I'm looking for a way to send write requests. Thus I thought that using a benchmark which sends both read and write requests, is suitable, but as linux-0.2.img is a very simple and light image, it is almost impossible to setup heavy benchmarks on it. So I want to use an ubuntu image instead. But I don't know where I should see kernel printks. Thanks in advance Regards, -- Amirali Shambayati Bachelor Student Computer Engineering Department Sharif University of Technology Tehran, Iran -- Amirali Shambayati Bachelor Student Computer Engineering Department Sharif University of Technology Tehran, Iran
Hi... On Mon, May 16, 2011 at 13:40, Amirali Shambayati <amirali.shambayati@gmail.com> wrote:
I'm using linux-0.2.img image(which is a light linux image) to debug kernel using Qemu.
where do you get that image? and why don't you make one by yourself?
I'm working on IO schedulers' optimization. As Qemu boots kernel, IO scheduler sends read requests to disk. Also by entering commands such as 'ls', it sends read requests. I'm looking for a way to send write requests.
"echo" command? "dd"?
Thus I thought that using a benchmark which sends both read and write requests, is suitable, but as linux-0.2.img is a very simple and light image, it is almost impossible to setup heavy benchmarks on it.
could you explain what do you mean by "heavy"?
So I want to use an ubuntu image instead. But I don't know where I should see kernel printks.
"see"? or "set"? I believe it's the latter, right? what do you want to see through printk, anyway? -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
participants (2)
-
Amirali Shambayati -
Mulyadi Santosa