From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, james@alentdesignsolutions.com
Subject: Re: [Qemu-devel] Syscall 269
Date: Thu, 18 Nov 2004 13:03:47 +0000 [thread overview]
Message-ID: <200411181303.47086.paul@codesourcery.com> (raw)
In-Reply-To: <200411180138.46857.james@alentdesignsolutions.com>
On Thursday 18 November 2004 09:38, James Pellow wrote:
> Hi All,
>
> I am trying to chroot to a gentoo flavor of arm linux on my AMD
> tbird-1.4GHz. I have set up binfmt_misc and qemu to allow me to do the
> chroot, and all seems to be working well. Now I wanted to emerge some
> stuff, and I get the following message:
>
> qemu: Unsupported syscall: 269.
>
> Looking at the arm linux kernel source, I see that 269 is utimes. Looking
> at the source code for qemu it seems that all I have to do is to add a
> define for TARGET_NR_utimes in all linux-user/*/syscall_nr.h and then add a
> new case in linux-user/syscall.c.
>
> So, I gave it a shot. The patch is at the bottom of this message. This is
> the first time I have looked at the qemu sources, so I am likely missing
> something, but the patch does seem to allow emerge to work properly under
> gentoo. If a correct implementation requires more work, I am happy to do
> that too, just let me know. BTW, I am not subscribed to this list to
> please CC me.
You also need to do proper 32/64bit and big/little endian conversion of struct
timeval. It happens to work in your case because arm-linux and i686-linux
both use the same word size and endianness.
Paul
next prev parent reply other threads:[~2004-11-18 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 9:38 [Qemu-devel] Syscall 269 James Pellow
2004-11-18 13:03 ` Paul Brook [this message]
2004-11-18 18:24 ` James Pellow
2004-12-04 0:05 ` James Pellow
2004-12-04 15:09 ` Paul Brook
2004-12-06 1:16 ` James Pellow
2004-12-06 1:26 ` Paul Brook
2004-12-06 2:58 ` James Pellow
2004-12-08 0:07 ` [Qemu-devel] Trivial (but useful) patch to save qemu pid to file Nile Geisinger
2004-12-08 18:12 ` Felipe Sanchez
2004-12-08 22:01 ` Fabrice Bellard
2004-12-09 2:11 ` Tim
2004-12-13 13:20 ` Nile Geisinger
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=200411181303.47086.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=james@alentdesignsolutions.com \
--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).