From: Stuart Morrow <morrow.stuart@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] VMX improvements + AVX
Date: Thu, 10 Dec 2020 12:23:05 +0000 [thread overview]
Message-ID: <CABB-WO_7T7SwaQhvnn9YYe8PiW2-=8GmFKzoJj74U6gJFeJBvQ@mail.gmail.com> (raw)
In-Reply-To: <52CB3E735527EF01CDF9E2641E3A406B@gmail.com>
I have to admit I don't understand why this type of thing actually
needs to be a patch. The kernel needs to know what instructions the
program is liable to use? Why? My Nemo's-book understanding of this
stuff: the kernel sets up an allotment of time, and then the user
process goes to town within the constraints set up for it. Can't
really imagine why certain instructions would need special
arrangements or what the mechanism might be.
I appreciate whatever educ9tion I might get out of this, although it's
kind of a waste (depending on what lurker sees it who might do
something useful with it).
next prev parent reply other threads:[~2020-12-10 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 15:39 Sigrid Solveig Haflínudóttir
2020-12-04 21:15 ` james palmer
2020-12-04 22:25 ` Kurt H Maier
2020-12-05 0:19 ` ori
2020-12-10 12:23 ` Stuart Morrow [this message]
2020-12-10 15:09 ` ori
2020-12-18 2:22 ` magma698hfsp273p9f
2020-12-18 4:41 ` ori
2021-01-21 0:58 ` Nemo's books (WAS: Re: [9front] VMX improvements + AVX) magma698hfsp273p9f
2021-01-21 3:37 ` Roman Shaposhnik
2021-01-21 3:58 ` sl
2021-01-23 7:31 ` [9front] Re: Nemo's books magma698hfsp273p9f
2021-01-23 12:47 ` Eckard Brauer
2021-01-21 4:07 ` Nemo's books (WAS: Re: [9front] VMX improvements + AVX) Anthony Martin
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='CABB-WO_7T7SwaQhvnn9YYe8PiW2-=8GmFKzoJj74U6gJFeJBvQ@mail.gmail.com' \
--to=morrow.stuart@gmail.com \
--cc=9front@9front.org \
/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.
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).