[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1196983219370-git-send-email-zach.brown@oracle.com>
Date: Thu, 6 Dec 2007 15:20:17 -0800
From: Zach Brown <zach.brown@...cle.com>
To: linux-kernel@...r.kernel.org
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Ulrich Drepper <drepper@...hat.com>,
Arjan van de Ven <arjan@...radead.org>,
Andrew Morton <akpm@....com.au>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
"David S. Miller" <davem@...emloft.net>,
Suparna Bhattacharya <suparna@...ibm.com>,
Davide Libenzi <davidel@...ilserver.org>,
Jens Axboe <jens.axboe@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Dan Williams <dan.j.williams@...il.com>,
Jeff Moyer <jmoyer@...hat.com>,
Simon Holm Thogersen <odie@...aau.dk>,
suresh.b.siddha@...el.com
Subject: [PATCH 4/6] syslets: add indirect args
This adds the syslet indirect args to the indirect_params union.
This is broken, but it lets us simply demonstrate the rest of the syslet
universe around the indirect argument passing convention.
A caller could well want to perform a syscall that uses indirect arguments as a
syscall. Maybe we turn indirect_params into a struct that contains a union for
arguments which can never be used concurrently. This needs wider discussion.
Signed-off-by: Zach Brown <zach.brown@...cle.com>
diff --git a/include/linux/indirect.h b/include/linux/indirect.h
index 97f9ac4..5d5abd7 100644
--- a/include/linux/indirect.h
+++ b/include/linux/indirect.h
@@ -3,6 +3,7 @@
#define _LINUX_INDIRECT_H
#include <asm/indirect.h>
+#include <linux/syslet-abi.h>
/* IMPORTANT:
@@ -14,6 +15,7 @@ union indirect_params {
struct {
int flags;
} file_flags;
+ struct syslet_args syslet;
};
#define INDIRECT_PARAM(set, name) current->indirect_params.set.name
--
1.5.2.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists