From: Thiemo Seufer <ths@networkno.de>
To: "Kirill A. Shutemov" <k.shutemov@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] syscall readahead
Date: Fri, 23 Feb 2007 17:02:06 +0000 [thread overview]
Message-ID: <20070223170206.GD2521@networkno.de> (raw)
In-Reply-To: <20070219131651.GE25556@localhost.localdomain>
Kirill A. Shutemov wrote:
> Patch from Debian patchset in the attachment
> --- linux-user/syscall.c.orig 2006-11-05 07:07:19.000000000 +0200
> +++ linux-user/syscall.c 2006-11-05 07:07:25.000000000 +0200
> @@ -3947,7 +3956,8 @@ long do_syscall(void *cpu_env, int num,
> ret = get_errno(gettid());
> break;
> case TARGET_NR_readahead:
> - goto unimplemented;
> + ret = get_errno(readahead((int)arg1, (off64_t)arg2, (size_t)arg3));
> + break;
arg2 is a (off64_t *), I figure it needs locking.
Thiemo
prev parent reply other threads:[~2007-02-23 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 13:16 [Qemu-devel] [PATCH] syscall readahead Kirill A. Shutemov
2007-02-23 17:02 ` Thiemo Seufer [this message]
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=20070223170206.GD2521@networkno.de \
--to=ths@networkno.de \
--cc=k.shutemov@gmail.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).