lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10398431.HfgFiK9AG8@vostro.rjw.lan>
Date:	Thu, 20 Jun 2013 00:50:44 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Xiaoguang Chen <chenxg.marvell@...il.com>
Cc:	Viresh Kumar <viresh.kumar@...aro.org>,
	Xiaoguang Chen <chenxg@...vell.com>, cpufreq@...r.kernel.org,
	linux-pm@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	njiang1@...vell.com, zjwu@...vell.com, ylmao@...vell.com
Subject: Re: [PATCH v5] cpufreq: fix governor start/stop race condition

On Wednesday, June 19, 2013 11:26:13 AM Xiaoguang Chen wrote:
> 2013/6/19 Viresh Kumar <viresh.kumar@...aro.org>:
> > On 19 June 2013 08:43, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> >> On 19 June 2013 06:50, Xiaoguang Chen <chenxg.marvell@...il.com> wrote:
> >>> 2013/6/19 Rafael J. Wysocki <rjw@...k.pl>:
> >>
> >>>>> 2) Current governor is userspace, now cpu0 hotplugs in cpu3, it will
> >>>>
> >>>> Can you please tell me what the above is supposed to mean?  Is it supposed to
> >>>> mean "the online of cpu3 is being run on cpu0" or something different?  If
> >>>> something different, then what?
> 
> Sorry I missed this question, Let me explain it in detail
> Suppose we are in such condtition, current cpufreq goveror is
> userspace governor. cpu3 is offline.
> and two things happen as above two cases, first thing is application
> tries to change current governor to ondemand governor,
> second thing is cpu0 tries to make cpu3 online which is off line
> before. both of these two cases will try to stop current governor and
> start a governor. if above two things interleave, unexpected behavior
> will happen.

Now it's clear, thanks for the explanation.  [Well, I'll still need to fix up
the changelog.  Sigh.]

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ