[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100819170717.GA4312@ericsson.com>
Date: Thu, 19 Aug 2010 10:07:17 -0700
From: Guenter Roeck <guenter.roeck@...csson.com>
To: Fenghua Yu <fenghua.yu@...el.com>
CC: Rudolf Marek <r.marek@...embler.cz>,
Huaxu Wan <huaxu.wan@...el.com>, H Peter Anvin <hpa@...or.com>,
Chen Gong <gong.chen@...ux.intel.com>,
Jean Delvare <khali@...ux-fr.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
lm-sensors <lm-sensors@...sensors.org>
Subject: Re: [lm-sensors] [PATCH] drivers/hwmon/coretemp: Fix incorrect
hot-removed CPU's core sensor issue
On Wed, Aug 18, 2010 at 06:53:45PM -0400, Fenghua Yu wrote:
> From: Fenghua Yu <fenghua.yu@...el.com>
>
> In current coretemp driver, when a CPU in dev_list is hot-removed, although its
> HT sibling is still running, its core sensor is gone and not available to user
> level application any more.
>
> When a CPU is hot-removed, its core sensor should be still available to upper
> level application as long as the hot-removed CPU's HT sibling is still running.
> A core sensor is invisible to user level only when all of siblings in a core are
> hot-removed.
>
Isn't that just a short term (ie a couple of ms or even us) race condition
until the sibling is removed as well ? If so, why bother ?
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists