From: Riku Voipio <riku.voipio@iki.fi>
To: Martin Mohring <martin.mohring@opensuse.org>
Cc: qemu-devel@nongnu.org, dl9pf@gmx.de
Subject: Re: [Qemu-devel] linux-user/arm unsupported syscalls
Date: Thu, 22 Jan 2009 23:04:06 +0200 [thread overview]
Message-ID: <20090122210406.GA15463@kos.to> (raw)
In-Reply-To: <4978D8FB.30801@opensuse.org>
On Thu, Jan 22, 2009 at 09:37:15PM +0100, Martin Mohring wrote:
> Jan-Simon Möller wrote:
> > Hi!
> >
> > I'm running some debian-lenny/arm binaries in user-mode emulation and get these 2 messages:
debian/arm or debian/armel ? Which specific binaries?
> > qemu: Unsupported ARM syscall: 0x9000e5
> > qemu: Unsupported ARM syscall: 0x9000e2
> Does anybody here know what the 0x9 number in front of e5 and e2 means?
oldabi syscalls.
> When such an error comes in qemu, for me usually a decimal number of a
> syscall from any of the "linux-user/<arch>/syscall_nr.h file is printed.
> But not a hexnumber with 0x9000 in front....
Because the error is being printed from a place than usual. Qemu appears
to think the binary is eabi and is thus not reducing 0x900000 as usual
when running oldabi binaries.
The warned syscalls (setxattr, getattr) go usually via the
unimplemented_nowarn path, so no warning should be visible for users.
--
"rm -rf" only sounds scary if you don't have backups
next prev parent reply other threads:[~2009-01-22 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 19:14 [Qemu-devel] linux-user/arm unsupported syscalls Jan-Simon Möller
2009-01-22 20:37 ` Martin Mohring
2009-01-22 21:04 ` Riku Voipio [this message]
2009-01-23 9:54 ` Jan-Simon Möller
2009-01-28 15:22 ` Riku Voipio
2009-01-28 16:28 ` Jan-Simon Möller
2009-01-28 16:36 ` Martin Mohring
2009-01-28 16:46 ` Riku Voipio
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=20090122210406.GA15463@kos.to \
--to=riku.voipio@iki.fi \
--cc=dl9pf@gmx.de \
--cc=martin.mohring@opensuse.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).