Re: user_to_phys() without mmap?

phil-news-nospam@xxxxxxxx writes:
On Mon, 16 Jul 2007 14:46:24 +0200 Rainer Weikusat <rweikusat@xxxxxxxxxxx> wrote:
| phil-news-nospam@xxxxxxxx writes:
|> On Sun, 15 Jul 2007 00:20:45 +0200 Rainer Weikusat <rweikusat@xxxxxxxxxxx> wrote:
|> | Neil Steiner <neil.steiner@xxxxxx> writes:
|> |> I'm trying to use a framebuffer from user space (think plain video
|> |> ram, not some PCI or AGP video card), but mmap'ing from kernel space
|> |> into user space is causing large latencies and unsightly artifacts.
|> |> It appears that anything written into the mmap'ed user memory is in
|> |> fact being copied into kernel space.
|> |
|> | Theoretically, this could probably be implemented with help of the
|> | MMU and some 'weird' fault handling, but I don't think someone would
|> | take the trouble, because it seems pretty useless. The /dev/mem driver
|> | certainly doesn't do this. Only the MMU will interfere accesses to
|> | virtual memory locations from user space, except for faults caused by
|> | this accesses.
|>
|> I tried to map the video buffer into user space some time ago and I did
|> find that what was mapped was not the actual physical memory of the video
|> card, but just some memory apparently allocated by a driver in the kernel
|> which was then periodically copied from that memory into the real physical
|> memory.
|
| Which driver? That should be easy to determine.

The basic console driver used for text and framebuffer modes.

So you weren't mmaping some hardware framebuffer to begin with but the
virtual framebuffer associated with one of the virtual consoles,
right?
.

Relevant Pages

  • Re: user_to_phys() without mmap?
    ... |> ram, not some PCI or AGP video card), but mmap'ing from kernel space ... |> into user space is causing large latencies and unsightly artifacts. ... | virtual memory locations from user space, ... Directly mapping physical memory to a process _can_, of course, be very ...
    (comp.os.linux.development.system)
  • [PATCH] vesafb, kernel 2.4.23
    ... The 2.4.23 vesafb driver wasn't using all of my video ... memory, so bootsplash images wouldn't load because ... Dec 14 00:14:31 blue vesafb: framebuffer at ...
    (Linux-Kernel)
  • Re: user_to_phys() without mmap?
    ... |> |> ram, not some PCI or AGP video card), but mmap'ing from kernel space ... |> |> into user space is causing large latencies and unsightly artifacts. ... The /dev/mem driver ... |> | virtual memory locations from user space, ...
    (comp.os.linux.development.system)
  • Re: user_to_phys() without mmap?
    ... |> ram, not some PCI or AGP video card), but mmap'ing from kernel space ... |> into user space is causing large latencies and unsightly artifacts. ... | virtual memory locations from user space, ...
    (comp.os.linux.development.system)
  • Re: + edac-new-opteron-athlon64-memory-controller-driver.patch added to -
    ... So we can kill the processes using that memory. ... What is the chipsets idea of which DIMM the memory error occurred on. ... There has always been enough information to determine the hardware ... some that are not easily accessible to user space so a kernel driver ...
    (Linux-Kernel)