From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BD96923A8 for ; Fri, 26 Jul 2024 13:04:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721999092; cv=none; b=Ha2Tpa6w57iL9GibOpv6mo9KGz3dhMk0ZluEwc7KukBg2KY6og1pYiDKtbSAAkgJLSzkPQBxWvq0F9eC6QTcBax9ed9gOWke4xgJ7POrku5t78yP0/7PvOCfwJKdoCiIah1i2Dy37oEik4lOD+BrtQSAl7S6pR+vqxrn0rjQalk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721999092; c=relaxed/simple; bh=uO12G0ckq47fIdqtlyWIWsBBD7gHquBqgoUXT4gDyT0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=DtQGZfI7ERXqf/iKgUFXJih2Hcq0XYGp3ws44tMrYmqXk8exutfAb4tspnlXWt1XsNXIUirbDqYXyN66soN24XsEf6gQW9eb6m7IMv0+JbiLZfWcq1pcv+0Vw791Me6/m1+qGlGorOmSOgnvTmnJ4T+DP7KDfz5/eOk5MKU5Fbw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=hGL8FSUL; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="hGL8FSUL" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1721999090; 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=B3g6QURrGZPYRxDC3Hx/i8519mXf108ro6Hrgt5KPqY=; b=hGL8FSULNU5z4NB+DXzdJZYqaz+t6j/sT7raZakvbU0pP9c0ZurfP+5Zcf5736qy6V6dzM diCvqxtNryEoeNstld7nVg3FRJzB7tq6EhCdtO+VgAE852UwHFr9ktm+uFsSObAuf9Qbw7 tcqiY/r1/y6O0iA71Qxi05B7cqTOHoQ= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-203-RvUtc-OANqqdIg_1hKAuGw-1; Fri, 26 Jul 2024 09:04:48 -0400 X-MC-Unique: RvUtc-OANqqdIg_1hKAuGw-1 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-36835f6ebdcso1543701f8f.1 for ; Fri, 26 Jul 2024 06:04:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721999087; x=1722603887; 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=B3g6QURrGZPYRxDC3Hx/i8519mXf108ro6Hrgt5KPqY=; b=WjFnkO2U6vlWbjs9LYSd9xeCmljJ63zwUdXPDLiFa0u7xzNyHNBnl7saaruMDlPJJV sAJL1Dtb1HQhLJ8VOJSK7MiisL6bNYTKaXntqNW0HNKOxab3LJilfVBzQn/Ufc0hgt/x FH3RttRM7LgjuUBomzkfqM0NdI9A+U48gdTe5RPaHMDE58zZWSLBUd2OAVvyvuKq1NHp rUGkPsyWXVBMphjOrXl4X8MT5egGWlsEUhWl42fijhDSqLAgvSuAbxa0IlAt4f7TPXIm x8yTVKRlXc5b4BfdQ9UCdWLP2+DkiO5aP73iupJg0ltH01jecgfvL46rCPsg26VY7mM7 Q4Gw== X-Forwarded-Encrypted: i=1; AJvYcCWQEKdDxyNEjKMKDBGpXcrhtTit60QwY5BFzme/oShpzgPXwqUafuyioNLGuuHzcvnjmKAaaDyK/yIksfEYAzfcbp4UPy2F X-Gm-Message-State: AOJu0Ywftw1kWmMOmkwts/Wcoq0hnRtnizE3x2Y2Zxvg9FybSUHa7O4h HfyqWIHoHKmxWepoKGu6ekDnyWflo5N88eRTWfClYj01hUPVRD877aVI1ZsCZ1z847cUMSFI5Rb eSRg1qGPMtNw8GdcE+OlBPQ27o84Pp8dPDdkQnH9XEQImDvgtKxW/+w== X-Received: by 2002:adf:f40e:0:b0:368:4ed7:2acc with SMTP id ffacd0b85a97d-36b3638148cmr3751288f8f.5.1721999087365; Fri, 26 Jul 2024 06:04:47 -0700 (PDT) X-Google-Smtp-Source: AGHT+IE2baiiVUKUBh/QT4ya/E9LOG3bE0mPK5t7EPOeVJPpQaN0mCePZ4SEB2ju0LD0SShA7ME5CA== X-Received: by 2002:adf:f40e:0:b0:368:4ed7:2acc with SMTP id ffacd0b85a97d-36b3638148cmr3751249f8f.5.1721999086564; Fri, 26 Jul 2024 06:04:46 -0700 (PDT) Received: from redhat.com ([2a02:14f:1f7:28ce:f21a:7e1e:6a9:f708]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-36b36801828sm5090963f8f.65.2024.07.26.06.04.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Jul 2024 06:04:46 -0700 (PDT) Date: Fri, 26 Jul 2024 09:04:38 -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: <20240726090326-mutt-send-email-mst@kernel.org> References: <20240725163843-mutt-send-email-mst@kernel.org> <20240725170328-mutt-send-email-mst@kernel.org> <20240725174327-mutt-send-email-mst@kernel.org> <9261e393083bcd151a017a5af3345a1364b3e0f3.camel@infradead.org> <20240726015613-mutt-send-email-mst@kernel.org> <2e427b102d8fd899a9a3db2ec17a628beb24bc01.camel@infradead.org> <20240726084836-mutt-send-email-mst@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Jul 26, 2024 at 02:00:25PM +0100, David Woodhouse wrote: > On Fri, 2024-07-26 at 08:52 -0400, Michael S. Tsirkin wrote: > > On Fri, Jul 26, 2024 at 09:35:51AM +0100, David Woodhouse wrote: > > > But for this use case, we only need a memory region that the hypervisor > > > can update. We don't need any of that complexity of gratuitously > > > interrupting all the vCPUs just to ensure that none of them can be > > > running userspace while one of them does an update for itself, > > > potentially translating from one ABI to another. The hypervisor can > > > just update the user-visible memory in place. > > > > Looks like then your userspace is hypervisor specific, and that's a > > problem because it's a one way street - there is no way for hypervisor > > to know what does userspace need, so no way for hypervisor to know which > > information to provide. No real way to fix bugs. > > It's not hypervisor specific, but you're right that as it stands there > is no negotiation of what userspace wants. So the hypervisor provides > what it feels it can provide without significant overhead (which may or > may not include the precise timekeeping, as discussed, but should > always include the disruption signal which is the most important > thing). > > The guest *does* know what the hypervisor provides. And when we get to > do this in virtio, we get all the goodness of negotiation as well. The > existence of the simple ACPI model doesn't hurt that at all. Maybe it doesn't, at that. E.g. virtio does a copy, acpi doesn't? I'll ponder compatibility over the weekend. -- MST