9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: [9fans] hacking issue: memory resizing
Date: Fri,  9 Sep 2005 09:52:16 -0500	[thread overview]
Message-ID: <20050909145216.4691A106B2F@dexter-peak.quanstro.net> (raw)
In-Reply-To: <432057DB.2060302@lanl.gov>

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


  reply	other threads:[~2005-09-09 14:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 15:45 Ronald G Minnich
2005-09-07 15:59 ` Francisco Ballesteros
2005-09-07 18:09   ` Ronald G Minnich
2005-09-08 11:50     ` Dave Lukes
2005-09-08 15:25       ` Ronald G Minnich
2005-09-09 14:52         ` erik quanstrom [this message]
2005-09-09 15:18           ` Ronald G Minnich
2005-09-09 15:31             ` jmk
2005-09-09 18:04               ` erik quanstrom
2005-09-09 18:09                 ` jmk
2005-09-09 18:14                 ` Eric Van Hensbergen
2005-09-09 19:06                   ` Ronald G Minnich
2005-09-09 19:59             ` Tim Newsham
2005-09-09 20:46               ` Francisco Ballesteros
2005-09-10  2:16                 ` Brian L. Stuart
2005-09-10 21:41                   ` Francisco Ballesteros
2005-09-11  2:11                     ` Brian L. Stuart

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=20050909145216.4691A106B2F@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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).