Comments on: More on potential processor problems https://www.dragonflydigest.com/2007/06/29/more-on-potential-processor-problems/ A running description of activity related to DragonFly BSD. Fri, 29 Jun 2007 23:39:24 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Joe "Floid" Kanowitz https://www.dragonflydigest.com/2007/06/29/more-on-potential-processor-problems/comment-page-1/#comment-13155 Fri, 29 Jun 2007 23:39:24 +0000 http://www.shiningsilence.com/dbsdlog/index.php/2007/06/29/2312.html#comment-13155 Hmm. Addressed in the Slashdot thread, but:
“AE21 – The execution disable bit is shared between cores. I’m not sure what this means but Intel seems to think that it compromises an anti-hacker feature. Sounds pretty serious.”

I read this the same way as the AC did, and imagine this could be an issue for OSes offering some sort of workaround for legacy software that breaks with it enabled. Trying to let just one ‘trusted’ process live insecurely for its timeslice would inadvertently do the same for whatever’s running on the other CPU.

Modest practical risk, but ugly (workaround: only use one core) if anyone ever wanted to implement the above.

]]> By: from hades / und wieder mal der Core2Duo https://www.dragonflydigest.com/2007/06/29/more-on-potential-processor-problems/comment-page-1/#comment-13152 Fri, 29 Jun 2007 14:01:24 +0000 http://www.shiningsilence.com/dbsdlog/index.php/2007/06/29/2312.html#comment-13152 […] Matthew Dillon, der Chef von DragonFly BSD, gab seine Meinung diesbezüglich ab. Darum gings initial, klick. Post a comment — Trackback URI RSS 2.0 feed for these comments […]

]]>