Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by rbanffy on Wednesday January 03, 2018 @04:41PM
(#16065473)
If your workload has no code that's untrusted, you can safely skip this patch or disable it on boot. If not, at 2000+ physical machines, it may be worth to move some of that into kernel modules that would collapse a couple syscalls into a single higher level one.
[ Parent
| on HN ]
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by ufo on Wednesday January 03, 2018 @09:20PM
(#16067460)
The VM host will still have the patch applied, won't it?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by rbanffy on Thursday January 04, 2018 @05:26AM
(#16069229)
Yes, but if it's your metal, you don't need to.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by dijit on Thursday January 04, 2018 @04:11AM
(#16068946)
Good idea. But it’s a windows executable and depends quite heavily on windows specifics.
(In my case anyway)
30% overhead might be inscentive to revisit the assumption we can’t rewrite it for Linux.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by rbanffy on Thursday January 04, 2018 @05:29AM
(#16069240)
You still can move some functionality to a device driver or something else that runs in the NT kernel space.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by rogerthis on Wednesday January 03, 2018 @08:06PM
(#16067095)
But then you have to release the module as GPL, no?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by lmm on Thursday January 04, 2018 @07:01AM
(#16069685)
Only if you want to do something that would otherwise be a violation of copyright - e.g. distribute the module to other people (assuming it's sufficiently entangled with linux to be a derivative work therof). The GPL only licenses you to do things that you otherwise couldn't do, it doesn't restrict you from doing things that were never a violation of copyright (e.g. privately modifying your own things).
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch...
by KingMachiavelli on Wednesday January 03, 2018 @09:44PM
(#16067575)
No kernel modules can be closed source; GPU drivers are a common example of a closed source kernel module.