diff options
| author | Wanpeng Li <wanpeng.li@linux.intel.com> | 2015-04-15 05:24:54 +0300 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-04-15 18:01:01 +0300 |
| commit | 130005231c9f2090b1b177e2cca9841b562c1784 (patch) | |
| tree | 3a08b71fe1577f3848af20f47381ae661d664243 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 95fce4fa0850da8f85ecf8d069ab3fc6c8bc1478 (diff) | |
| download | linux-130005231c9f2090b1b177e2cca9841b562c1784.tar.xz | |
kvm: mmu: don't do memslot overflow check
As Andres pointed out:
| I don't understand the value of this check here. Are we looking for a
| broken memslot? Shouldn't this be a BUG_ON? Is this the place to care
| about these things? npages is capped to KVM_MEM_MAX_NR_PAGES, i.e.
| 2^31. A 64 bit overflow would be caused by a gigantic gfn_start which
| would be trouble in many other ways.
This patch drops the memslot overflow check to make the codes more simple.
Reviewed-by: Andres Lagar-Cavilla <andreslc@google.com>
Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
Message-Id: <1429064694-3072-1-git-send-email-wanpeng.li@linux.intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions