All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Add fadvise64 stubs
Date: Fri, 19 Sep 2008 16:33:13 +0300	[thread overview]
Message-ID: <20080919133313.GA19874@kos.to> (raw)

Since these are only hints, we happily fake them for now
to make applications not barf on ENOSYS.

Signed-off-by: Riku Voipio <riku.voipio@iki.fi>
---
 linux-user/syscall.c |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 4cde5e8..8e6e735 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -5576,6 +5576,18 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
     case TARGET_NR_mincore:
         goto unimplemented;
 #endif
+#ifdef TARGET_NR_fadvise64_64
+     case TARGET_NR_fadvise64_64:
+        /* This is a hint, so ignoring and returning success is ok.  */
+        ret = get_errno(0);
+        break;
+#endif
+#ifdef TARGET_NR_arm_fadvise64_64
+     case TARGET_NR_arm_fadvise64_64:
+        /* This is a hint, so ignoring and returning success is ok.  */
+        ret = get_errno(0);
+        break;
+#endif
 #ifdef TARGET_NR_madvise
     case TARGET_NR_madvise:
         /* A straight passthrough may not be safe because qemu sometimes
-- 
1.5.6.5


-- 
"rm -rf" only sounds scary if you don't have backups

             reply	other threads:[~2008-09-19 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 13:33 Riku Voipio [this message]
2008-09-19 13:52 ` [Qemu-devel] [PATCH] Add fadvise64 stubs Kirill A. Shutemov
2008-09-20 18:26   ` [Qemu-devel] " Riku Voipio
2008-09-20 18:41     ` Kirill A. Shutemov
2008-09-20 18:51     ` [Qemu-devel] " Kirill A. Shutemov
2008-09-20 19:01       ` [Qemu-devel] " Riku Voipio
2008-10-01 21:49       ` [Qemu-devel] " Aurelien Jarno
  -- strict thread matches above, loose matches on Subject: below --
2008-10-01 13:56 Kirill A. Shutemov

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=20080919133313.GA19874@kos.to \
    --to=riku.voipio@iki.fi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.