Crashes when reading physical memory
Crashes when reading physical memory
- Subject: Crashes when reading physical memory
- From: Hajime Inoue <email@hidden>
- Date: Fri, 13 Mar 2009 16:28:17 -0400
Thanks, M.M., Michael, Andreas, and Terry, for your thoughts.
It's clear that there are definite limitations in getting a physical memory
dump using the same resources being dumped. However, for some purposes
what's
available just by dumping memory to a file is "good enough".
So I used the function M.M. suggested and wrote a kext using the
ml_phys_read_*
functions. This works fine for ppc (I've tested on 10.3.9 and 10.5 with 0.5
and
1.5G of memory, respectively). But it fails after reading about 3.3 or 3.4
G
on my Intel 10.5 machine.
Does anyone know why this should be? One of my colleagues mentioned that he
saw
something about problems reading memory simultaneously being used for DMA.
Is
this a possibility?
Also, it appears that ml_io_map is also exported. However, I can't find an
equivalent ml_io_munmap. pmap_release isn't exported (giving a warning),
but
is found when the kext is loaded. Can I use pmap_release(kernel_map, ...)
with
the memory allocated by ml_io_map?
Thanks again,
-Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden