From: vibi sreenivasan <vibi_sreenivasan@cms.com>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH ] linux-user: add tee systemcall support
Date: Tue, 19 May 2009 18:06:14 +0530 [thread overview]
Message-ID: <1242736574.2188.32.camel@system> (raw)
In-Reply-To: <20090519113635.GA11400@kos.to>
hi ,
thanks for looking into my code.
On Tue, 2009-05-19 at 14:36 +0300, Riku Voipio wrote:
> On Tue, May 19, 2009 at 01:42:03PM +0530, vibi sreenivasan wrote:
> > hi all,
>
> > >Subject: [Qemu-devel] [PATCH ] linux-user: add tee systemcall support
>
> > Is there any thing wrong with this patch. Please give some feedback
> > So if there is anything wrong i will be able to correct it.
>
> The implementation of tee appears fine. However, the tee testcases
> I found all also used splice. What did you use to test this
i used a small test code
----------------------------------------------------------------------------------------
#define _GNU_SOURCE
#include <fcntl.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#define die(X) do { perror(#X);exit(EXIT_FAILURE); } while(0)
#define SZ 255
#define TEST_STRING "This is a test to check the presence of tee system call\n\
This print states that tee system call is present\n"
int main(void)
{
int pipe1[2], pipe2[2],strln = strlen(TEST_STRING);
char data[SZ] = {0};
if (pipe(pipe1) || pipe(pipe2))
die("perror");
if (write(pipe1[1], TEST_STRING, strln) < 0)
die("write");
if(tee(pipe1[0], pipe2[1], strln, SPLICE_F_MOVE) != strln)
die("tee");
if(read(pipe2[0], data, SZ - 1) < 0)
die("read");
printf("%s",data);
fflush(stdout);
}
----------------------------------------------------------------------------------------------
> , or do
> you plan to implement splice too?
>
yes i am plannig to implement splice & vmsplice.
Also i have a plan to look in to adding support for
unimplemented syscalls (got that idea from TODO),if any.
Before that i was trying to make sure that i am going in the
right path.
thanks & regards
vibi sreenivasan
> >
> > Thanks & Regards
> > vibi sreenivasan
> >
> > >Signed-off-by: vibi <vibi_sreenivasan@cms.com>
> > >---
> > >linux-user/syscall.c | 8 ++++++++
> > >1 files changed, 8 insertions(+), 0 deletions(-)
> >
> > >diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> > >index 76f0c95..f2f87c3 100644
> > >--- a/linux-user/syscall.c
> > >+++ b/linux-user/syscall.c
> > >@@ -6580,6 +6580,14 @@ abi_long do_syscall(void *cpu_env, int num,
> > >abi_long arg1,
> > break;
> > >#endif
> >
> > >+#ifdef TARGET_NR_tee
> > >+ case TARGET_NR_tee:
> > >+ {
> > >+ ret = get_errno(tee(arg1,arg2,arg3,arg4));
> > >+ }
> > >+ break;
> > >+#endif
> > >+
> > > default:
> > > unimplemented:
> > > gemu_log("qemu: Unsupported syscall: %d\n", num);
> >
> >
> >
> >
>
>
>
>
next prev parent reply other threads:[~2009-05-19 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 13:02 [Qemu-devel] [PATCH ] linux-user: add tee systemcall support vibisreenivasan
2009-05-19 8:12 ` vibi sreenivasan
2009-05-19 10:31 ` vibi sreenivasan
2009-05-19 11:36 ` Riku Voipio
2009-05-19 12:36 ` vibi sreenivasan [this message]
2009-05-20 14:24 ` Riku Voipio
2009-05-21 6:41 ` vibi sreenivasan
2009-05-21 15:38 ` Arnaud Patard
2009-05-22 5:31 ` vibi sreenivasan
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=1242736574.2188.32.camel@system \
--to=vibi_sreenivasan@cms.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).