[lkml]   [2004]   [Nov]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [4/7] Xen VMM patch set : /dev/mem io_remap_page_range for CONFIG_XEN
> On Tue, 2004-11-30 at 12:09 +0000, Ian Pratt wrote:
> > > On Tue, 2004-11-30 at 08:56 +0000, Ian Pratt wrote:
> > >
> > > > In the Xen case, we actually need to use io_remap_page_range for
> > > > all /dev/mem accesses, so as to be able to map the BIOS area, DMI
> > > > tables etc.
> > >
> > > look at the /dev/mem patches in the -mm tree... there might be
> > > infrastructure there that is useful to you
> >
> > Thanks for the pointer. Having looked through, it's orthogonal
> > and can't help us, though doesn't conflict with our patch either
> > (fuzz 2).
> well.. it makes all non-ram unaccessible... so what's left is only the
> stuff Xen wants to make accessible anyway :)

Ha -- I'd missed that because I hadn't spotted the addition of
devmem_is_allowed to /arch/i386/mm/init.c

I'm really rather pleased to see this attempt at disambiguating
what /dev/mem can be used for. What's nice from our POV is it now
explicitly prevents the cases that we couldn't easily support in
Xen. We'd observed that nothing seemed to break, so presumed
they weren't very common.

The next logical step with that patch would be to have mmap_mem
call io_remap_page_range rather than remap_pfn_range, at which
point it would solve our problem. I'm not sure what this would
mean for architectures other than i386.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:08    [W:0.067 / U:1.276 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site