qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xuebing wang <xbing6@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: linux-arm-kernel@lists.infradead.org
Subject: [Qemu-devel]  Using qemu to debug arm64 linux kernel
Date: Mon, 03 Mar 2014 17:28:41 +0800	[thread overview]
Message-ID: <53144B49.8010407@gmail.com> (raw)

Hi community,

I can think of 2 ways to use gdb+qemu to remotely debug arm64 kernel, by 
enabling gdbstub within qemu to communicate with gdb.

I am wondering in the real-world practice, is this debug technique 
helpful for debugging arm64 kernel?

Options are:

1) Host environment: qemu is running as kvm hypervisor

i) armv8 foundation model running arm64 kernel
ii) or a real armv8 Linux machine running arm64 kernel

Qemu guest environment: arm64 kernel

2) Host environment: x86 linux machine running qemu as tcg aarch64 emulator

Qemu guest environment: arm64 kernel

Prerequisite: qemu-aarch64 needs to be reliable.

-- Thanks,
Xuebing Wang

                 reply	other threads:[~2014-03-03  9:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53144B49.8010407@gmail.com \
    --to=xbing6@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=qemu-devel@nongnu.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).