Re: [PATCH] kvm tools: Introduce KVM VCPU data structure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Cyrill Gorcunov <gorcunov@xxxxxxxxx> wrote:

> On 04/09/2011 03:59 PM, Ingo Molnar wrote:
> > 
> > * Pekka Enberg <penberg@xxxxxxxxxx> wrote:
> > 
> >> In preparation for threaded execution model, this patch introduces a KVM VCPU
> >> data structure 'struct kvm_cpu'.
> >>
> >> Cc: Asias He <asias.hejun@xxxxxxxxx>
> >> Cc: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
> >> Cc: Ingo Molnar <mingo@xxxxxxx>
> >> Signed-off-by: Pekka Enberg <penberg@xxxxxxxxxx>
> >> ---
> ...
> > 
> > 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);
> 
> Ugh, Pekka, was the memory properly mmaped? Setup bios called multiple
> times in every thread?

Why should mmap() be called in every thread?

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux