KVM: PPC: BOOK3S: HV: CMA: Reserve cma region only in hypervisor mode
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Trusty |
Fix Released
|
Medium
|
Chris J Arges | ||
| Utopic |
Fix Released
|
Medium
|
Chris J Arges | ||
Bug Description
SRU Justification:
[Impact]
KVM guests on PowerNV allocate memory for CMA in kvm_cma_reserve unnecessarily leading to additional memory consumption.
[Test Case]
Boot a KVM guest on PowerNV and measure the differences in memory consumption with and without this patch.
[Fix]
commit cec26bc3c125b5d
in v3.18-rc1
--
Problem Description
==================
This bugzilla is opened to track the inclusion of the upstream commit mentioned below:
commit cec26bc3c125b5d
Author: Aneesh Kumar K.V <email address hidden>
Date: Mon Sep 29 13:32:38 2014 +0530
KVM: PPC: BOOK3S: HV: CMA: Reserve cma region only in hypervisor mode
We use cma reserved area for creating guest hash page table.
Don't do the reservation in non-hypervisor mode. This avoids unnecessary
CMA reservation when booting with limited memory configs like
fadump and kdump.
---uname output---
ubuntu14.10
Machine Type = ppc64
| tags: | added: architecture-ppc64le bugnameltc-119457 severity-high targetmilestone-inin--- |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #1 |
| tags: | added: bot-comment |
| affects: | ubuntu → linux (Ubuntu) |
| Changed in linux (Ubuntu): | |
| status: | New → Fix Released |
| Changed in linux (Ubuntu Trusty): | |
| assignee: | nobody → Chris J Arges (arges) |
| Changed in linux (Ubuntu Utopic): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Utopic): | |
| assignee: | nobody → Chris J Arges (arges) |
| Changed in linux (Ubuntu Trusty): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Utopic): | |
| status: | New → In Progress |
| Changed in linux (Ubuntu Trusty): | |
| status: | New → In Progress |
| Changed in linux (Ubuntu Utopic): | |
| status: | In Progress → Fix Committed |
| Changed in linux (Ubuntu Trusty): | |
| status: | In Progress → Fix Committed |
| tags: |
added: targetmilestone-inin1410 removed: targetmilestone-inin--- |
| Brad Figg (brad-figg) wrote | #3 |
| tags: | added: verification-needed-trusty |
| tags: | added: verification-needed-utopic |
| Brad Figg (brad-figg) wrote | #4 |
| Breno Leitão (breno-leitao) wrote | #5 |
| tags: |
added: verification-done-utopic removed: verification-needed-utopic |
| Breno Leitão (breno-leitao) wrote | #6 |
| tags: |
added: verification-done-trusty removed: verification-needed-trusty |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in linux (Ubuntu Utopic): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #8 |
| Changed in linux (Ubuntu Trusty): | |
| status: | Fix Committed → Fix Released |
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #9 |
| tags: | removed: verification-done-trusty verification-done-utopic |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/
To change the source package that this bug is filed about visit https:/
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]