Xen devel - May 2006 - Re: [Xen-changelog] New memory_op subops which return the apparent or actual physical address map.

* Xen patchbot-unstable (patchbot-unstable@lists.xensource.com)
wrote:
> # HG changeset patch
> # User Ian.Campbell@xensource.com
> # Node ID 810ad61870e8c61a4e9ed096c4f73ab62048183b
> # Parent  ebfa1046a81f2243c9742ef0c5f99ccd255f99e5
> New memory_op subops which return the apparent or actual physical address
map.
> +    case XENMEM_memory_map:
> +    {
> +        return -ENOSYS;
> +    }
Is this meant to be a place holder?  Did you plan to replace the
hardcoded single entry map later?

thanks,
-chris

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

On 26 May 2006, at 10:23, Chris Wright wrote:
>> +    case XENMEM_memory_map:
>> +    {
>> +        return -ENOSYS;
>> +    }
>
> Is this meant to be a place holder?  Did you plan to replace the
> hardcoded single entry map later?
It will be properly defined for mini-xen, where it will return the real 
physical memory map. It could also be properly defined for 
auto-translate guests (where Xen manages the pseudo-physical space and 
therefore it is reasonable for Xen to provide the pseuophys e820 map). 
It could also be properly defined for all guests if the guest loader 
could poke down e820 maps.

  -- Keir


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