| commit | 0ae076bf40782c48b1b26ca63ed2c349532dd81e | [log] [tgz] |
|---|---|---|
| author | José Fonseca <jfonseca@vmware.com> | Thu Jan 21 12:12:33 2010 -0800 |
| committer | José Fonseca <jfonseca@vmware.com> | Thu Jan 21 15:18:40 2010 -0800 |
| tree | c47c315f753c09746d80680bf382ee53fb38729d | |
| parent | efc08bddb7622e4acfa795b58e1264b64b78ab4f [diff] |
svga: Follow buffer usage semantics properly. It's necessary to download buffers from the host always, except if the buffer is undefined, because: - just PIPE_BUFFER_USAGE_CPU_WRITE doesn't guarantee all data is written -- old contents may still pierce through - PIPE_BUFFER_USAGE_DISCARD refers to a range, not the whole buffer, so unless we track which parts have been modified and not we still need to download the data.