summaryrefslogtreecommitdiffstats
path: root/mm/hugetlb.c
diff options
context:
space:
mode:
authorSerhii Popovych <spopovyc@redhat.com>2017-12-04 09:36:41 -0500
committerPaul Mackerras <paulus@ozlabs.org>2017-12-06 13:35:21 +1100
commit3073774e638ef18d222465fe92bfc8fccb90d288 (patch)
tree9743ab541a7aac8b4a59b1d8dfe39cd36b1f4405 /mm/hugetlb.c
parenta63dd7480d8f3c2b52e1e2bcab83e3e64c7c61a1 (diff)
downloadop-kernel-dev-3073774e638ef18d222465fe92bfc8fccb90d288.zip
op-kernel-dev-3073774e638ef18d222465fe92bfc8fccb90d288.tar.gz
KVM: PPC: Book3S HV: Drop prepare_done from struct kvm_resize_hpt
Currently the kvm_resize_hpt structure has two fields relevant to the state of an ongoing resize: 'prepare_done', which indicates whether the worker thread has completed or not, and 'error' which indicates whether it was successful or not. Since the success/failure isn't known until completion, this is confusingly redundant. This patch consolidates the information into just the 'error' value: -EBUSY indicates the worked is still in progress, other negative values indicate (completed) failure, 0 indicates successful completion. As a bonus this reduces size of struct kvm_resize_hpt by __alignof__(struct kvm_hpt_info) and saves few bytes of code. While there correct comment in struct kvm_resize_hpt which references a non-existent semaphore (leftover from an early draft). Assert with WARN_ON() in case of HPT allocation thread work runs more than once for resize request or resize_hpt_allocate() returns -EBUSY that is treated specially. Change comparison against zero to make checkpatch.pl happy. Cc: stable@vger.kernel.org # v4.10+ Signed-off-by: Serhii Popovych <spopovyc@redhat.com> [dwg: Changed BUG_ON()s to WARN_ON()s and altered commit message for clarity] Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'mm/hugetlb.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud