kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to debug kernel in qemu using ubuntu image
Date: Tue, 17 May 2011 01:40:45 +0700	[thread overview]
Message-ID: <BANLkTin_Cw58ZBxLK6jFXvhqO4Q4+MF1UA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=+fd2URxvYLQ6CFtqJmC0Ct4MWPw@mail.gmail.com>

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

      reply	other threads:[~2011-05-16 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTimS++GWcNSBNqwZ=cUtQwX1wdKzUQ@mail.gmail.com>
2011-05-16  6:40 ` Fwd: how to debug kernel in qemu using ubuntu image Amirali Shambayati
2011-05-16 18:40   ` Mulyadi Santosa [this message]

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=BANLkTin_Cw58ZBxLK6jFXvhqO4Q4+MF1UA@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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).