rototiller: pass num_cpus to .create_context()

Back in the day, there was no {create,destroy}_context(), so passing
num_cpus to just prepare_frame made sense.  Modules then would
implicitly initialize themselves on the first prepare_frame() call
using a static initialized variable.

Since then things have been decomposed a bit for more sophisticated
(and cleaner) modules.  It can be necessary to allocate per-cpu data
structures and the natural place to do that is @ create_context().  So
this commit wires that up.

A later commit will probably have to plumb a "current cpu" identifier
into the render_fragment() function.  Because a per-cpu data structure
isn't particularly useful if you can't easily address it from within
your execution context.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/modules/ray/ray.c b/src/modules/ray/ray.c
index c0c067e..99e6609 100644
--- a/src/modules/ray/ray.c
+++ b/src/modules/ray/ray.c
@@ -124,7 +124,7 @@ typedef struct ray_context_t {
 } ray_context_t;
 
 
-static void * ray_create_context(void)
+static void * ray_create_context(unsigned num_cpus)
 {
 	return calloc(1, sizeof(ray_context_t));
 }