[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090605110627.GH4421@prithivi.gnumonks.org>
Date: Fri, 5 Jun 2009 13:06:27 +0200
From: Harald Welte <HaraldWelte@...tech.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "Michael S. Zick" <lkml@...ethan.org>,
Duane Griffin <duaneg@...da.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: VIA PowerSaver (Re: Linux 2.6.30-rc8 [also: VIA Support])
Hi Linus and Michael,
On Thu, Jun 04, 2009 at 10:46:00AM -0700, Linus Torvalds wrote:
> On Thu, 4 Jun 2009, Michael S. Zick wrote:
> >
> > Yes, I build test cases with and without - -
> > It was a fixed-speed kernel build that first hit the 4 hour up-time mark.
> > I just reposted that build today (the -09143lk).
> >
> > > Features like that easily put a huge stress on power regulators etc, if
> > > they result in sudden changes in current draw. Underspecced capacitors
> > > etc can cause CPU "brown-outs", which in turn can easily cause total
> > > failure.
> >
> > There is also a possible thermal issue with these machines - -
> > I doubt that VIA runs their qualification testing in bake ovens;
> > which is what NetBook cases amount too. ;)
>
> If the fixed-speed case runs for longer, it's not likely to be a thermal
> issue. The fixed speed case should be the higher-power one.
>
> So it can easily be a weak power setup (insufficient grounding, bad
> capacitors etc). But it could also be external bus issues, in case VIA
> power management also impact the external bus (eg "stopclock" like
> behavior on the CPU<->chipset bus).
I'm not intending to disagree with you, I just wanted to quote from
a not [yet] public document on the C7-M. This quote describes model A
(family 6, model 10(hex A), stepping 0-15):
===============
Enhanced PowerSaver technology allows the dynamic adjustment of the operating
frequency and operating voltage. The VIA C7-M can only change from the
highest supported performance state to the lowest supported performance state:
intermediate performance states are not guaranteed to work and are not offi-
cially supported. System software can use Enhanced PowerSaver to request the
sufficient amount of performance. Each individual performance state (P-State)
is described in the system bios according to 8.4.4 of the ACPI 3.0
specification.
The VIA C7-M processor incorporates two on-chip core clock PLLs. This allows
the processor to ping-pong between two frequencies instantaneously. In the
simplest scenario, where there are only two clock frequencies of interest and
no voltage changes, the transition can be instantaneous with no latency. In
more complex scenarios, where there are multiple clock frequencies of interest,
the "old" frequency can continue to be used while the new frequency is ramped
up. The transition is still instantaneous from a software point of view (code
still executes), but there is a latency associated with switching to the ramp-
ing "new" frequency.
VIA C7-M allows for a clean hardware approach to processor operating point
transitions. The transitions are performed instantaneously from a software and
functional point of view. Snoops and interrupts, for example, are unaffected by
transitions.
===============
A C7-M model D (family 6, model 13(hex D), stepping 0-15) has advanced performance
states, they use an inflection ratio, as well as adaptive-p-state control and
adaptive overclocking, as well as iteravie P-state transitions and adaptive
thermal control. I'm not yet aware of all the details, but have requested them.
In any case, the problems that have been reported by Michael were "Model A",
so those particular deatils shouldn't matter at this point.
Regards,
--
- Harald Welte <HaraldWelte@...tech.com> http://linux.via.com.tw/
============================================================================
VIA Free and Open Source Software Liaison
--
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