Re: [Xen-devel] [PATCH 00/18] xenpaging changes for 4.0

[Olaf Hering <olaf@xxxxxxxxx>]

On Mon, Oct 18, Tim Deegan wrote:

> These patches look pretty good to me, with a few caveats:
> - Is it possible to avoid having quite so many paths return ENOENT?
>   In particular, there seemed to be paths where _removing_ a p2m entry
>   that's paged out caused an error.  Would it be possible to have some of
>   those cases fixed up from the paging code instead?

I'm not sure if thats possible.
Thats currently beyond my knowledge, sorry.
Any pointer for how to do that are welcome.

> - The usual way to get patches into the 4.0 tree is to submit them
>   againts xen-unstable and then ask for specific patches to be
>   backported; I see you're already going that way with most of these.

Yes, just wanted to send my current state and all of them are also
needed for xen-unstable

> - I imagine the tools maintainers will encourage you to do your tools
>   patches againsl xl/libxl as well. :)

Sure, that will be done as well.


Olaf


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