qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: ml-qemu@twilight-hall.net
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] mips-user socket-related syscall support
Date: Tue, 20 Jun 2006 00:52:08 +0200	[thread overview]
Message-ID: <44972A98.6060905@bellard.org> (raw)
In-Reply-To: <449667B1.5070300@twilight-hall.net>

Another point is that doing:

+    target_long args[6];
+
+    tputl(args, arg1);
+    tputl(args+1, arg2);
+    tputl(args+2, arg3);
+    tputl(args+3, arg4);
+    tputl(args+4, arg5);
+    tputl(args+5, arg6);

at the start of every syscall is not acceptable. You should add a 
specific socket call wrapper which takes arg1... arg6 as arguments.

Regards,

Fabrice.

Raphaël Rigo wrote:
> Hello,
> this patch is a revamped version of the one I posted about 2 months ago,
> it is much better. It implements the syscalls related to sockets on the
> MIPS platform (because it has no "socketcall" syscall). I had to create
> a "socket.h" file defining the constants for the targets because MIPS
> doesn't have the same as every other platform.
> 
> The calls implemented are : accept, bind, connect, getpeername,
> getsockname, listen, recv, recvfrom, recvmsg, send, sendmsg, sendto,
> shutdown, socket, socketpair.
> 
> Combined with the other patch I just posted (signal handling), qemu-mips
> is now capable of running a webserver (which is very nice :)
> 
> Please consider it for inclusion into mainline.
> 
> Raphaël Rigo

  parent reply	other threads:[~2006-06-19 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  9:00 [Qemu-devel] [PATCH] mips-user socket-related syscall support Raphaël Rigo
2006-06-19 22:03 ` Fabrice Bellard
2006-06-20  6:54   ` Raphaël Rigo
2006-06-20  8:28     ` Thiemo Seufer
2006-06-19 22:52 ` Fabrice Bellard [this message]
2006-06-20  8:47   ` Raphaël Rigo
2006-06-22 17:14     ` Raphaël Rigo
2006-06-24 15:08       ` Fabrice Bellard

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=44972A98.6060905@bellard.org \
    --to=fabrice@bellard.org \
    --cc=ml-qemu@twilight-hall.net \
    --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).