From: Michael Raskin <7c6f434c@mail.ru>
To: hi@alyssa.is, devel@spectrum-os.org
Cc: mm@m-squa.red
Subject: [PATCH www 2/1] design.html: mention aarch64 as well as x86_64
Date: Sat, 21 Nov 2020 17:34:15 +0100 [thread overview]
Message-ID: <E1kgVjD-0000Xy-VM.7c6f434c-mail-ru@smtp37.i.mail.ru> (raw)
In-Reply-To: <20201121152314.15152-1-hi@alyssa.is>
>I'd like to continue to link to x86 Considered Harmful somewhere in
>the text, but couldn't figure out how to fit it in since there's not
>really anywhere I'm talking about x86 specifically rather than all
>architectures. I'd appreciate suggestions for how I might do that.
I think it is nice to have «why not ARM» and «why not x86*» sections
when you have an implementation that you are justifying, and no doubts
on the way-cheaper attack level (there must be a memory attack on Sway
given a hijacked browser, mustn't there be?)
Right now, you getting a restful break is more useful than picking
wording on choices Spectrum cannot yet afford to make.
[horrible mis-implementation of user hostility is worse than no
implementation, perfect implementations do nto exist]
> <p>
> I would like Spectrum to additionally have first class support for at
Looks fine
>+cannot be inspected and audited. One of the advantages of Spectrum's
>+Linux base is the extremely wide hardware support that Linux offers,
>+so the only blocker for POWER9 support is support in crosvm for
>+virtualizing that architecture, which is outside the expertise of
>+anybody currently working on Spectrum but would be a very welcome
>+contribution.
Looks frank and true
> <p>
>-Ideally, all Spectrum packages, x86_64 and ppc64le, would be built on
>+Ideally, all Spectrum packages, for all architectures, would be built on
> POWER9 hardware. Even if a user has to trust the x86_64 computer
_Ideally_ on diverse hardware with more than one transparent-ish
platform, because lack of blobs to load does not mean lack of backed-in
vulnerable functionality. Open POWER9 cores help, but do not prove
faithful implementation on a specific chip in your hands, all that
stuff.
I would put as
«
Ideally, all Spectrum packages, for all architectures, would be built on
diverse hardware including a platform with POWER9 level of openness.
»
But, again, this a bridge to burn once it is crossed, or something.
next prev parent reply other threads:[~2020-11-21 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:01 [PATCH www] design.html: backpedal a bit on POWER9 Alyssa Ross
2020-11-18 12:52 ` Michael Raskin
2020-11-20 14:06 ` Alyssa Ross
2020-11-21 15:23 ` [PATCH www 2/1] design.html: mention aarch64 as well as x86_64 Alyssa Ross
2020-11-21 16:34 ` Michael Raskin [this message]
2020-11-22 20:09 ` Alyssa Ross
2020-11-29 23:54 ` [PATCH www 3/1] design.html: mention goal of diverse build hardware Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1kgVjD-0000Xy-VM.7c6f434c-mail-ru@smtp37.i.mail.ru \
--to=7c6f434c@mail.ru \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
--cc=mm@m-squa.red \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).