On Sat, Jun 1, 2013 at 12:16 AM, Suman Anna wrote:
> It is not preferable to have the allocated pages for carveout
> memories freed before they are unmapped. The code that deals
> with the cleanup of carveout memories is therefore moved after
> the corresponding mapping entries were cleaned up.
>
On Sat, Jun 1, 2013 at 12:16 AM, Suman Anna s-a...@ti.com wrote:
It is not preferable to have the allocated pages for carveout
memories freed before they are unmapped. The code that deals
with the cleanup of carveout memories is therefore moved after
the corresponding mapping entries were
It is not preferable to have the allocated pages for carveout
memories freed before they are unmapped. The code that deals
with the cleanup of carveout memories is therefore moved after
the corresponding mapping entries were cleaned up.
This is mostly a no-op since the remote processors are
It is not preferable to have the allocated pages for carveout
memories freed before they are unmapped. The code that deals
with the cleanup of carveout memories is therefore moved after
the corresponding mapping entries were cleaned up.
This is mostly a no-op since the remote processors are
4 matches
Mail list logo