Re: [Clax86list] Accessing Physical Memory & Other Process's Address Space
- From: Charles Crayne <spamtrap@xxxxxxxxxx>
- Date: Wed, 6 Feb 2008 12:12:07 -0800
On Wed, 6 Feb 2008 10:00:52 -0800 (PST)
"mybwpp@xxxxxxxxxxxxxx" <spamtrap@xxxxxxxxxx> wrote:
What does 1234h imply here, is it the linear address (virtual memory
address) in the process own address space or physical address?
Virtual address.
how a process can
refer to the memory location in another process address space (both
operating at the same privilege level)?
Such a process would have to determine what physical address was
currently assigned to the target virtual address and map that physical
address into its own virtual address space, which would require both a
system privilege level, and a detailed knowledge of the OS internals.
On the other hand, the OS may offer such a service to processes which
wish to share a common memory range. In Linux, for example, this is done by
issuing an mmap request with the MAP_SHARED attribute.
Is there any way to directly refer to physical memory locations in
mov or similar instructions?
Not while paging is enabled.
--
Chuck
http://www.pacificsites.com/~ccrayne/charles.html
.
- Follow-Ups:
- Re: Accessing Physical Memory & Other Process's Address Space
- From: mybwpp@xxxxxxxxxxxxxx
- Re: Accessing Physical Memory & Other Process's Address Space
- References:
- Accessing Physical Memory & Other Process's Address Space
- From: mybwpp@xxxxxxxxxxxxxx
- Accessing Physical Memory & Other Process's Address Space
- Prev by Date: Accessing Physical Memory & Other Process's Address Space
- Next by Date: Re: Accessing Physical Memory & Other Process's Address Space
- Previous by thread: Accessing Physical Memory & Other Process's Address Space
- Next by thread: Re: Accessing Physical Memory & Other Process's Address Space
- Index(es):
Relevant Pages
|