1. 29 10月, 2012 3 次提交
  2. 27 10月, 2012 2 次提交
  3. 23 10月, 2012 7 次提交
  4. 22 10月, 2012 4 次提交
  5. 20 10月, 2012 12 次提交
  6. 18 10月, 2012 3 次提交
  7. 17 10月, 2012 1 次提交
    • A
      i440fx: avoid destroying memory regions within a transaction · 2725aec7
      Avi Kivity 提交于
      Calling memory_region_destroy() within a transaction is illegal, since
      the memory API is allowed to continue to dispatch to a region until the
      transaction commits.  440fx does that however when managing PAM registers.
      
      This bug is benign, since the regions are all aliases (which the memory
      core tends to throw anyway), and since we don't do concurrent dispatch yet,
      but instead of relying on that, tighten ship ahead of the coming concurrency
      storm.
      
      Fix by having a predefined set of regions, of which one will be enabled at
      any time.
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      2725aec7
  8. 15 10月, 2012 4 次提交
  9. 13 10月, 2012 4 次提交