Re: [PATCH] memory: transaction API

2011-07-21 Thread Avi Kivity
On 07/21/2011 04:17 PM, Jan Kiszka wrote: On 2011-07-21 14:58, Avi Kivity wrote: On 07/21/2011 03:52 PM, Jan Kiszka wrote: The problem is that update can change lots of things. offset, size, whether it's mmio or RAM, read-onlyness, even the wierd things like coalesced mmio. So it's

Re: [PATCH] memory: transaction API

2011-07-21 Thread Jan Kiszka
On 2011-07-21 15:50, Avi Kivity wrote: On 07/21/2011 04:17 PM, Jan Kiszka wrote: On 2011-07-21 14:58, Avi Kivity wrote: On 07/21/2011 03:52 PM, Jan Kiszka wrote: The problem is that update can change lots of things. offset, size, whether it's mmio or RAM, read-onlyness, even the wierd

Re: [PATCH] memory: transaction API

2011-07-21 Thread Avi Kivity
On 07/21/2011 05:32 PM, Jan Kiszka wrote: On 2011-07-21 15:50, Avi Kivity wrote: On 07/21/2011 04:17 PM, Jan Kiszka wrote: On 2011-07-21 14:58, Avi Kivity wrote: On 07/21/2011 03:52 PM, Jan Kiszka wrote: The problem is that update can change lots of things. offset, size, whether

Re: [PATCH] memory: transaction API

2011-07-21 Thread Jan Kiszka
On 2011-07-21 16:39, Avi Kivity wrote: On 07/21/2011 05:32 PM, Jan Kiszka wrote: On 2011-07-21 15:50, Avi Kivity wrote: On 07/21/2011 04:17 PM, Jan Kiszka wrote: On 2011-07-21 14:58, Avi Kivity wrote: On 07/21/2011 03:52 PM, Jan Kiszka wrote: The problem is that update can change

Re: [PATCH] memory: transaction API

2011-07-21 Thread Avi Kivity
On 07/21/2011 06:05 PM, Jan Kiszka wrote: The point is _update() can only make changes for one region atomic, while _commit() is more general. You can sometimes batch all changes into a single container region, but sometimes it is clumsy, and sometimes impossible. Deletion and