Re: [Xen-devel] building blktap as a module

[Gerd Hoffmann <kraxel@xxxxxxx>]

  Hi,

>  1. The one in blktap_release() - why? Standard semantics is for mmap
> regions to exist beyond the closing of the mapping device. Doesn't make much
> sense to do that here, but then again not really any need to explicitly
> disallow it (and add extra code to enforce).

The linux kernel does call the drivers release() method when the last
reference is gone.  If you call close() with mappings still being
active, then ->release() is _not_ called when you close the file handle
but when the last mapping is unmapped.  Thus there is no point in trying
to handle active mappings there ;)

cheers,

  Gerd

-- 
Gerd Hoffmann <kraxel@xxxxxxx>
http://www.suse.de/~kraxel/julika-dora.jpeg

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel