[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191030140511.GA14252@lst.de>
Date: Wed, 30 Oct 2019 15:05:11 +0100
From: Christoph Hellwig <hch@....de>
To: Akinobu Mita <akinobu.mita@...il.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
LKML <linux-kernel@...r.kernel.org>,
linux-nvme@...ts.infradead.org,
Linux PM <linux-pm@...r.kernel.org>,
Chris Healy <cphealy@...il.com>
Subject: Re: [PATCH v2] nvme: Add hardware monitoring support
On Wed, Oct 30, 2019 at 08:16:48PM +0900, Akinobu Mita wrote:
> The nvme_init_identify() can be called multiple time in nvme ctrl's
> lifetime (e.g 'nvme reset /dev/nvme*' or suspend/resume paths), so
> should we need to prevent nvme_hwmon_init() from registering hwmon
> device more than twice?
>
> In the nvme thermal zone patchset[1], thernal zone is registered in
> nvme_init_identify and unregistered in nvme_stop_ctrl().
So Guenter said above the thermal subsystem could use the information
from hwmon as well. Does this mean this patch would solve your needs
as well?
Powered by blists - more mailing lists