Jump to content

My take on Intel refuse to patch the bug.

Apparently we all know that intel Chips (all the modern chips that are produced in the last 10 years) have a bug that skips some security checks to improve performance. Basically it checks 999 out of 1000 checks to save time so it can improve performance. Fixing this can cause intel Chips to slowdown as much as 35% And apparently intel is refusing to fix it via a bios update. 
 
So yea intel is refusing to fix the bug saying it cannot be fixed by a bios update and can only be fixed via a software OS level update. The solution is a kernel table isolation patch which separates the kernel memory from the user processes providing kernel overhead. This unfortunately will results in slowing down the system by as much as 35% (5% ~ 35%)
 
My take on this is, this bug can be fixed via a simple bios update and intel is only refusing to do that is cause then the only systems that are effected by this will be intel CPU's, apparently we all know that AMD does not suffer from this bug but a os level update can and will bring down the AMD systems along with Intel systems. 
 
I think intel is deliberately doing this so as to bring down AMD along with it. 

Microsoft in there infinite wisdom have decided to impose a VRAM cap for games the that use DX9 o.O. May God Bless them those whoever came up with that idea. :dry:

 

You're looking for something that does not, has not, will not, might not or must not exist ... ... but you're always welcome to search for it. 

 

Link to comment
Share on other sites

Link to post
Share on other sites

AMD has opted out of being targeted by the patches that are being ported to Linux to patch this bug. 

 

One would assume that they've done the same for Windows as well. 

 

This really deserves to be on the thread for this topic in Tech News, not as a separate thread. 

idk

Link to comment
Share on other sites

Link to post
Share on other sites

 

Watch this video through.

Link to comment
Share on other sites

Link to post
Share on other sites

5 minutes ago, DeadlyTitan said:

35% (5% ~ 35%)

I've more or less only heard of this today but its only effecting certain tasks, no?  Not the rntire system.

Want to custom loop?  Ask me more if you are curious

 

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Damascus said:

I've more or less only heard of this today but its only effecting certain tasks, no?  Not the rntire system.

Mostly I/O and Memory based tasks. 

 

IO is by far where it hits the hardest. 

idk

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, Droidbot said:

Mostly I/O and Memory based tasks. 

 

IO is by far where it hits the hardest. 

Could you do a quick explain like I'm 5 for this situation? Just woke up and haven't had my coffee yet.

Want to custom loop?  Ask me more if you are curious

 

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Damascus said:

I've more or less only heard of this today but its only effecting certain tasks, no?  Not the rntire system.

That depends, but it's going to effect I/O tasks and networking, requesting and accepting data. Its still unknown as of how this is going to effect normal person who just uses it to play games and watch youtube but well video encoding, sound processing, running virtual machines and other such stuff are going to take a hit. 

 

5 minutes ago, Droidbot said:

AMD has opted out of being targeted by the patches that are being ported to Linux to patch this bug. 

 

One would assume that they've done the same for Windows as well. 

 

This really deserves to be on the thread for this topic in Tech News, not as a separate thread. 

Well lets hope they did, i myself have personally bought an Intel CPU so its not like i am rooting for AMD.  But its wrong like punishing an innocent for a crime he have not done. Also am pretty new to forums so apologizes for posting it on wrong topic if i did 

Microsoft in there infinite wisdom have decided to impose a VRAM cap for games the that use DX9 o.O. May God Bless them those whoever came up with that idea. :dry:

 

You're looking for something that does not, has not, will not, might not or must not exist ... ... but you're always welcome to search for it. 

 

Link to comment
Share on other sites

Link to post
Share on other sites

12 minutes ago, DeadlyTitan said:
And apparently intel is refusing to fix it via a bios update.

No they aren't. It's not a bug that can be fixed with a microcode-update.

Hand, n. A singular instrument worn at the end of the human arm and commonly thrust into somebody’s pocket.

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, WereCatf said:

No they aren't. It's not a bug that can be fixed with a microcode-update.

Well am sure it can be. I am an application developer and when something can be fixed via OS level patch then am sure as hell that it can be fixed with a microcode update. 

Microsoft in there infinite wisdom have decided to impose a VRAM cap for games the that use DX9 o.O. May God Bless them those whoever came up with that idea. :dry:

 

You're looking for something that does not, has not, will not, might not or must not exist ... ... but you're always welcome to search for it. 

 

Link to comment
Share on other sites

Link to post
Share on other sites

14 minutes ago, DeadlyTitan said:
Apparently we all know that intel Chips (all the modern chips that are produced in the last 10 years) have a bug that skips some security checks to improve performance. Basically it checks 999 out of 1000 checks to save time so it can improve performance. Fixing this can cause intel Chips to slowdown as much as 35% And apparently intel is refusing to fix it via a bios update. 
 
So yea intel is refusing to fix the bug saying it cannot be fixed by a bios update and can only be fixed via a software OS level update. The solution is a kernel table isolation patch which separates the kernel memory from the user processes providing kernel overhead. This unfortunately will results in slowing down the system by as much as 35% (5% ~ 35%)
 
My take on this is, this bug can be fixed via a simple bios update and intel is only refusing to do that is cause then the only systems that are effected by this will be intel CPU's, apparently we all know that AMD does not suffer from this bug but a os level update can and will bring down the AMD systems along with Intel systems. 
 
I think intel is deliberately doing this so as to bring down AMD along with it. 

Looking to raise your posts count? There is already a topic on the tech news where you could've wrote down your take and maybe read some of the replies and see that it cannot be solved through a bios update.

CPU: Ryzen 7 2700x, Cooling: Corsair H100i Platinum AIO MOBO: Asus Strix B450 F GPU: Gigabyte GTX 1080 Founders Edition + Arctic Accelero Xtreme III RAM: 2x8GB ThermalTake ToughRAM White 3200MHz PSU: Corsair RM850x White Storage: 250GB Samsung 970 Evo NVMe CASE: Corsair 275r Airflow White OTHER: White and Orange Cable Extensions ---- MONITOR: Samsung LC32JG5 32" WQHD 1440p VA 144Hz

Link to comment
Share on other sites

Link to post
Share on other sites

8 minutes ago, Damascus said:

Could you do a quick explain like I'm 5 for this situation? Just woke up and haven't had my coffee yet.

Screenshot_2018-01-03-13-16-06-951_com.emogoth.android.phone_mimi.png.d8db68ddf9920ef92e3424cc7d2ddf04.png

 

this is from /g/ and it sums it up pre well

idk

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Droidbot said:

this is from /g/ and it sums it up pre wel

Any reason to just not patch It?

I just went from a 1700 to a 6800k :/

Want to custom loop?  Ask me more if you are curious

 

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, Droidbot said:

Screenshot_2018-01-03-13-16-06-951_com.emogoth.android.phone_mimi.png.d8db68ddf9920ef92e3424cc7d2ddf04.png

 

this is from /g/ and it sums it up pre well

Sweet post there.  That sums up everything petty well

Microsoft in there infinite wisdom have decided to impose a VRAM cap for games the that use DX9 o.O. May God Bless them those whoever came up with that idea. :dry:

 

You're looking for something that does not, has not, will not, might not or must not exist ... ... but you're always welcome to search for it. 

 

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, DeadlyTitan said:

Sweet post there.  That sums up everything petty well

Aside the fact the greatest majority of mainstream applications will most likely only see a hit of 0% ~ 5% the huge issue is for the enterprise level as they shown cloud services and what not... your mainstream CPU specially if Coffee Lake will be mostly fine thanks to PCID.

Personal Desktop":

CPU: Intel Core i7 10700K @5ghz |~| Cooling: bq! Dark Rock Pro 4 |~| MOBO: Gigabyte Z490UD ATX|~| RAM: 16gb DDR4 3333mhzCL16 G.Skill Trident Z |~| GPU: RX 6900XT Sapphire Nitro+ |~| PSU: Corsair TX650M 80Plus Gold |~| Boot:  SSD WD Green M.2 2280 240GB |~| Storage: 1x3TB HDD 7200rpm Seagate Barracuda + SanDisk Ultra 3D 1TB |~| Case: Fractal Design Meshify C Mini |~| Display: Toshiba UL7A 4K/60hz |~| OS: Windows 10 Pro.

Luna, the temporary Desktop:

CPU: AMD R9 7950XT  |~| Cooling: bq! Dark Rock 4 Pro |~| MOBO: Gigabyte Aorus Master |~| RAM: 32G Kingston HyperX |~| GPU: AMD Radeon RX 7900XTX (Reference) |~| PSU: Corsair HX1000 80+ Platinum |~| Windows Boot Drive: 2x 512GB (1TB total) Plextor SATA SSD (RAID0 volume) |~| Linux Boot Drive: 500GB Kingston A2000 |~| Storage: 4TB WD Black HDD |~| Case: Cooler Master Silencio S600 |~| Display 1 (leftmost): Eizo (unknown model) 1920x1080 IPS @ 60Hz|~| Display 2 (center): BenQ ZOWIE XL2540 1920x1080 TN @ 240Hz |~| Display 3 (rightmost): Wacom Cintiq Pro 24 3840x2160 IPS @ 60Hz 10-bit |~| OS: Windows 10 Pro (games / art) + Linux (distro: NixOS; programming and daily driver)
Link to comment
Share on other sites

Link to post
Share on other sites

6 minutes ago, DeadlyTitan said:

Hold on.. wait .. i never said i am MORE knowledgeable than Linux Kernel devs wth...  I just said that i am a application developer and i know how some stuff works. 

You being an application-developer has no bearing on this, as e.g. the following quote shows you have no idea what you're talking about:

32 minutes ago, DeadlyTitan said:

My take on this is, this bug can be fixed via a simple bios update and intel is only refusing to do that is cause then the only systems that are effected by this will be intel CPU's, apparently we all know that AMD does not suffer from this bug but a os level update can and will bring down the AMD systems along with Intel systems. 

 
I think intel is deliberately doing this so as to bring down AMD along with it. 

There is no reason for why the OS-level fix couldn't be made so that it only affects Intel-systems. I mean, all modern OSes set a whole bunch of different kinds of flags that direct its internal operations based on what CPUID they read and just as well the workaround for this bug can be turned on/off with a simple "if(cpuManufacturer == Intel) enableWorkaround = true;"

Hand, n. A singular instrument worn at the end of the human arm and commonly thrust into somebody’s pocket.

Link to comment
Share on other sites

Link to post
Share on other sites

> Now we know how intel had all that performance above AMD. ( ͡° ͜ʖ ͡°)

http://pcpartpicker.com/list/Mf3Zcc My build

 

R.I.P Donny- Got banned. We will always remember your spamming of "Cancerbooks"

 

iPhones are like 1 ply toliet paper with a logo slapped on them and years old hardware in them- A Wise Man

Link to comment
Share on other sites

Link to post
Share on other sites

 

PostgreSQL SELECT 1 with the KPTI workaround for Intel CPU vulnerability https://www.postgresql.org/message-id/20180102222354.qikjmf7dvnjgbkxe@alap3.anarazel.de 

Best case: 17% slowdown
Worst case: 23%

http://pcpartpicker.com/list/Mf3Zcc My build

 

R.I.P Donny- Got banned. We will always remember your spamming of "Cancerbooks"

 

iPhones are like 1 ply toliet paper with a logo slapped on them and years old hardware in them- A Wise Man

Link to comment
Share on other sites

Link to post
Share on other sites

No noticeable changes for gaming though

Want to custom loop?  Ask me more if you are curious

 

Link to comment
Share on other sites

Link to post
Share on other sites

39 minutes ago, DeadlyTitan said:

Well am sure it can be. I am an application developer and when something can be fixed via OS level patch then am sure as hell that it can be fixed with a microcode update. 

Isn't the microcode update limited to 1kB ? Can everything be fixed with 1kB ?

Link to comment
Share on other sites

Link to post
Share on other sites

7 minutes ago, Boo Berry said:

Looks like Windows has enabled KPTI for AMD processors too, so expect a performance drop with AMD on Windows as well.

 

 

This ... Exactly this is what i have been worried about...  Thank you for pointing it out 

Microsoft in there infinite wisdom have decided to impose a VRAM cap for games the that use DX9 o.O. May God Bless them those whoever came up with that idea. :dry:

 

You're looking for something that does not, has not, will not, might not or must not exist ... ... but you're always welcome to search for it. 

 

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, .spider. said:

Isn't the microcode update limited to 1kB ? Can everything be fixed with 1kB ?

I am not sure really but in the software field there is always a way. it all depends on how willing you are to solve the problem :)

Microsoft in there infinite wisdom have decided to impose a VRAM cap for games the that use DX9 o.O. May God Bless them those whoever came up with that idea. :dry:

 

You're looking for something that does not, has not, will not, might not or must not exist ... ... but you're always welcome to search for it. 

 

Link to comment
Share on other sites

Link to post
Share on other sites

I'm super pissed as I'm sure all of the Intel owners are. The last part for my first rig ever is arriving tomorrow, and I already have the 8600k in storage. Does anyone know if the performance loss caused by the patch will ever be fixed, if it even can be fixed?

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×