[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGM2rebkNJzNDieAJWR=xj9sr1TGJeqxabgBvbJBGELjyk6JRg@mail.gmail.com>
Date: Wed, 11 Jul 2018 23:12:43 -0400
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: tglx@...utronix.de
Cc: linux-kernel@...r.kernel.org, pbonzini@...hat.com,
rkrcmar@...hat.com, peterz@...radead.org, jgross@...e.com,
steven.sistare@...cle.com, daniel.m.jordan@...cle.com,
x86@...nel.org, kvm@...r.kernel.org
Subject: Re: [patch 7/7] x86/kvmclock: Switch kvmclock data to a PER_CPU variable
> /* Aligned to page sizes to match whats mapped via vsyscalls to userspace */
> #define HV_CLOCK_SIZE (sizeof(struct pvclock_vsyscall_time_info) * NR_CPUS)
HV_CLOCK_SIZE is not used anywhere anymore, can be deleted.
> +#define HVC_BOOT_ARRAY_SIZE \
> + (PAGE_SIZE / sizeof(struct pvclock_vsyscall_time_info))
This works, because sizeof(struct pvclock_vsyscall_time_info)) == 64
bytes, but static assert that verifies that IS_ALIGNED(PAGESIZE,
sizeof(struct pvclock_vsyscall_time_info)) would guarantee that no
random data is ever exposed to vdso.
Otherwise looks good to me:
Reviewed-by: Pavel Tatashin <pasha.tatashin@...cle.com>
Powered by blists - more mailing lists