From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 13F63C3DA49 for ; Thu, 25 Jul 2024 05:55:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:In-Reply-To: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Dh3yyuBj9HXf2A5cEfYqf0NaFgetwfgWSnefr6wKli8=; b=ttxmz2l7AaaItx9mwX7etE3nGZ PV9Qz4saFBvc81K5sBwuVZCdMZymt8uZpie2vKs27bsvhZI1ZulMRpEeH3lEVLJti6J7bYNwECdLs GA+KHyTiEkSXf2ra5acVwyGeWVcCQlI9UwMX35Nyx7XMJ0J6YiEJVsDkxF5NgMzsoZEI83TQiHfo0 jql8RUs1zkVyy9PTvB+zNtr9GG/3MCWjIo7f+Lwg8KoEOjRN2zbZtgt4pErjW3KmBgXM7zkPr137S o3Vwxk+H7ay958Nzy4CAVtYTMe9b9r+U60pLCtjhp7P8mwYNJrZ0OsABc9F3iwGSMeBHtcM4a34My e5mEVzjw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sWrRD-0000000HVwH-2atO; Thu, 25 Jul 2024 05:54:51 +0000 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sWrQo-0000000HVnt-12iv for linux-arm-kernel@lists.infradead.org; Thu, 25 Jul 2024 05:54:27 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1721886865; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Dh3yyuBj9HXf2A5cEfYqf0NaFgetwfgWSnefr6wKli8=; b=QCYG7z6QMAhKm0o4TMDKNIQT4pxdvUxgU7v8opdjOSVyUbA9p9naW2XDVM4mv7UswTacgv G1RI/amt6XV5LXDANwedi1OODPQJbD83mIiLVlpjujQsPGAPZ1eg3aVNZruEUaPBeTKsfN PdqCfAtHS/UbqO2E+20PsQp8Y2ox2qY= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-590-RR9TpbyXPzORkZUCaTPKlw-1; Thu, 25 Jul 2024 01:54:21 -0400 X-MC-Unique: RR9TpbyXPzORkZUCaTPKlw-1 Received: by mail-wr1-f70.google.com with SMTP id ffacd0b85a97d-3679ab94cdbso334501f8f.3 for ; Wed, 24 Jul 2024 22:54:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721886860; x=1722491660; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Dh3yyuBj9HXf2A5cEfYqf0NaFgetwfgWSnefr6wKli8=; b=ddfapXzFaKSsFRSFVmprJ0yP/NuBT3DPbMcd/Zv2QQVnY52Ubvx/hDc/NPlPCY2LM5 zg0lku2dSGpqjK0665vTVaeRD+M84C021TXOI/JOnSFfoNg4T3v1GAjbAXRkmeJ/x4kn 4zMgfy0J/GLmcmLFvwE8szauPp2g9/+RX78K4KEzWWLiYi6wR333DcIsNohe7hWhJIH9 6zs9XvvBDUzvgQ6PA9nYT2+Imm7sdMiLLsWfXD3sF3MTwF+QTcyLxZYH70VrKgdAAyHk FHCUn+0TyuzWZV1Hi//XcLccqXwYr0H5IsNRKm2tF8JQN7syyxc4oxqMw71CEuonCY1S qZ7w== X-Forwarded-Encrypted: i=1; AJvYcCWJTsO/mDIEK3f079MY+Z468XLGIyXxfDPCT8mhFqsfg6c1UmGnuAHO0Xh4Nu6xv4q8+OoRLSnaalJjGcRGGA6J4OuvWq/QaTq63JWaU+Hft0+ZMhI= X-Gm-Message-State: AOJu0YxlWBHEVKCTVEHReT34eNEKslR2gr5SgtHxZN+CzrVGbeXf+K23 RchUReU09OkjbePvYDpFdFJPPykun/2j8smscqstx+c9n/HF0L2C5LFGFccHg8BKMBEPC49EIgc YSoTC7+Q6KYbjE3t5KgQpbVlxnzuo/2HKRsJhtffuKU5VQ/g1A4uVxyvFVKP/eLB1Ox78//o/ X-Received: by 2002:a05:6000:1942:b0:368:3038:8290 with SMTP id ffacd0b85a97d-36b36421ac8mr707593f8f.39.1721886860524; Wed, 24 Jul 2024 22:54:20 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHI3Abal444WmsilGMojUOB9llheQDVQUaMgG30HCOZkmwXntXo9Fy/JkeXGpR8m6xgr9AF9A== X-Received: by 2002:a05:6000:1942:b0:368:3038:8290 with SMTP id ffacd0b85a97d-36b36421ac8mr707561f8f.39.1721886859582; Wed, 24 Jul 2024 22:54:19 -0700 (PDT) Received: from redhat.com ([2a02:14f:1ed:8427:35e3:731c:3106:ee46]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-36b36857dcesm900105f8f.85.2024.07.24.22.54.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 24 Jul 2024 22:54:18 -0700 (PDT) Date: Thu, 25 Jul 2024 01:54:10 -0400 From: "Michael S. Tsirkin" To: David Woodhouse Cc: Richard Cochran , Peter Hilber , linux-kernel@vger.kernel.org, virtualization@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-rtc@vger.kernel.org, "Ridoux, Julien" , virtio-dev@lists.linux.dev, "Luu, Ryan" , "Chashper, David" , "Mohamed Abuelfotoh, Hazem" , "Christopher S . Hall" , Jason Wang , John Stultz , netdev@vger.kernel.org, Stephen Boyd , Thomas Gleixner , Xuan Zhuo , Marc Zyngier , Mark Rutland , Daniel Lezcano , Alessandro Zummo , Alexandre Belloni , qemu-devel , Simon Horman Subject: Re: [PATCH] ptp: Add vDSO-style vmclock support Message-ID: <20240725015120-mutt-send-email-mst@kernel.org> References: <14d1626bc9ddae9d8ad19d3c508538d10f5a8e44.camel@infradead.org> MIME-Version: 1.0 In-Reply-To: <14d1626bc9ddae9d8ad19d3c508538d10f5a8e44.camel@infradead.org> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240724_225426_363680_BCF6D12C X-CRM114-Status: GOOD ( 17.68 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Jul 24, 2024 at 06:16:37PM +0100, David Woodhouse wrote: > From: David Woodhouse > > The vmclock "device" provides a shared memory region with precision clock > information. By using shared memory, it is safe across Live Migration. > > Like the KVM PTP clock, this can convert TSC-based cross timestamps into > KVM clock values. Unlike the KVM PTP clock, it does so only when such is > actually helpful. > > The memory region of the device is also exposed to userspace so it can be > read or memory mapped by application which need reliable notification of > clock disruptions. > > Signed-off-by: David Woodhouse one other thing worth mentioning is that this design can't work with confidential computing setups. By comparison, mapping e.g. a range in a PCI BAR would work for these setups. Is there a reason this functionality is not interesting for confidential VMs? -- MST