From: Jan Kiszka <jan.kiszka@web.de>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Kernel oops in host caused by mmaping RAM
Date: Tue, 12 Apr 2011 23:09:01 +0200 [thread overview]
Message-ID: <4DA4BF6D.7000607@web.de> (raw)
In-Reply-To: <BANLkTinOOPAPmnzyNtX69V9FXrjsR_4rTQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
On 2011-04-12 21:41, Sasha Levin wrote:
> Hello,
>
> I've tried using mmap to map the RAM of a guest instead of
> posix_memalign which is used both in the kvm tool and qemu.
>
> Doing so caused a kernel Oops, which happens every time I run the code
> and was confirmed both on 2.6.38 and the latest git build of 2.6.39.
>
Can you share the test case that triggers it? That's easier than
guessing what you did precisely.
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-04-12 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 19:41 Kernel oops in host caused by mmaping RAM Sasha Levin
2011-04-12 21:09 ` Jan Kiszka [this message]
2011-04-13 12:50 ` Pekka Enberg
2011-04-13 12:58 ` Sasha Levin
2011-04-12 23:27 ` [PATCH] KVM: VMX: Ensure that vmx_create_vcpu always returns proper error Jan Kiszka
2011-04-16 14:50 ` Marcelo Tosatti
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=4DA4BF6D.7000607@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.