Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Stefan Monnier <monnier@iro.umontreal.ca>
Newsgroups: comp.arch
Subject: Re: virtualization, Constant Stack Canaries
Date: Wed, 16 Apr 2025 21:07:13 -0400
Organization: A noiseless patient Spider
Lines: 10
Message-ID: <jwvr01rfvi4.fsf-monnier+comp.arch@gnu.org>
References: <vsbcnl$1d4m5$1@dont-email.me>
	<694fc2e37e0bcb6de19c0e1d1d0f0042@www.novabbs.org>
	<vtpaq5$35su6$1@dont-email.me> <IlYLP.249406$bYQ4.26862@fx41.iad>
	<vtpk2a$2l2l$1@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Thu, 17 Apr 2025 03:07:14 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="6229a318b5cc7625c28552bb9e28070a";
	logging-data="3530177"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/w2hmvO0GECnaw2CS3M6bFHbn/jqC/hXw="
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:0asJVodz+YvBw/msh5okPO8z/DQ=
	sha1:jKE20hZz87OSRbK35PqYSUrlN1M=

> External interrupts are indeed a lot harder unless you know a whole lot
> about the thing that's interrupting.

Not only the thing that's interrupting but also the thing
it's interrupting.  Maybe it's easier for My 66000 where I understand
that the hardware has a notion of threads/processes so it may be able to
know how to deliver the interrupt to the appropriate thread/process.


        Stefan