Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp78472ybx; Wed, 6 Nov 2019 13:31:18 -0800 (PST) X-Google-Smtp-Source: APXvYqwSfIrttbGU3ynnBiKMlIWtFi2jAPA7hloPqGgPCdKARHzCVaXNOU9tyVefnjt4+m8V80C2 X-Received: by 2002:a50:ea8a:: with SMTP id d10mr4984357edo.97.1573075878357; Wed, 06 Nov 2019 13:31:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573075878; cv=none; d=google.com; s=arc-20160816; b=ON2b/K4NsamBSOniFL4MURnD6oOlODMBKOnsGD48IQMsjUWjyeQheNrBVdC7nAc7Qu HczBnHSzVwB7JBhjGRYio+BIG2Ajf/4v/cUZZYAXptD4ApkV31CnhNRpRVXzlBOJwANi oKjfq7Z44TWW5dD+TQBL6VFURTa2PoRhgaq75WrDSPzruXa7RzZ8d279nJ5YRFz0gv7S B6xnJNZ+bmTIotLx0a5vY0roOsFMnbAFgnXAecMMQycJ4vTs29BtL/ZEeb6b7vwE5yj3 aPN4ZxV31G4ttBT1yl2w5rpgcUSa7uYZKusc6MzcSpXrTo02zaIlemNzJan2tZ1H3IIG 2O/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=knGwZ6GzcAVtCpuWEw+en4nSuN2Psmr95qFaNmiviFU=; b=kk04XJTS+G+1xwscE/LK9Y/BSc+8WHiNj7B5TDXCTpjWSzxqD9leoXNA/tQA3e5Q7u qVaXumluIvAE4D5EWr1yBnvqt/2+DD7/fYrrlkcfAI97ZV7EVLSuyQppTcmcYwCeqW7m bsyd59Ei5ISaLUihj5i0jqPKWZRDGomtkBgfd3HoBrLSwyCZ3KUSuebq+N7P8HMjSx3G xoFrwk6hAktPPICBt5QFCI2KBvbM6P4VPkomNq4OX5G/3hr8ab/g4NrbiJbmazqepvuJ 9hLFgdZHwiYFyEAlrRPVoQ2tO4Q/XRMokXcq/bYJkQF0X/5KdgTsRw2pmqqQb9BdAm6e rSxg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id dd5si87221ejb.179.2019.11.06.13.30.53; Wed, 06 Nov 2019 13:31:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727559AbfKFV3i (ORCPT + 99 others); Wed, 6 Nov 2019 16:29:38 -0500 Received: from jabberwock.ucw.cz ([46.255.230.98]:56578 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726779AbfKFV3i (ORCPT ); Wed, 6 Nov 2019 16:29:38 -0500 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id 9B5A81C09B6; Wed, 6 Nov 2019 22:29:36 +0100 (CET) Date: Wed, 6 Nov 2019 22:29:21 +0100 From: Pavel Machek To: Keith Busch Cc: Guenter Roeck , Jens Axboe , Christoph Hellwig , Sagi Grimberg , linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, Akinobu Mita , linux-pm@vger.kernel.org, Chris Healy Subject: Re: [PATCH v2] nvme: Add hardware monitoring support Message-ID: <20191106212921.GA7020@amd> References: <20191029223214.18889-1-linux@roeck-us.net> <20191030005327.GC15332@redsun51.ssa.fujisawa.hgst.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <20191030005327.GC15332@redsun51.ssa.fujisawa.hgst.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > nvme devices report temperature information in the controller informati= on > > (for limits) and in the smart log. Currently, the only means to retrieve > > this information is the nvme command line interface, which requires > > super-user privileges. > >=20 > > At the same time, it would be desirable to use NVME temperature informa= tion > > for thermal control. > >=20 > > This patch adds support to read NVME temperatures from the kernel using= the > > hwmon API and adds temperature zones for NVME drives. The thermal subsy= stem > > can use this information to set thermal policies, and userspace can acc= ess > > it using libsensors and/or the "sensors" command. > >=20 > > Example output from the "sensors" command: > >=20 > > nvme0-pci-0100 > > Adapter: PCI adapter > > Composite: +39.0=B0C (high =3D +85.0=B0C, crit =3D +85.0=B0C) > > Sensor 1: +39.0=B0C > > Sensor 2: +41.0=B0C > >=20 > > Signed-off-by: Guenter Roeck >=20 > This looks fine to me, but I'll wait a few more days to see if there are > any additional comments.. User wants to know temperature of /dev/sda... and we already have an userspace tools knowing about smart, etc... pavel@amd:/data/film$ sudo hddtemp /dev/sda /dev/sda: ST1000LM014-1EJ164: 48=B0C I see we also have sensors framework but it does _not_ handle harddrive temperatures. Does it need some kind of unification? Should NVMe devices expose "SMART" information in the same way other SSDs do? Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAl3DOzEACgkQMOfwapXb+vIMvACfQ4av1AszPWgW7jbyZuTg6fmz a2EAoIkF7v4EygABLAACFFwF9dxY14dS =o7Jq -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT--