From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55869) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKPBA-0005Hr-76 for qemu-devel@nongnu.org; Mon, 03 Mar 2014 04:29:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WKPB1-0005Hq-Pd for qemu-devel@nongnu.org; Mon, 03 Mar 2014 04:28:56 -0500 Received: from mail-pb0-x229.google.com ([2607:f8b0:400e:c01::229]:45366) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKPB1-0005Es-Gn for qemu-devel@nongnu.org; Mon, 03 Mar 2014 04:28:47 -0500 Received: by mail-pb0-f41.google.com with SMTP id jt11so3572478pbb.28 for ; Mon, 03 Mar 2014 01:28:46 -0800 (PST) Message-ID: <53144B49.8010407@gmail.com> Date: Mon, 03 Mar 2014 17:28:41 +0800 From: Xuebing wang MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Using qemu to debug arm64 linux kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU Developers Cc: linux-arm-kernel@lists.infradead.org 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