Actually, the best thing is what I did: I saw the bounce, and
forwarded using "correct" email addresses. After all, it is far
easier to repost, than to scramble after a breach.
The biggest point, is that the case has been submitted, and will
likely have no -1's by tomorrow, so Rafael should be able to proceed.
Next up is to get the 'turbo' kstat.
Cheers!
---- Randy
On Tue, 10 Feb 2009, Eric Saxe wrote:
> Yea, sorry about this Randy. If I open the floodgates and allow
> non-subscribers to post, then all sorts of unsavory spam begins to comes
> through.... ;) I'll see if I can add an exception for sac.sfbay...
>
> Thanks,
> -Eric
>
> Randy Fishel wrote:
> > Sorry, but this message has been bounced (often happens when I submit
> > cases via sac). So forwarding it instead. Should you choose to reply, use
> > the email addresses below (except use my 'randy.fishel at sun.com' address).
> >
> > Cheers!
> >
> > ---- Randy
> >
> > ---------- Forwarded message ----------
> > Date: Tue, 10 Feb 2009 20:04:56 -0800 (PST)
> > From: Randy Fishel <randyf at sac.sfbay.sun.com>
> > To: PSARC-ext at Sun.Com
> > Cc: Rafael.Vanoni at Sun.Com, tesla-dev at opensolaris.org
> > Subject: PowerTOP --cpu option [PSARC/2009/086 Self Review]
> >
> >
> > I am sponsoring the following self-review for Rafael Vanoni. It adds
> > an option to PowerTOP allowing behavior to be focused on a specific
> > cpu. As other options, the stability is "Uncommitted", and a release
> > binding of "Patch/Micro".
> >
> >
> > Template Version: @(#)sac_nextcase %I% %G% SMI
> > This information is Copyright 2009 Sun Microsystems
> > 1. Introduction
> > 1.1. Project/Component Working Name:
> > PowerTOP --cpu option
> > 1.2. Name of Document Author/Supplier:
> > Author: Rafael Vanoni
> > 1.3 Date of This Document:
> > 10 February, 2009
> > 4. Technical Description
> > Currently, PowerTOP observes power management related events on a
> > system wide basis. With the growing number of cores and processors in
> > today's system, it is sometimes desirable to observe the system in a finer
> > grained manner. This project introduces a new command line option that
> > allows the user to specify which core/processor he wishes to observe with
> > PowerTOP.
> >
> > The new option will focus all of PowerTOP's subwindows into the
> > specified processor. Therefore, presenting the processor's behavior in terms
> > of idle state and frequency level transitions, as well as reporting only
> > events that affect power management on that CPU. This new option can be
> > specified through the --cpu or -c option, and must be followed by a CPU id.
> > It can be used while specifying a time interval (-t), with dump mode (-d),
> > but not with verbose mode (-v).
> >
> > Proposed man page addition:
> >
> > OPTIONS
> >
> > -c [processor id]
> >
> > Specifies which CPU the tool should observe.
> >
> > EXAMPLES
> >
> > Example 4 Analyzing activity on a specific processor
> >
> > This command will run PowerTOP and only display data for CPU 3.
> >
> > % powertop -c 3
> >
> >
> > 6. Resources and Schedule
> > 6.4. Steering Committee requested information
> > 6.4.1. Consolidation C-team Name:
> > ON
> > 6.5. ARC review type: Automatic
> > 6.6. ARC Exposure: open
> >
> > _______________________________________________
> > tesla-dev mailing list
> > tesla-dev at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/tesla-dev
> >
