Make cpu param to continue_hypercall_on_cpu() an unsigned integer.

Negative input makes no sense, and this makes the input range check
correct.

Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
This commit is contained in:
Keir Fraser committed 2010-04-15 09:04:45 +01:00
1 parent 0b8d217214
commit e6baf56c8c
2 files changed
+4 -2

No files matched your search

+2 -1
View File
@@ -943,7 +943,8 @@ static void continue_hypercall_tasklet_handler(unsigned long _info)
}
}
int continue_hypercall_on_cpu(int cpu, long (*func)(void *data), void *data)
int continue_hypercall_on_cpu(
unsigned int cpu, long (*func)(void *data), void *data)
{
struct migrate_info *info;
+2 -1
View File
@@ -64,7 +64,8 @@ bool_t domctl_lock_acquire(void);
void domctl_lock_release(void);
/* Continue the current hypercall via func(data) on specified cpu. */
int continue_hypercall_on_cpu(int cpu, long (*func)(void *data), void *data);
int continue_hypercall_on_cpu(
unsigned int cpu, long (*func)(void *data), void *data);
extern unsigned int xen_processor_pmbits;
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.