Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

6 May, 2024: The networking issue during the past two days has been identified and fixed.


devel / comp.arch / Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!

SubjectAuthor
* Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!Anton Ertl
`* Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!MitchAlsup
 `* Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!Scott Lurndal
  `- Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!MitchAlsup

1
Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!

<2023Feb22.173645@mips.complang.tuwien.ac.at>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=30937&group=comp.arch#30937

  copy link   Newsgroups: comp.arch
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ant...@mips.complang.tuwien.ac.at (Anton Ertl)
Newsgroups: comp.arch
Subject: Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!
Date: Wed, 22 Feb 2023 16:36:45 GMT
Organization: Institut fuer Computersprachen, Technische Universitaet Wien
Lines: 21
Message-ID: <2023Feb22.173645@mips.complang.tuwien.ac.at>
References: <a80be088-e4c2-4186-a7c1-f1c22737d44bn@googlegroups.com>
Injection-Info: reader01.eternal-september.org; posting-host="0664a081baa7d8de417c4f8995f8b32f";
logging-data="1651350"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX198fis8/T+ED6OP/aOYdEgQ"
Cancel-Lock: sha1:9XkwrbGP8N850ZbnqLqcYMjuZkg=
X-newsreader: xrn 10.11
 by: Anton Ertl - Wed, 22 Feb 2023 16:36 UTC

Skybuck Flying <skybuckflying@gmail.com> writes:
>AMD HAD 3 YEARS TO FIX THIS SHIT ?!

Spectre V1 has been reported to them in June 2017, so it's now over
5.5 years. Even the public was informed more than five years ago.

>WHY IS NOT FIXED YET ?!

Apparently they think that customers don't care enough to make it a
competetive advantage to fix it (or a competetive disadvantage if the
competitor fixes it and they don't).

Alternative theory: A three-letter agency pressures all major CPU
manufacturers not to fix it. Counterargument: They could just as well
pressure them to provide backdoors to the ME/PSP or the like, which
would probably be more convenient for them.

- anton
--
'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>

Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!

<633f4bce-98f6-4440-bc11-ef88afcfe9a0n@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=30939&group=comp.arch#30939

  copy link   Newsgroups: comp.arch
X-Received: by 2002:a05:620a:a47:b0:71f:b89c:4f26 with SMTP id j7-20020a05620a0a4700b0071fb89c4f26mr1186921qka.0.1677092206435;
Wed, 22 Feb 2023 10:56:46 -0800 (PST)
X-Received: by 2002:a05:6870:ac1f:b0:163:36d5:35db with SMTP id
kw31-20020a056870ac1f00b0016336d535dbmr2018590oab.113.1677092206162; Wed, 22
Feb 2023 10:56:46 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.arch
Date: Wed, 22 Feb 2023 10:56:45 -0800 (PST)
In-Reply-To: <2023Feb22.173645@mips.complang.tuwien.ac.at>
Injection-Info: google-groups.googlegroups.com; posting-host=2600:1700:291:29f0:c574:cb2b:dcb1:62db;
posting-account=H_G_JQkAAADS6onOMb-dqvUozKse7mcM
NNTP-Posting-Host: 2600:1700:291:29f0:c574:cb2b:dcb1:62db
References: <a80be088-e4c2-4186-a7c1-f1c22737d44bn@googlegroups.com> <2023Feb22.173645@mips.complang.tuwien.ac.at>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <633f4bce-98f6-4440-bc11-ef88afcfe9a0n@googlegroups.com>
Subject: Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!
From: MitchAl...@aol.com (MitchAlsup)
Injection-Date: Wed, 22 Feb 2023 18:56:46 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2507
 by: MitchAlsup - Wed, 22 Feb 2023 18:56 UTC

On Wednesday, February 22, 2023 at 10:45:52 AM UTC-6, Anton Ertl wrote:
> Skybuck Flying <skybuc...@gmail.com> writes:
> >AMD HAD 3 YEARS TO FIX THIS SHIT ?!
> Spectre V1 has been reported to them in June 2017, so it's now over
> 5.5 years. Even the public was informed more than five years ago.
<
> >WHY IS NOT FIXED YET ?!
<
> Apparently they think that customers don't care enough to make it a
> competetive advantage to fix it (or a competetive disadvantage if the
> competitor fixes it and they don't).
<
And how would they know their customers level of care ??
Did AMD lose market share to Intel or ARM in the last 5 years or not ??
{none of AMD, Intel, or ARM have addressed the underlying problem}.
RISC-V has not addressed the problems, either.
<
So, there is no evidence that consumers in the market gives a flying frick !!
>
> Alternative theory: A three-letter agency pressures all major CPU
> manufacturers not to fix it. Counterargument: They could just as well
> pressure them to provide backdoors to the ME/PSP or the like, which
> would probably be more convenient for them.
>
> - anton
> --
> 'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
> Mitch Alsup, <c17fcd89-f024-40e7...@googlegroups.com>

Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!

<n_tJL.781121$MVg8.90498@fx12.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=30940&group=comp.arch#30940

  copy link   Newsgroups: comp.arch
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx12.iad.POSTED!not-for-mail
X-newsreader: xrn 9.03-beta-14-64bit
Sender: scott@dragon.sl.home (Scott Lurndal)
From: sco...@slp53.sl.home (Scott Lurndal)
Reply-To: slp53@pacbell.net
Subject: Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!
Newsgroups: comp.arch
References: <a80be088-e4c2-4186-a7c1-f1c22737d44bn@googlegroups.com> <2023Feb22.173645@mips.complang.tuwien.ac.at> <633f4bce-98f6-4440-bc11-ef88afcfe9a0n@googlegroups.com>
Lines: 22
Message-ID: <n_tJL.781121$MVg8.90498@fx12.iad>
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Wed, 22 Feb 2023 19:25:07 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Wed, 22 Feb 2023 19:25:07 GMT
X-Received-Bytes: 1746
 by: Scott Lurndal - Wed, 22 Feb 2023 19:25 UTC

MitchAlsup <MitchAlsup@aol.com> writes:
>On Wednesday, February 22, 2023 at 10:45:52 AM UTC-6, Anton Ertl wrote:
>> Skybuck Flying <skybuc...@gmail.com> writes:
>> >AMD HAD 3 YEARS TO FIX THIS SHIT ?!
>> Spectre V1 has been reported to them in June 2017, so it's now over
>> 5.5 years. Even the public was informed more than five years ago.
><
>> >WHY IS NOT FIXED YET ?!
><
>> Apparently they think that customers don't care enough to make it a
>> competetive advantage to fix it (or a competetive disadvantage if the
>> competitor fixes it and they don't).
><
>And how would they know their customers level of care ??
>Did AMD lose market share to Intel or ARM in the last 5 years or not ??
>{none of AMD, Intel, or ARM have addressed the underlying problem}.
>RISC-V has not addressed the problems, either.
><
>So, there is no evidence that consumers in the market gives a flying frick !!g

The 'consumers in the market' have accepted the software
workarounds, albeit reluctantly due to the performance impacts.

Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!

<10e57c76-51f2-4e34-b23b-c1d578505cbbn@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=30941&group=comp.arch#30941

  copy link   Newsgroups: comp.arch
X-Received: by 2002:a05:620a:1229:b0:738:e510:99f3 with SMTP id v9-20020a05620a122900b00738e51099f3mr2190472qkj.7.1677184307238;
Thu, 23 Feb 2023 12:31:47 -0800 (PST)
X-Received: by 2002:a05:6808:610:b0:378:1e37:ff20 with SMTP id
y16-20020a056808061000b003781e37ff20mr353637oih.8.1677184307045; Thu, 23 Feb
2023 12:31:47 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.arch
Date: Thu, 23 Feb 2023 12:31:46 -0800 (PST)
In-Reply-To: <n_tJL.781121$MVg8.90498@fx12.iad>
Injection-Info: google-groups.googlegroups.com; posting-host=2600:1700:291:29f0:7ccf:3725:844d:6b2f;
posting-account=H_G_JQkAAADS6onOMb-dqvUozKse7mcM
NNTP-Posting-Host: 2600:1700:291:29f0:7ccf:3725:844d:6b2f
References: <a80be088-e4c2-4186-a7c1-f1c22737d44bn@googlegroups.com>
<2023Feb22.173645@mips.complang.tuwien.ac.at> <633f4bce-98f6-4440-bc11-ef88afcfe9a0n@googlegroups.com>
<n_tJL.781121$MVg8.90498@fx12.iad>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <10e57c76-51f2-4e34-b23b-c1d578505cbbn@googlegroups.com>
Subject: Re: AMD 7950X STILL VUNERABLE TO SPECTRE ?!?!?!?!
From: MitchAl...@aol.com (MitchAlsup)
Injection-Date: Thu, 23 Feb 2023 20:31:47 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2728
 by: MitchAlsup - Thu, 23 Feb 2023 20:31 UTC

On Wednesday, February 22, 2023 at 1:25:11 PM UTC-6, Scott Lurndal wrote:
> MitchAlsup <Mitch...@aol.com> writes:
> >On Wednesday, February 22, 2023 at 10:45:52 AM UTC-6, Anton Ertl wrote:
> >> Skybuck Flying <skybuc...@gmail.com> writes:
> >> >AMD HAD 3 YEARS TO FIX THIS SHIT ?!
> >> Spectre V1 has been reported to them in June 2017, so it's now over
> >> 5.5 years. Even the public was informed more than five years ago.
> ><
> >> >WHY IS NOT FIXED YET ?!
> ><
> >> Apparently they think that customers don't care enough to make it a
> >> competetive advantage to fix it (or a competetive disadvantage if the
> >> competitor fixes it and they don't).
> ><
> >And how would they know their customers level of care ??
> >Did AMD lose market share to Intel or ARM in the last 5 years or not ??
> >{none of AMD, Intel, or ARM have addressed the underlying problem}.
> >RISC-V has not addressed the problems, either.
> ><
> >So, there is no evidence that consumers in the market gives a flying frick !!g
>
> The 'consumers in the market' have accepted the software
> workarounds, albeit reluctantly due to the performance impacts.
<
Perhaps there is simply no alternative at the consumer level, and that the
giants see no particular gain for the effort it would take.

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor