Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp1261438pxx; Fri, 30 Oct 2020 06:11:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz33TQDMK1nA3ypBNjRRlZ4qb7BPB4BKmOwA3mjIrPZQrL7Ms0cCCLCiWqrJ5vwmFFJ232B X-Received: by 2002:aa7:c984:: with SMTP id c4mr2229047edt.42.1604063463571; Fri, 30 Oct 2020 06:11:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1604063463; cv=none; d=google.com; s=arc-20160816; b=yLnVwEeB+oFkAhxcowNG96soWl8QoPIWJUePTHsw5TsqfhSFU+ewLUQS/gZD28Mvc6 DWzFvQKIGuKzrKvBKwkKNCw8e091x+vgTXdGPRrwMnhB4j+Fyfuq5K94IbVj8oC3vedZ UEAL0pSi4taGTfAtoEVt1OmbvJt/HI0R5gwAIVq7XbQsdCseMfb4iKnz79TeUiRfZ6iA A1OhmBIIVI8L13vQ5r64dxPLjD5D7Tk4xkcEe8B06pDHRxijLBOnkScPAvdas7OKx0k7 vMRKS5FW13aQDgjbZW4UyFGq7W+HZKgOmRtKkrkW26xGSuBb7UAInudLXvXlloqA11q8 L5KA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=XCaYMdTrl3RnP9DiH91VC3uvp6vlZ27bXHklu69/ezs=; b=tF0A9y7fkzRq9F3kvidTcrX2iUB4ngx0o9M/in9mTb3ekOHg+zhs4+b5yPeCWApklS dY2TjEOAYrbwvYWmyJGTTJ1WvY7T8ojTBjU4Tl5169JREC+2KZ1VHfD79ZYuUT9Fp7KY LsdVnTywayJRuVlQ/sVKdxbJGVA9fzbnvPoCqNIb8gt8++0xLuNo4vS6WfiZCFNwz4YS zkrjse8x4No8u1H+6taEXUM1EPedwHMvErLFdqIO3+X05IPdph8HzVsSpDC1KQ59hGp1 nyxjYG5aXpNT9WzjZahXmYbSFT7s6ajsi52Y/ml5xWp2BG9KzvsA1X4rHyfRiUDHWP9c mylA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=3ow5LXhQ; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n13si4186524eda.416.2020.10.30.06.10.40; Fri, 30 Oct 2020 06:11:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=3ow5LXhQ; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726536AbgJ3NIu (ORCPT + 99 others); Fri, 30 Oct 2020 09:08:50 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:42376 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725999AbgJ3NIt (ORCPT ); Fri, 30 Oct 2020 09:08:49 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1604063328; 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=XCaYMdTrl3RnP9DiH91VC3uvp6vlZ27bXHklu69/ezs=; b=3ow5LXhQS3wYOfqUW6gcHW9UDA0t4QduDNbdJXHWUuCAalcVAQJ7/Am1xpy9SBMTBYGAKU Ithm5j3jPDk5BKmVKm/88+Z+X3Iasi1ms5VQY57UFRNMxxl6g0swnXHWK8ztKs0N/GSdnT /UxLVweNxE1enula+FbXnzHUc1brhvZpSoc/dSiz83oxwP4yu8/6Eenpw9jJGp817EDk0k PP/swJmL5EYOG9f/fRj2bvJJvJ9Dr/NTAY69BsJFu0nRmWYOTC1NCekACn06yoOQVxfTwH XruxyZxExREl00yVFVxsIF+zahjdQ8Ztla3bXTQVvc0sOs62q2cYojzarAoZ6g== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1604063328; 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=XCaYMdTrl3RnP9DiH91VC3uvp6vlZ27bXHklu69/ezs=; b=hDdBeq3Hs6KfDQHzUMktWKE/YmSvKFFMVM8anc5fZJzJCW2ZKAj+noHlhL538R/RjgaGTe gdaDRqGepZubRnBQ== To: Lukasz Majewski , Andrei Vagin , Dmitry Safonov Cc: GNU C Library , Arnd Bergmann , linux-kernel@vger.kernel.org Subject: Re: [Y2038][time namespaces] Question regarding CLOCK_REALTIME support plans in Linux time namespaces In-Reply-To: <20201030110229.43f0773b@jawa> References: <20201030110229.43f0773b@jawa> Date: Fri, 30 Oct 2020 14:08:48 +0100 Message-ID: <871rhfoo7z.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Lukasz, On Fri, Oct 30 2020 at 11:02, Lukasz Majewski wrote: > I do have a question regarding the Linux time namespaces in respect of > adding support for virtualizing the CLOCK_REALTIME. > > According to patch description [1] and time_namespaces documentation > [2] the CLOCK_REALTIME is not supported (for now?) to avoid complexity > and overhead in the kernel. > > Is there any plan to add support for it in a near future? Not really. Just having an offset on clock realtime would be incorrect in a number of ways. Doing it correct is a massive trainwreck. For a debug aid, which is what you are looking for, the correctness would not really matter, but providing that is a really slippery slope. If at all we could hide it under a debug option which depends on CONFIG_BROKEN and emitting a big fat warning in dmesg with a clear statement that it _is_ broken, stays so forever and any attempt to "fix" it results in a permanent ban from all kernel lists. Preferrably we don't go there. Thanks, tglx