From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Nested suspends; messages vs. states Date: Wed, 23 Mar 2005 22:54:16 +0100 Message-ID: <20050323215416.GK30704@elf.ucw.cz> References: <1111540913.16224.43.camel@gaston> <1111548664.16201.63.camel@gaston> <20050323210204.GE30704@elf.ucw.cz> <1111613750.14853.117.camel@desktop.cunningham.myip.net.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============38246863189304614==" In-Reply-To: <1111613750.14853.117.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces-qjLDD68F18O7TbgM5vRIOg@public.gmane.org Errors-To: linux-pm-bounces-qjLDD68F18O7TbgM5vRIOg@public.gmane.org To: Nigel Cunningham Cc: Linux-pm mailing list List-Id: linux-pm@vger.kernel.org --===============38246863189304614== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! > > There are many drivers that do not fit your idea of "driver". Like > > mtrrs. Some drivers only ever do work on resume, etc. Forcing driver > > to think how to split it into class->stop, bus->save_state and > > bus->enter state is bad idea. [Notice that almost no drivers need > > ->save_state operation...] > > I don't think MTRRs should be counted as drivers. Rather, they should be > counted as part of the CPU state(s), to be saved and restored when CPU > context is saved and restored. Treating them as drivers leads to races > :> Okay, I'll need to make cpu hotplug deal with them. But MTRR are not the only strange device. Think timer, for example. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! --===============38246863189304614== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============38246863189304614==--