From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: erik quanstrom <quanstro@quanstro.net>
Subject: [9fans] hacking issue: memory resizing
In-Reply-To: <432057DB.2060302@lanl.gov>
Message-Id: <20050909145216.4691A106B2F@dexter-peak.quanstro.net>
Date: Fri,  9 Sep 2005 09:52:16 -0500
Topicbox-Message-UUID: 85d1c334-ead0-11e9-9d60-3106f5b1d025

this is a pretty interesting problem. i'd bet that nobody
envisioned doing things like this back when this code was 
written.

for a toehold on the problem, it looks like the cardbus
code (/sys/boot/pc/devpccard.c:828) and the functions
upamalloc() and upafree() in memory.c allow some kernel-level 
dynamic memory. (although upafree() doesn't do anything.)

am i wrong in this? what can i do with memory on a pccard?
how scary is it to eject a pccard with configured memory?
(i guess those are the same question.)

erik