From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54303) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WwxDq-0000VT-Qs for qemu-devel@nongnu.org; Tue, 17 Jun 2014 13:31:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WwxDh-0000oY-Of for qemu-devel@nongnu.org; Tue, 17 Jun 2014 13:31:02 -0400 Received: from mail-qg0-x236.google.com ([2607:f8b0:400d:c04::236]:52935) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WwxDh-0000oQ-KQ for qemu-devel@nongnu.org; Tue, 17 Jun 2014 13:30:53 -0400 Received: by mail-qg0-f54.google.com with SMTP id q107so286837qgd.13 for ; Tue, 17 Jun 2014 10:30:53 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <53A07B49.5020600@redhat.com> Date: Tue, 17 Jun 2014 19:30:49 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1402505369-12526-1-git-send-email-pbonzini@redhat.com> <1402505369-12526-6-git-send-email-pbonzini@redhat.com> <53A07641.1080906@suse.de> In-Reply-To: <53A07641.1080906@suse.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 5/5] mc146818rtc: add "rtc" link to "/machine" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-15?Q?Andreas_F=E4rber?= , qemu-devel@nongnu.org Cc: mtosatti@redhat.com, stefanha@redhat.com Il 17/06/2014 19:09, Andreas Färber ha scritto: > Do those management apps want a generic location for each machine or > just for PC? For machines that implement the RTC_CHANGE event. > I know several ARM boards that have different ones on SoC > and on PMIC (I2C) for instance. In that case it may be safer to > implement an interface and to search for that? Possibly, but I'm not sure how management can know which types have an interface. If there are many clocks, they all *should* be based on rtc_clock and hopefully: - either only one sends RTC_CHANGE events (right now only the PC's RTC sends the event) - or the OS sets them to the same value when it modifies them, so they should have the same date property (but if not, one is as good as any other for the purpose of reconstructing lost RTC_CHANGE events). > Or at least give the > "rtc" node a more generic property type for ABI stability? I.e. you only > want "date" here, not any other properties of the mc146818rtc. The idea is to make a few selected properties "well-known" and link to them via aliases, in this case "date" from "/machine/rtc" is the well-known property. Paolo