Source-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[src/trunk]: src/sys/arch/xen/x86 xen/x86/cpu.c: Nix trailing whitespace.
details: https://anonhg.NetBSD.org/src/rev/0e1be6deacde
branches: trunk
changeset: 373723:0e1be6deacde
user: riastradh <riastradh%NetBSD.org@localhost>
date: Sat Feb 25 00:35:01 2023 +0000
description:
xen/x86/cpu.c: Nix trailing whitespace.
No functional change intended.
diffstat:
sys/arch/xen/x86/cpu.c | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
diffs (69 lines):
diff -r b8a008be863e -r 0e1be6deacde sys/arch/xen/x86/cpu.c
--- a/sys/arch/xen/x86/cpu.c Sat Feb 25 00:34:48 2023 +0000
+++ b/sys/arch/xen/x86/cpu.c Sat Feb 25 00:35:01 2023 +0000
@@ -1,4 +1,4 @@
-/* $NetBSD: cpu.c,v 1.144 2023/02/25 00:32:38 riastradh Exp $ */
+/* $NetBSD: cpu.c,v 1.145 2023/02/25 00:35:01 riastradh Exp $ */
/*-
* Copyright (c) 2000 The NetBSD Foundation, Inc.
@@ -65,7 +65,7 @@
*/
#include <sys/cdefs.h>
-__KERNEL_RCSID(0, "$NetBSD: cpu.c,v 1.144 2023/02/25 00:32:38 riastradh Exp $");
+__KERNEL_RCSID(0, "$NetBSD: cpu.c,v 1.145 2023/02/25 00:35:01 riastradh Exp $");
#include "opt_ddb.h"
#include "opt_multiprocessor.h"
@@ -521,7 +521,7 @@
(void *)pcb->pcb_rsp
#endif
);
-
+
}
#endif /* MPVERBOSE */
}
@@ -690,10 +690,10 @@
/*
* APs end up here immediately after initialisation and VCPUOP_up in
- * mp_cpu_start().
+ * mp_cpu_start().
* At this point, we are running in the idle pcb/idle stack of the new
* CPU. This function jumps to the idle loop and starts looking for
- * work.
+ * work.
*/
extern void x86_64_tls_switch(struct lwp *);
void
@@ -931,8 +931,8 @@
gdt_prepframes(frames, (vaddr_t)ci->ci_gdt, gdt_ents);
- /*
- * Initialise the vcpu context:
+ /*
+ * Initialise the vcpu context:
* We use this cpu's idle_loop() pcb context.
*/
@@ -1160,7 +1160,7 @@
/*
* pmap_cpu_init_late: perform late per-CPU initialization.
- *
+ *
* Short note about percpu PDIR pages. Both the PAE and __x86_64__ architectures
* have per-cpu PDIR tables, for two different reasons:
* - on PAE, this is to get around Xen's pagetable setup constraints (multiple
@@ -1170,7 +1170,7 @@
* (see cpu_load_pmap()).
*
* What this means for us is that the PDIR of the pmap_kernel() is considered
- * to be a canonical "SHADOW" PDIR with the following properties:
+ * to be a canonical "SHADOW" PDIR with the following properties:
* - its recursive mapping points to itself
* - per-cpu recursive mappings point to themselves on __x86_64__
* - per-cpu L4 pages' kernel entries are expected to be in sync with
Home |
Main Index |
Thread Index |
Old Index