9 messages in com.xensource.lists.xen-ia64-develRe: [Xen-ia64-devel] [Patch 2/2] para...
FromSent OnAttachments
Akio Takebe16 Feb 2007 16:43 
Akio Takebe16 Feb 2007 16:46.patch
Akio Takebe16 Feb 2007 16:47.patch
Alex Williamson18 Feb 2007 15:52 
Isaku Yamahata21 Feb 2007 19:37 
Tristan Gingold21 Feb 2007 20:54 
Isaku Yamahata21 Feb 2007 21:23 
Tristan Gingold21 Feb 2007 21:31 
Isaku Yamahata21 Feb 2007 21:56 
Subject:Re: [Xen-ia64-devel] [Patch 2/2] paravirtualize mmap hundlers of /proc/bus/pci
From:Isaku Yamahata (yama@valinux.co.jp)
Date:02/21/2007 09:23:15 PM
List:com.xensource.lists.xen-ia64-devel

On Thu, Feb 22, 2007 at 05:55:13AM +0100, Tristan Gingold wrote:

add_window(), which registers io region and memory region, calls ioremap with ACPI_IO_RANGE regions, but it doesn't with ACPI_MEMORY_RANGE regions. If the ioremap hypercall is called with ACPI_MEMORY_RANGE regions, all pci devices are free from such paravirtualization. Especially we can get rid of /dev/mem and pci mmap paravirtualization to use X.

Would be nice, but isn't the ACPI_MEMORY_RANGE very large on some machine ?

Yes. So I wondered what kind of devices had such large area.

Presumably we don't want to map pci bridge which may be large so that we need to detect it somehow in add_window().

Pci root bridge or pci-to-pci bridges ?

Yes.