From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, stefano.stabellini@eu.citrix.com,
mtosatti@redhat.com, agraf@suse.de, borntraeger@de.ibm.com,
pbonzini@redhat.com, afaerber@suse.de, rth@twiddle.net
Subject: [Qemu-devel] [PATCH 0/8] ] Guest memory allocation fixes & cleanup
Date: Wed, 19 Jun 2013 13:44:16 +0200 [thread overview]
Message-ID: <1371642264-17704-1-git-send-email-armbru@redhat.com> (raw)
All I wanted to do is exit(1) instead of abort() on guest memory
allocation failure [07/08]. But that lead me into a minor #ifdef bog,
and here's what I brought back. Enjoy!
Testing:
* Christian Borntraeger reports this version works fine under LPAR
(new S390 KVM, i.e. generic allocation) and as second guest under
z/VM (old S390 KVM, i.e. legacy S390 allocation). Thanks for
testing, and for catching a stupid mistake.
Changes since RFC:
* 1-3+8/8 unchanged except for commit message tweaks
* 4+6/8 rewritten to address Paolo's review
* 5/8 rewritten: don't fix dead code, just assert it's dead
* 7/8 fix mistakes caught by Richard Henderson and Peter Maydell
Markus Armbruster (8):
exec: Fix Xen RAM allocation with unusual options
exec: Clean up fall back when -mem-path allocation fails
exec: Reduce ifdeffery around -mem-path
exec: Simplify the guest physical memory allocation hook
exec: Drop incorrect & dead S390 code in qemu_ram_remap()
exec: Clean up unnecessary S390 ifdeffery
exec: Don't abort when we can't allocate guest memory
pc_sysfw: Fix ISA BIOS init for ridiculously big flash
exec.c | 121 ++++++++++++++++++++++++++----------------------
hw/block/pc_sysfw.c | 5 +-
include/exec/cpu-all.h | 2 -
include/exec/exec-all.h | 2 +
include/sysemu/kvm.h | 5 --
kvm-all.c | 13 ------
target-s390x/kvm.c | 23 +++------
util/oslib-posix.c | 4 +-
util/oslib-win32.c | 5 +-
9 files changed, 78 insertions(+), 102 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-06-19 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 11:44 Markus Armbruster [this message]
2013-06-19 11:44 ` [Qemu-devel] [PATCH 1/8] exec: Fix Xen RAM allocation with unusual options Markus Armbruster
2013-06-19 11:44 ` [Qemu-devel] [PATCH 2/8] exec: Clean up fall back when -mem-path allocation fails Markus Armbruster
2013-06-19 11:44 ` [Qemu-devel] [PATCH 3/8] exec: Reduce ifdeffery around -mem-path Markus Armbruster
2013-06-19 11:44 ` [Qemu-devel] [PATCH 4/8] exec: Simplify the guest physical memory allocation hook Markus Armbruster
2013-06-19 12:20 ` Christian Borntraeger
2013-06-19 11:44 ` [Qemu-devel] [PATCH 5/8] exec: Drop incorrect & dead S390 code in qemu_ram_remap() Markus Armbruster
2013-06-19 12:26 ` Christian Borntraeger
2013-06-19 12:56 ` Paolo Bonzini
2013-06-19 13:22 ` Markus Armbruster
2013-06-19 11:44 ` [Qemu-devel] [PATCH 6/8] exec: Clean up unnecessary S390 ifdeffery Markus Armbruster
2013-06-19 11:44 ` [Qemu-devel] [PATCH 7/8] exec: Don't abort when we can't allocate guest memory Markus Armbruster
2013-06-19 11:44 ` [Qemu-devel] [PATCH 8/8] pc_sysfw: Fix ISA BIOS init for ridiculously big flash Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1371642264-17704-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefano.stabellini@eu.citrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).