summaryrefslogtreecommitdiff
path: root/arch/um
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2020-12-15 12:52:21 +0300
committerRichard Weinberger <richard@nod.at>2021-02-12 23:21:17 +0300
commit74e919d2307d9014400c818b82e752c623a4da94 (patch)
treefadb1208cb03a2d1222f2b74f2d9676812d82fe7 /arch/um
parent92bf22614b21a2706f4993b278017e437f7785b3 (diff)
downloadlinux-74e919d2307d9014400c818b82e752c623a4da94.tar.xz
um: virtio: clean up a comment
There's no 'simtime' device, because implementing that through virtio was just too much complexity. Clean up the comment that still refers to it. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'arch/um')
-rw-r--r--arch/um/drivers/virtio_uml.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/um/drivers/virtio_uml.c b/arch/um/drivers/virtio_uml.c
index 5d957b7e7fd5..515d648d3c3d 100644
--- a/arch/um/drivers/virtio_uml.c
+++ b/arch/um/drivers/virtio_uml.c
@@ -914,8 +914,7 @@ static struct virtqueue *vu_setup_vq(struct virtio_device *vdev,
#ifdef CONFIG_UML_TIME_TRAVEL_SUPPORT
/*
* When we get an interrupt, we must bounce it through the simulation
- * calendar (the simtime device), except for the simtime device itself
- * since that's part of the simulation control.
+ * calendar (the time-travel=ext:... socket).
*/
if (time_travel_mode == TT_MODE_EXTERNAL && callback) {
info->callback = callback;