From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] coretemp: fix reading of microcode revision
Date: Fri, 08 Oct 2010 12:44:12 +0000 [thread overview]
Message-ID: <20101008124412.GA24894@ericsson.com> (raw)
In-Reply-To: <4CADB0A1020000780001B335@vpn.id2.novell.com>
On Fri, Oct 08, 2010 at 08:33:22AM -0400, Henrique de Moraes Holschuh wrote:
[ ... ]
>
> The nasty thing about microcode revisions is that they can increase at any
> point in time (although we CAN get notified of it), but I don't think we
> ensure that they cannot go BACK after suspend/resume cycles.
>
Not sure if it would be worthwhile dealing with that. This sounds a lot like
"let's try to make the OS's life miserable", and you end up with a lot of
nasty code trying to deal with such situations. Next would be to try to verify
if the microcode is really the version it claims to be, or if someone hacked it.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-10-08 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 9:36 [lm-sensors] [PATCH] coretemp: fix reading of microcode revision Jan Beulich
2010-10-07 18:46 ` Fenghua Yu
2010-10-08 7:05 ` Jan Beulich
2010-10-08 8:22 ` Jean Delvare
2010-10-08 8:59 ` Jan Beulich
2010-10-08 12:33 ` Henrique de Moraes Holschuh
2010-10-08 12:34 ` [lm-sensors] [PATCH] coretemp: fix reading of microcode Henrique de Moraes Holschuh
2010-10-08 12:44 ` Guenter Roeck [this message]
2010-10-09 0:03 ` [lm-sensors] [PATCH] coretemp: fix reading of microcode revision Henrique de Moraes Holschuh
2010-10-09 18:44 ` [lm-sensors] [PATCH] coretemp: fix reading of microcode Guenter Roeck
2010-10-11 6:51 ` Jan Beulich
2010-10-11 12:40 ` Guenter Roeck
2010-10-11 15:13 ` Fenghua Yu
2010-10-11 23:07 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101008124412.GA24894@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.