| commit | f0bc8d7271c4480dd71a6fe81aeb957d688f1888 | |
| author | Anthony Liguori <aliguori@us.ibm.com> | |
| Wed, 7 May 2008 18:09:36 +0000 (7 13:09 -0500) | ||
| committer | Avi Kivity <avi@qumranet.com> | |
| Fri, 9 May 2008 15:22:00 +0000 (9 18:22 +0300) | ||
| tree | 87a43a11557d3e2c450b76c9eb429bce2a81fdef | treesnapshot (tar.gz zip) |
| parent | 3512445e5aab4684d45c923647063cf81e9d4331 | commitdiff |
Support more than 3.5GB with virtio
We're pretty sloppy in virtio right now about phys_ram_base assumptions. This
patch is an incremental step between what we have today and a full blown DMA
API. I backported the DMA API but the performance impact was not acceptable
to me. There's only a slight performance impact with this particular patch.
Since we're no longer assuming guest physical memory is contiguous, we need
a more complex way to validate the memory regions than just checking if it's
within ram_size.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
We're pretty sloppy in virtio right now about phys_ram_base assumptions. This
patch is an incremental step between what we have today and a full blown DMA
API. I backported the DMA API but the performance impact was not acceptable
to me. There's only a slight performance impact with this particular patch.
Since we're no longer assuming guest physical memory is contiguous, we need
a more complex way to validate the memory regions than just checking if it's
within ram_size.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
| hw/virtio.c | diffblobblamehistory |