Living things on this planet breathe. They exhale. Sometimes we humans kill and eat them.
This is a carbon-neutral process.
If all those animals were left alive, breathing out CO2, farting methane, eating up all the good grass and taking the jobs of other animals whose consumption have fallen out of popularity, their carbon footprint would be even worse.
This belies a complete lack of understanding of the carbon cycle:/
Save the environment - stop eating plants that absorb CO2 and eat more meat.
Whether you eat plants, or animals, you're merely eating a link in the carbon cycle.
This article (and study) isn't making the insane claim that the meat in the sandwich, or the bread in the sandwich is a carbon-costly ingredient... They're measuring the cost of transportation, refrigeration, etc, etc - the things that require non-cycle sourced carbon to produce the final product.
Your ignorance makes this problem intractable. I hope you understand that some day.
This very well may be the case specifically with the processors in question, but as a general concept it is not.
Depending on the microarchitecture, things like permissions checks on TLB lookups, page table walks, can all be *implemented* in the actual microcode (DEC Alpha), making such a flaw a flaw in the microcode, not the silicon.
That's a dishonest characterization, even if the end-result is the same.
Intel put "do not optimize non-Intel CPUs" code generation in their compiler. Which still equally sucks, but is far less evil from a purely capitalist competition standpoint.
Kind of. Intel isn't proposing making all future processors insecure, they're just implementing this fix in a way that would allow for it architecturally (setting CPUID bits), and Linus is rightly skeptical that that is their goal.
It's entirely possible the Intel engineers are just idiots.
Huh? Where is AMD's proposed fix for Specter??
This patch is about Intel addressing Specter in microcode and requiring the OS to do funny things to support it, including recognizing that the fix has to be enabled at boot-time. Everyone is affected by this bug, Intel is pushing a fix via microcode that is lame. As Linus said, we already have retpoline, and we can already enable it based on rational checks that don't indicate this microcode fix will become an architectural feature ongoing. AMD (and literally everyone else) did *not* do it in the correct way.
Even a 20 Celsius rise wouldn't kill us all. Those of us still alive would only be living closer to the poles or higher in the mountains.
Look at the larger picture. Genetic bottlenecks can lead to extinction. Not that mankind isn't one adaptable critter, but if you put us in isolated barely arable hills for enough time without some nice lowland cultures to plunder, we could very well die off. Sure, it wouldn't happen overnight, but we'd be rather foolish to think we can survive anything.
Aye:(
I'd love to be able to get rid of this fscking Windows partition. Dual booting is annoying, and so is running a desktop virtualized on your desktop.
Oh, my marginal drops- the tax plan as a whole is a net gain for me... I was simply stating that the doubling of the standard deduction was a no-op due to the elimination of the personal exemption.
Not that this data point is really any better than your completely bullshit data point, but the fastest growing economy in the world is the Ethiopian economy, with a corporate tax rate of 30% (higher than ours, now)
But tax cuts are evil even though the standard deduction for everyone is doubled.
Yes, but the personal exemption is eliminated...
Now, I only file a standard plebeian 1040-EZ, so someone with more complicated taxes can correct me- but I believe that makes it a no-op...
Raw, unassisted handling peaked in the 1990s, when suspension geometry technology reached essentially the point we've reached today, but when vehicles were lighter.
Ehhhh, I'll give you that technology peaked... mostly.
But to say that unassisted handling peaked? That's patently false.
Even with all driving aids disabled in a modern performance vehicle, they handle stupidly better than anything made in the 90s.
The heavier cars these days have larger tires. They grip better. They've got bigger brakes. They stop better.
The tech may not be much different, but if you put someone today who is used to the handling of a big ass car with fat wheels and brakes in command of a factory E30 M3, considered a great handling car with great balance... They're going to fucking die. And it's not because the car is fast, or handles well.
Simple Meltdown attacks run within your own attacking process, bypassing privilege bits.
Simple Meltdown attacks run within your own attacking process, *because* the privilege bits can be bypassed.
The design fault spectre exploits is sharing the branch predictor between different processes. Spectre *doesn't* depend on bypassing privilege bits. Spectre attacks trick the processor into accessing privileged memory from within a privileged process, by speculatively branching to snippets of the wrong code.
That is correct. Meltdown also uses faulty branch predictor behavior to widen the window with which the side-channel is open to improper reading. Only Intel processors allow this to happen across privilege boundaries.
And Spectre's (variant b) branch predictor tomfoolery is just to pre-load the cache. The data is read from the cache. That is the side-channel. These are 3 variants of the same problem- cache leakage side-channel that can be read utilizing common behaviors of superscalar architectures.
Unsure where we're miscommunicating.
This description is very misleading because it makes it sound like the two issues are similar when they very much are not.
No, they are.
"Meltdown" should be considered a subset of the "Spectre" class of vulnerabilities.
While AMD is not vulnerable to Meltdown variants that can be mitigated with KPTI, they're still vulnerable to Meltdown variants that can manipulate the kernel into doing the speculative execution for them- as the Google PoC demonstrated, eBPF with JIT (though disabled by default).
Spectre is merely a side-channel timing attack. Similar issues have been known about for years exploiting static caches, hyper threading, branch prediction, DPA...etc. Spectre is little more than a PR smoke screen for Meltdown. The two are not in the same league and they don't deserve to be described as if they are close relatives.
They're both side-channel timing attacks. They both exploit a race condition between instruction retirement after a fault in a superscalar architecture. The difference is that AMDs execution units can't specifically leak the data, because their L1 caches store and honor privilege bits. However, if that speculative execution happens in the kernel context (eBPF JIT) then userspace can still pick up the side-channel leaked data, making even AMD vulnerable to a subset of Meltdown, itself a subset of Spectre. Clear?
Or that there is a strong negative pressure for intelligence arising in an unintelligent society, making it difficult to spread.... Like smart people not having kids.
I have a newer car, take yearly (is that regular?) vacations, have semi-reasonable savings and retirement.
I make ~91st percentile single-earner income.
It is probably safe to say that I do avoid thinking about the future as much as possible, which segways into the next point- I have suffered from panic attacks for about a year now, and recently progressed into a very several generalized anxiety disorder. It's being treated now, thankfully, and fairly successfully.
I think that counts as taking action to correct things in my life?
I think I probably run on about 80% instinct, but it's a very talented instinct that commands significant pay. I will probably not have offspring.
Oh, I definitely wasn't aiming to make it look appealing- just spreading the word that for interested people, the quality issues can be worked around, and as the person who replied to you said- the marketing of just 'bluetooth' is the main problem. There are technical considerations, and without taking them into account, the highest probable outcome is that you end up listening to the audio of the SBC codec, which further propagates the idea that BT is absolutely unsuitable for use at all.
That's kind of the impression I'm getting from most of the posts on here.
I hated BT quality for a while before I figured out that Codec Matters.
I now have a cheap set of headphones that supports AAC and aptX, so I never revert to SBC on either my apple or android devices, and the quality is wonderful.
Slashdot Mirror
Living things on this planet breathe. They exhale. Sometimes we humans kill and eat them.
This is a carbon-neutral process.
If all those animals were left alive, breathing out CO2, farting methane, eating up all the good grass and taking the jobs of other animals whose consumption have fallen out of popularity, their carbon footprint would be even worse.
This belies a complete lack of understanding of the carbon cycle :/
Save the environment - stop eating plants that absorb CO2 and eat more meat.
Whether you eat plants, or animals, you're merely eating a link in the carbon cycle.
This article (and study) isn't making the insane claim that the meat in the sandwich, or the bread in the sandwich is a carbon-costly ingredient... They're measuring the cost of transportation, refrigeration, etc, etc - the things that require non-cycle sourced carbon to produce the final product.
Your ignorance makes this problem intractable. I hope you understand that some day.
This very well may be the case specifically with the processors in question, but as a general concept it is not.
Depending on the microarchitecture, things like permissions checks on TLB lookups, page table walks, can all be *implemented* in the actual microcode (DEC Alpha), making such a flaw a flaw in the microcode, not the silicon.
In Twitter's defense, it's getting terribly hard to tell you guys apart from the Russian TrollBots
That's a dishonest characterization, even if the end-result is the same.
Intel put "do not optimize non-Intel CPUs" code generation in their compiler. Which still equally sucks, but is far less evil from a purely capitalist competition standpoint.
Kind of. Intel isn't proposing making all future processors insecure, they're just implementing this fix in a way that would allow for it architecturally (setting CPUID bits), and Linus is rightly skeptical that that is their goal.
It's entirely possible the Intel engineers are just idiots.
Huh? Where is AMD's proposed fix for Specter??
This patch is about Intel addressing Specter in microcode and requiring the OS to do funny things to support it, including recognizing that the fix has to be enabled at boot-time. Everyone is affected by this bug, Intel is pushing a fix via microcode that is lame. As Linus said, we already have retpoline, and we can already enable it based on rational checks that don't indicate this microcode fix will become an architectural feature ongoing. AMD (and literally everyone else) did *not* do it in the correct way.
Look at the larger picture. Genetic bottlenecks can lead to extinction. Not that mankind isn't one adaptable critter, but if you put us in isolated barely arable hills for enough time without some nice lowland cultures to plunder, we could very well die off. Sure, it wouldn't happen overnight, but we'd be rather foolish to think we can survive anything.
Now that makes sense!
Thanks for the explanation
Aye :(
I'd love to be able to get rid of this fscking Windows partition. Dual booting is annoying, and so is running a desktop virtualized on your desktop.
https://www.merriam-webster.co...
You are being obnoxious. You know that, right?
Oh, my marginal drops- the tax plan as a whole is a net gain for me... I was simply stating that the doubling of the standard deduction was a no-op due to the elimination of the personal exemption.
Not that this data point is really any better than your completely bullshit data point, but the fastest growing economy in the world is the Ethiopian economy, with a corporate tax rate of 30% (higher than ours, now)
Author has an agenda, news at 11.
But tax cuts are evil even though the standard deduction for everyone is doubled.
Yes, but the personal exemption is eliminated...
Now, I only file a standard plebeian 1040-EZ, so someone with more complicated taxes can correct me- but I believe that makes it a no-op...
Raw, unassisted handling peaked in the 1990s, when suspension geometry technology reached essentially the point we've reached today, but when vehicles were lighter.
Ehhhh, I'll give you that technology peaked... mostly.
But to say that unassisted handling peaked? That's patently false. Even with all driving aids disabled in a modern performance vehicle, they handle stupidly better than anything made in the 90s.
The heavier cars these days have larger tires. They grip better. They've got bigger brakes. They stop better.
The tech may not be much different, but if you put someone today who is used to the handling of a big ass car with fat wheels and brakes in command of a factory E30 M3, considered a great handling car with great balance... They're going to fucking die. And it's not because the car is fast, or handles well.
Simple Meltdown attacks run within your own attacking process, bypassing privilege bits.
Simple Meltdown attacks run within your own attacking process, *because* the privilege bits can be bypassed.
The design fault spectre exploits is sharing the branch predictor between different processes. Spectre *doesn't* depend on bypassing privilege bits. Spectre attacks trick the processor into accessing privileged memory from within a privileged process, by speculatively branching to snippets of the wrong code.
That is correct. Meltdown also uses faulty branch predictor behavior to widen the window with which the side-channel is open to improper reading. Only Intel processors allow this to happen across privilege boundaries.
And Spectre's (variant b) branch predictor tomfoolery is just to pre-load the cache. The data is read from the cache. That is the side-channel. These are 3 variants of the same problem- cache leakage side-channel that can be read utilizing common behaviors of superscalar architectures.
Unsure where we're miscommunicating.
This description is very misleading because it makes it sound like the two issues are similar when they very much are not.
No, they are. "Meltdown" should be considered a subset of the "Spectre" class of vulnerabilities.
While AMD is not vulnerable to Meltdown variants that can be mitigated with KPTI, they're still vulnerable to Meltdown variants that can manipulate the kernel into doing the speculative execution for them- as the Google PoC demonstrated, eBPF with JIT (though disabled by default).
Spectre is merely a side-channel timing attack. Similar issues have been known about for years exploiting static caches, hyper threading, branch prediction, DPA...etc. Spectre is little more than a PR smoke screen for Meltdown. The two are not in the same league and they don't deserve to be described as if they are close relatives.
They're both side-channel timing attacks. They both exploit a race condition between instruction retirement after a fault in a superscalar architecture. The difference is that AMDs execution units can't specifically leak the data, because their L1 caches store and honor privilege bits. However, if that speculative execution happens in the kernel context (eBPF JIT) then userspace can still pick up the side-channel leaked data, making even AMD vulnerable to a subset of Meltdown, itself a subset of Spectre. Clear?
That is true of older ARM devices. Nothing modern though. ARMs have been superscalar for a while.
Or that there is a strong negative pressure for intelligence arising in an unintelligent society, making it difficult to spread.... Like smart people not having kids.
Probably true.
Almost certainly false.
And anyone rolling a Mage knows you don't give two squirts of piss about WIS
I have a newer car, take yearly (is that regular?) vacations, have semi-reasonable savings and retirement.
I make ~91st percentile single-earner income.
It is probably safe to say that I do avoid thinking about the future as much as possible, which segways into the next point- I have suffered from panic attacks for about a year now, and recently progressed into a very several generalized anxiety disorder. It's being treated now, thankfully, and fairly successfully.
I think that counts as taking action to correct things in my life?
I think I probably run on about 80% instinct, but it's a very talented instinct that commands significant pay. I will probably not have offspring.
Where do I fit in to your generalization?
Oh, I definitely wasn't aiming to make it look appealing- just spreading the word that for interested people, the quality issues can be worked around, and as the person who replied to you said- the marketing of just 'bluetooth' is the main problem. There are technical considerations, and without taking them into account, the highest probable outcome is that you end up listening to the audio of the SBC codec, which further propagates the idea that BT is absolutely unsuitable for use at all.
That's kind of the impression I'm getting from most of the posts on here.
I hated BT quality for a while before I figured out that Codec Matters.
I now have a cheap set of headphones that supports AAC and aptX, so I never revert to SBC on either my apple or android devices, and the quality is wonderful.