From: Marc Zyngier <marc.zyngier@arm.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: kvm [2087]: load/store instruction decoding not implemented
Date: Tue, 24 Feb 2015 16:37:31 +0000 [thread overview]
Message-ID: <54ECA8CB.8000402@arm.com> (raw)
In-Reply-To: <20150224150911.GQ11603@redhat.com>
On 24/02/15 15:09, Richard W.M. Jones wrote:
>> On 24/02/15 14:36, Richard W.M. Jones wrote:
>>> I can probably bisect this given time, but I'm going to try putting
>>> some debug into the userspace process to find out which system call
>>> fails first.
>
> Perhaps not surprisingly, it's the init_module syscall which causes
> the failure, ie. this line of code:
>
> https://github.com/libguestfs/supermin/blob/master/src/init.c#L436
>
> I've no idea why that code would call copy_to_user. It should be
> copying the other way ...
>
> It also fails on the first call to init_module, so the fact that it's
> loading crc32-arm64.ko may just be a coincidence.
>
> There are no other userspace processes running, but just to be sure
> that it's not some other process in the guest, I also added a sleep
> before the call to init_module, but same result as above.
>
> I also looked at the implementation of init_module in glibc, but
> AFAICT init_module is a straight syscall and glibc is not involved.
>
> I also looked to see if I was calling init_module correctly on aarch64
> (in case it has a different # of arguments of something) but it's
> called in the same way in the libkmod code, so I think we're OK.
>
> Next up, I will have a go at bisecting the guest kernel.
Patch posted there:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325445.html
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-02-24 16:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 11:59 kvm [2087]: load/store instruction decoding not implemented Richard W.M. Jones
2015-02-24 12:15 ` Peter Maydell
2015-02-24 12:29 ` Richard W.M. Jones
2015-02-24 12:47 ` Christoffer Dall
2015-02-24 13:12 ` Marc Zyngier
2015-02-24 13:45 ` Richard W.M. Jones
2015-02-24 14:10 ` Marc Zyngier
2015-02-24 14:36 ` Richard W.M. Jones
2015-02-24 14:42 ` Marc Zyngier
2015-02-24 14:43 ` Richard W.M. Jones
2015-02-24 15:03 ` Marc Zyngier
2015-02-24 15:09 ` Richard W.M. Jones
2015-02-24 15:20 ` Marc Zyngier
2015-02-24 16:37 ` Marc Zyngier [this message]
2015-02-24 14:25 ` Richard W.M. Jones
2015-02-24 14:55 ` Christoffer Dall
2015-02-24 15:06 ` Peter Maydell
2015-02-24 15:22 ` Richard W.M. Jones
2015-02-24 12:57 ` Peter Maydell
2015-02-24 12:16 ` Christoffer Dall
2015-02-24 12:27 ` Richard W.M. Jones
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=54ECA8CB.8000402@arm.com \
--to=marc.zyngier@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=rjones@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox