From: Alexander Graf <agraf@suse.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Carsten Otte <cotte@de.ibm.com>
Subject: [Qemu-devel] [PATCH 1/9] Export function for VA defined ram allocation
Date: Wed, 21 Oct 2009 11:24:58 +0200 [thread overview]
Message-ID: <1256117106-9475-2-git-send-email-agraf@suse.de> (raw)
In-Reply-To: <1256117106-9475-1-git-send-email-agraf@suse.de>
S390 requires vmas for guests to be < 256 GB. So we need to directly export
mmaps "try to use this vma as start address" feature to not accidently get
over that limit.
Signed-off-by: Alexander Graf <agraf@suse.de>
---
cpu-common.h | 1 +
exec.c | 15 +++++++++++++--
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/cpu-common.h b/cpu-common.h
index 6302372..ecaf9e3 100644
--- a/cpu-common.h
+++ b/cpu-common.h
@@ -30,6 +30,7 @@ static inline void cpu_register_physical_memory(target_phys_addr_t start_addr,
ram_addr_t cpu_get_physical_page_desc(target_phys_addr_t addr);
ram_addr_t qemu_ram_alloc(ram_addr_t);
+ram_addr_t _qemu_ram_alloc(ram_addr_t size, void *map_at);
void qemu_ram_free(ram_addr_t addr);
/* This should only be used for ram local to a device. */
void *qemu_get_ram_ptr(ram_addr_t addr);
diff --git a/exec.c b/exec.c
index 076d26b..36c26cd 100644
--- a/exec.c
+++ b/exec.c
@@ -2404,14 +2404,20 @@ void qemu_unregister_coalesced_mmio(target_phys_addr_t addr, ram_addr_t size)
kvm_uncoalesce_mmio_region(addr, size);
}
-ram_addr_t qemu_ram_alloc(ram_addr_t size)
+ram_addr_t _qemu_ram_alloc(ram_addr_t size, void *map_at)
{
RAMBlock *new_block;
size = TARGET_PAGE_ALIGN(size);
new_block = qemu_malloc(sizeof(*new_block));
- new_block->host = qemu_vmalloc(size);
+ if (map_at) {
+ new_block->host = mmap(map_at, size, PROT_EXEC|PROT_READ|PROT_WRITE,
+ MAP_SHARED | MAP_ANONYMOUS, -1, 0);
+
+ } else {
+ new_block->host = qemu_vmalloc(size);
+ }
#ifdef MADV_MERGEABLE
madvise(new_block->host, size, MADV_MERGEABLE);
#endif
@@ -2434,6 +2440,11 @@ ram_addr_t qemu_ram_alloc(ram_addr_t size)
return new_block->offset;
}
+ram_addr_t qemu_ram_alloc(ram_addr_t size)
+{
+ return _qemu_ram_alloc(size, NULL);
+}
+
void qemu_ram_free(ram_addr_t addr)
{
/* TODO: implement this. */
--
1.6.0.2
next prev parent reply other threads:[~2009-10-21 9:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 9:24 [Qemu-devel] [PATCH 0/9] S390x KVM support v2 Alexander Graf
2009-10-21 9:24 ` Alexander Graf [this message]
2009-10-21 9:24 ` [Qemu-devel] [PATCH 2/9] Add KVM support for S390x Alexander Graf
2009-10-21 9:25 ` [Qemu-devel] [PATCH 3/9] Add support for S390x system emulation Alexander Graf
2009-10-21 9:25 ` [Qemu-devel] [PATCH 4/9] Add S390x virtio machine bus Alexander Graf
2009-10-21 9:25 ` [Qemu-devel] [PATCH 5/9] Add S390x virtio machine description Alexander Graf
2009-10-21 9:25 ` [Qemu-devel] [PATCH 6/9] S390 GDB stub Alexander Graf
2009-10-21 9:25 ` [Qemu-devel] [PATCH 7/9] Implement early printk in virtio-console Alexander Graf
2009-10-21 9:25 ` [Qemu-devel] [PATCH 8/9] Set default console to virtio on S390x Alexander Graf
2009-10-21 9:25 ` [Qemu-devel] [PATCH 9/9] Move mp_state to CPU_COMMON Alexander Graf
2009-10-21 14:29 ` [Qemu-devel] [PATCH 1/9] Export function for VA defined ram allocation Anthony Liguori
2009-10-21 16:02 ` Alexander Graf
2009-10-21 16:54 ` Anthony Liguori
2009-10-21 17:03 ` Alexander Graf
2009-10-21 18:06 ` Anthony Liguori
2009-10-21 18:27 ` Alexander Graf
2009-10-21 18:30 ` Anthony Liguori
2009-10-21 18:42 ` [Qemu-devel] " Paolo Bonzini
2009-10-21 18:48 ` Anthony Liguori
2009-10-22 5:39 ` [Qemu-devel] " Carsten Otte
2009-10-21 11:03 ` [Qemu-devel] Re: [PATCH 0/9] S390x KVM support v2 Carsten Otte
-- strict thread matches above, loose matches on Subject: below --
2009-10-19 14:37 [Qemu-devel] [PATCH 0/9] S390x KVM support Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 1/9] Export function for VA defined ram allocation Alexander Graf
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=1256117106-9475-2-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=cotte@de.ibm.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.