cuda: fix off-by-one error in SET_TIME command
With the new framework the cuda_cmd_set_time command directly receive
the data, without the command byte. Therefore the time is stored at
in_data[0], not at in_data[1].
This fixes the "hwclock --systohc" command in a guest.
Cc: Hervé Poussineau <hpoussin@reactos.org>
Cc: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Reviewed-by: Hervé Poussineau <hpoussin@reactos.org>
[this fixes a regression introduced by e647317
"cuda: port SET_TIME
command to new framework"]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
This commit is contained in:
parent
92b674b62a
commit
ed3d807b0a
|
@ -685,8 +685,8 @@ static bool cuda_cmd_set_time(CUDAState *s,
|
|||
return false;
|
||||
}
|
||||
|
||||
ti = (((uint32_t)in_data[1]) << 24) + (((uint32_t)in_data[2]) << 16)
|
||||
+ (((uint32_t)in_data[3]) << 8) + in_data[4];
|
||||
ti = (((uint32_t)in_data[0]) << 24) + (((uint32_t)in_data[1]) << 16)
|
||||
+ (((uint32_t)in_data[2]) << 8) + in_data[3];
|
||||
s->tick_offset = ti - (qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL)
|
||||
/ NANOSECONDS_PER_SECOND);
|
||||
return true;
|
||||
|
|
Loading…
Reference in a new issue