netdev - Re: [PATCH net-next] ptp: Remove 'default y' for VMCLOCK PTP device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241104181927.05a9485a@kernel.org>
Date: Mon, 4 Nov 2024 18:19:27 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: David Woodhouse <dwmw2@...radead.org>
Cc: Richard Cochran <richardcochran@...il.com>, Peter Hilber
 <peter.hilber@...nsynergy.com>, linux-kernel@...r.kernel.org,
 virtualization@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
 linux-rtc@...r.kernel.org, "Ridoux, Julien" <ridouxj@...zon.com>,
 virtio-dev@...ts.linux.dev, "Luu, Ryan" <rluu@...zon.com>, "Chashper,
 David" <chashper@...zon.com>, "Mohamed Abuelfotoh, Hazem"
 <abuehaze@...zon.com>, Paolo Abeni <pabeni@...hat.com>, "Christopher S .
 Hall" <christopher.s.hall@...el.com>, Jason Wang <jasowang@...hat.com>,
 John Stultz <jstultz@...gle.com>, "Michael S . Tsirkin" <mst@...hat.com>,
 netdev@...r.kernel.org, Stephen Boyd <sboyd@...nel.org>, Thomas Gleixner
 <tglx@...utronix.de>, Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, Marc Zyngier
 <maz@...nel.org>, Mark Rutland <mark.rutland@....com>, Daniel Lezcano
 <daniel.lezcano@...aro.org>, Alessandro Zummo <a.zummo@...ertech.it>,
 Alexandre Belloni <alexandre.belloni@...tlin.com>, qemu-devel
 <qemu-devel@...gnu.org>, Simon Horman <horms@...nel.org>
Subject: Re: [PATCH net-next] ptp: Remove 'default y' for VMCLOCK PTP device

On Sat, 02 Nov 2024 16:52:17 -0500 David Woodhouse wrote:
> From: David Woodhouse <dwmw@...zon.co.uk>
> 
> The VMCLOCK device gives support for accurate timekeeping even across 
> live migration, unlike the KVM PTP clock. To help ensure that users can
> always use ptp_vmclock where it's available in preference to ptp_kvm,
> set it to 'default PTP_1588_CLOCK_VMCLOCK' instead of 'default y'.

Good enough for me, let's see if it's good enough for the main guy :)
Thanks!