| Deutsch English Français Italiano |
|
<6a77fabdb64f59e4497ef3353d747441@www.novabbs.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail From: mitchalsup@aol.com (MitchAlsup1) Newsgroups: comp.arch Subject: Re: Constant Stack Canaries Date: Fri, 4 Apr 2025 21:13:27 +0000 Organization: Rocksolid Light Message-ID: <6a77fabdb64f59e4497ef3353d747441@www.novabbs.org> References: <vsbcnl$1d4m5$1@dont-email.me> <vsc058$20pih$1@dont-email.me> <4cf60b5fd8b785feb07a67a823cc349d@www.novabbs.org> <vseeen$l4ig$1@dont-email.me> <vseiq9$qndj$1@dont-email.me> <e05e9d429f71944bbfe74c3f54b79a03@www.novabbs.org> <vseojq$112f7$1@dont-email.me> <62b5c4a25d917c5bab64a815189de826@www.novabbs.org> <vshf6a$3smcv$1@dont-email.me> <21397906a7a77c2d43191fdaab98a3c9@www.novabbs.org> <jwv4iz75l6k.fsf-monnier+comp.arch@gnu.org> <vsidun$sput$2@dont-email.me> <jwvtt752vg1.fsf-monnier+comp.arch@gnu.org> <vsmg8a$16gr3$1@dont-email.me> <vsnksc$2fkk9$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="3147608"; mail-complaints-to="usenet@i2pn2.org"; posting-account="o5SwNDfMfYu6Mv4wwLiW6e/jbA93UAdzFodw5PEa6eU"; User-Agent: Rocksolid Light X-Rslight-Posting-User: cb29269328a20fe5719ed6a1c397e21f651bda71 X-Rslight-Site: $2y$10$q1Z3B7eJR2IslrtaZlqme.mOi1nnpyUpoiUH0YVTkockiGut09D7q X-Spam-Checker-Version: SpamAssassin 4.0.0 Bytes: 2372 Lines: 22 On Fri, 4 Apr 2025 3:49:31 +0000, Robert Finch wrote: > On 2025-04-03 1:22 p.m., BGB wrote: ------------------- >> >> Or, to allow for NOMMU operation, or reduce costs by not having context >> switches result in as large of numbers of TLB misses. >> >> Also makes the kernel simpler as it doesn't need to deal with each >> process having its own address space. > > Have you seen the MPRV bit in RISCV? Allows memory ops to execute using > the previous mode / address space. The bit just has to be set, then do > the memory op, then reset the bit. Makes it easy to access data using > the process address space. Let us postulate you are running in RISC-V HyperVisor on core[j] and you want to write into GuestOS VAS and into application VAS more or less simultaneously. Seems to me like you need a MPRV to be more than a single bit so it could index which layer of the SW stack's VAS it needs to touch.