From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@kernel.org>
Cc: kvm@vger.kernel.org, Asias He <asias.hejun@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>
Subject: Re: [PATCH] kvm tools: Introduce KVM VCPU data structure
Date: Sat, 9 Apr 2011 13:59:13 +0200 [thread overview]
Message-ID: <20110409115913.GA26593@elte.hu> (raw)
In-Reply-To: <1302343631-30060-1-git-send-email-penberg@kernel.org>
* Pekka Enberg <penberg@kernel.org> wrote:
> In preparation for threaded execution model, this patch introduces a KVM VCPU
> data structure 'struct kvm_cpu'.
>
> Cc: Asias He <asias.hejun@gmail.com>
> Cc: Cyrill Gorcunov <gorcunov@gmail.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Signed-off-by: Pekka Enberg <penberg@kernel.org>
> ---
> tools/kvm/Makefile | 1 +
> tools/kvm/cpuid.c | 6 +-
> tools/kvm/include/kvm/kvm-cpu.h | 33 ++++
> tools/kvm/include/kvm/kvm.h | 16 --
> tools/kvm/ioport.c | 2 +
> tools/kvm/kvm-cpu.c | 370 +++++++++++++++++++++++++++++++++++++++
> tools/kvm/kvm-run.c | 62 ++++---
> tools/kvm/kvm.c | 338 -----------------------------------
> 8 files changed, 445 insertions(+), 383 deletions(-)
> create mode 100644 tools/kvm/include/kvm/kvm-cpu.h
> create mode 100644 tools/kvm/kvm-cpu.c
This commit causes a segfault for 'kvm run bzImage':
(gdb) set args run bzImage
(gdb) run
Starting program: /home/mingo/tip/tools/kvm/kvm run bzImage
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000405054 in setup_bios (kvm=0x68a010) at bios.c:106
106 memset(p, 0, BDA_END - BDA_START);
Missing separate debuginfos, use: debuginfo-install glibc-2.13-1.x86_64
(gdb) bt
#0 0x0000000000405054 in setup_bios (kvm=0x68a010) at bios.c:106
#1 0x0000000000404ef5 in kvm_cmd_run (argc=<value optimized out>, argv=<value optimized out>,
prefix=<value optimized out>) at kvm-run.c:160
#2 0x00000000004038cf in handle_kvm_command (argc=<value optimized out>, argv=<value optimized out>)
at main.c:16
#3 main (argc=<value optimized out>, argv=<value optimized out>) at main.c:21
(gdb) q
A debugging session is active.
Thanks,
Ingo
next prev parent reply other threads:[~2011-04-09 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 10:07 [PATCH] kvm tools: Introduce KVM VCPU data structure Pekka Enberg
2011-04-09 11:59 ` Ingo Molnar [this message]
2011-04-09 12:25 ` Cyrill Gorcunov
2011-04-09 12:27 ` Ingo Molnar
2011-04-09 12:33 ` Cyrill Gorcunov
2011-04-09 12:34 ` Pekka Enberg
2011-04-09 12:35 ` Cyrill Gorcunov
2011-04-09 12:38 ` Pekka Enberg
2011-04-09 12:26 ` Ingo Molnar
2011-04-09 12:30 ` Pekka Enberg
2011-04-09 12:36 ` Ingo Molnar
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=20110409115913.GA26593@elte.hu \
--to=mingo@elte.hu \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=penberg@kernel.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