Re: [PATCH] memory: transaction API

Jan Kiszka
2011-07-21T10:38:21Z

On 2011-07-21 12:21, Avi Kivity wrote:
> Allow changes to the memory hierarchy to be accumulated and
> made visible all at once. This reduces computational effort,
> especially when an accelerator (e.g. kvm) is involved.
>
> Useful when a single register update causes multiple changes
> to an address space.

That's simple to implement in the core, but complicates life for the
users, at least for the simple "update this region" use case.

Do we have transactional scenarios during runtime where multiple memory
regions are reconfigured?

Jan

--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux