From nobody Sat Nov 30 10:49:56 2024 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (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 9FF7218FDC5; Tue, 10 Sep 2024 08:09:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1725955771; cv=none; b=fMb0YEwtvjmANiwbAdEaxJUgE4G0ZJKy/xDQDjxYEWK8FbXSGS6bT0i/rCJUgBsz1LJEtxVn77uGHHU4BnZEatupC5hZyPzY8BseWp44g+XReyiP4E4KArzmbICDUrCcPbYhXvdqI6+5uqGP/88GYP92Rla9uhNtZ09ydqZFHd8= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1725955771; c=relaxed/simple; bh=MkeYnlhdEESH2TrS9SFr8mlAOIX/Xz4Z/oUd5ak5aK8=; h=Date:From:To:Subject:Cc:In-Reply-To:References:MIME-Version: Message-ID:Content-Type; b=TuKkOTmtXeR/cQ55MTIU7nWE9q3Df7EP5kWoXWMmjIttX9SqF3zApJIznYetGQeZN/175U3cOfRjfZ/j4IcUUlDh9FPST2JrBW9UvYeNPbaztaXIi9IqrGMll33QSoShtMUFAhyiptoS9nGhTtAWgNdeHGX/IcAHxSM5koQ/Z1g= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=OuHGcLy/; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=mJdGdjCV; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="OuHGcLy/"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="mJdGdjCV" Date: Tue, 10 Sep 2024 08:09:21 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1725955762; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HN4Nw0VxFB1571u5uytu8fVnj0sR/WNHFCDs8jJ+bDw=; b=OuHGcLy/silFVyOrQn1qpNfyNVvdAdplmTG/FDRYR9sKn6Ac8zYk/MExW1W8NK6pA8gQmx LW9wyNFwS0L9fIAjDfQBcmg156/G9r9G2QSF52DMb54JeuMsGCC50aMcNqHnanKzw2EfQ7 BI4r8Dmlaqs0eXlx8PRVv77GneoVjNxALN3zcWK0CHsUnUrGF/SqR8fYJZRAUimhByB9Bw PXnKWILeFMeV3wtQ5h94KrusyToPJAxQAfHGs2oJdtuFC5FLms31kkTeC6T/6QANsrETYQ JyLC7HatPO0uJl5G9NUHrSIfJpvbpkBAv1fKAicB08jTNXqLvk593mIV8aiQGg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1725955762; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HN4Nw0VxFB1571u5uytu8fVnj0sR/WNHFCDs8jJ+bDw=; b=mJdGdjCVZE1wMqe7kqRlQxRhLa2Dspgt0E82XePbtHo5lDtpzEUthTaSdpcxYjKeBKQo2M kU6FyLADo5DdLaAA== From: "tip-bot2 for Christian Loehle" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: sched/core] sched/deadline: Clarify nanoseconds in uapi Cc: Christian Loehle , "Peter Zijlstra (Intel)" , Juri Lelli , "Rafael J. Wysocki" , x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20240813144348.1180344-3-christian.loehle@arm.com> References: <20240813144348.1180344-3-christian.loehle@arm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-ID: <172595576164.2215.5427726851322207167.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Precedence: bulk Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable The following commit has been merged into the sched/core branch of tip: Commit-ID: 478b58152034395024b692ea94af0d01810a6522 Gitweb: https://git.kernel.org/tip/478b58152034395024b692ea94af0d018= 10a6522 Author: Christian Loehle AuthorDate: Tue, 13 Aug 2024 15:43:46 +01:00 Committer: Peter Zijlstra CommitterDate: Tue, 10 Sep 2024 09:51:16 +02:00 sched/deadline: Clarify nanoseconds in uapi Specify the time values of the deadline parameters of deadline, runtime, and period as being in nanoseconds explicitly as they always have been. Signed-off-by: Christian Loehle Signed-off-by: Peter Zijlstra (Intel) Acked-by: Juri Lelli Acked-by: Rafael J. Wysocki Link: https://lore.kernel.org/r/20240813144348.1180344-3-christian.loehle@a= rm.com --- include/uapi/linux/sched/types.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/uapi/linux/sched/types.h b/include/uapi/linux/sched/ty= pes.h index 9066238..bf6e9ae 100644 --- a/include/uapi/linux/sched/types.h +++ b/include/uapi/linux/sched/types.h @@ -58,9 +58,9 @@ * * This is reflected by the following fields of the sched_attr structure: * - * @sched_deadline representative of the task's deadline - * @sched_runtime representative of the task's runtime - * @sched_period representative of the task's period + * @sched_deadline representative of the task's deadline in nanoseconds + * @sched_runtime representative of the task's runtime in nanoseconds + * @sched_period representative of the task's period in nanoseconds * * Given this task model, there are a multiplicity of scheduling algorithms * and policies, that can be used to ensure all the tasks will make their