kernel/vm_manager: Remove redundant Reset call in destructor
This is performing more work than would otherwise be necessary during VMManager's destruction. All we actually want to occur in this scenario is for any allocated memory to be freed, which will happen automatically as the VMManager instance goes out of scope. Anything else being done is simply unnecessary work.
This commit is contained in:
parent
bb776e25a9
commit
1f2e75ecea
1 changed files with 1 additions and 3 deletions
|
@ -40,9 +40,7 @@ VMManager::VMManager(Memory::MemorySystem& memory) : memory(memory) {
|
||||||
Reset();
|
Reset();
|
||||||
}
|
}
|
||||||
|
|
||||||
VMManager::~VMManager() {
|
VMManager::~VMManager() = default;
|
||||||
Reset();
|
|
||||||
}
|
|
||||||
|
|
||||||
void VMManager::Reset() {
|
void VMManager::Reset() {
|
||||||
vma_map.clear();
|
vma_map.clear();
|
||||||
|
|
Loading…
Reference in a new issue