Good question. I was thinking about documenting what modes each platforms supports and if a non supported mode is used log a message that it is not supported :). Might be, it is better to have the 4 modes as Eric suggested and "cpupm enable" will default to either "event-mode" or "polling-mode" based on the platform. In this case too, if a non supported mode is used might have to log a message.
Anup On 10/10/08 13:30, Bill Holler wrote: > This does not specify what happens if a platform does not support > the specified mode? For example "enable-event-mode" on a SPARC > platform. Will this default to "enable"? > > Bill > > > On 10/10/08 12:16, bugzilla-daemon at defect.opensolaris.org wrote: > >> http://defect.opensolaris.org/bz/show_bug.cgi?id=3838 >> >> >> >> >> >> --- Comment #1 from Anup <napanda.pemmaiah at sun.com> 2008-10-10 12:16:49 >> --- >> Eric, >> >> It sounds good. Had couple of comments/questions to make myself clear. >> >> 1) event-mode will only exist for x86 right? If that is the case, by default >> "cpupm enable" for x86 will be event mode and for sparc it will be >> "polled-mode". Does that make sense? >> >> 2) If "polled-mode" has to be used, then I assume "cpupm enable" has to be >> replaced by "cpupm polled-mode". >> >> 3) Instead of having 4 behaviors, How about having three. >> >> a)enable-event-mode >> b) enable-polling-mode >> c)disable >> >> x86 will support all the three and sparc supports just 'b' and 'c'. Just my >> thoughts. >> >> Thanks >> Anup >> >> >> > > _______________________________________________ > tesla-dev mailing list > tesla-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/tesla-dev > -- Anup Pemmaiah Sun Microsystems -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/tesla-dev/attachments/20081010/ea1dc2d5/attachment.html>
