From: Alex Williamson <alex.williamson@redhat.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Cc: chrisw@redhat.com, alex.williamson@redhat.com, pugs@cisco.com,
mst@redhat.com
Subject: [Qemu-devel] [RFC PATCH 3/5] RAM API: Make use of it for x86 PC
Date: Sun, 11 Jul 2010 12:09:29 -0600 [thread overview]
Message-ID: <20100711180929.20121.19946.stgit@localhost6.localdomain6> (raw)
In-Reply-To: <20100711180910.20121.93313.stgit@localhost6.localdomain6>
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
hw/pc.c | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index a96187f..b9ce6ae 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -911,13 +911,13 @@ void pc_memory_init(ram_addr_t ram_size,
/* allocate RAM */
ram_addr = qemu_ram_alloc(NULL, "pc.ram",
below_4g_mem_size + above_4g_mem_size);
- cpu_register_physical_memory(0, 0xa0000, ram_addr);
- cpu_register_physical_memory(0x100000,
- below_4g_mem_size - 0x100000,
- ram_addr + 0x100000);
+
+ qemu_ram_register(0, 0xa0000, ram_addr);
+ qemu_ram_register(0x100000, below_4g_mem_size - 0x100000,
+ ram_addr + 0x100000);
#if TARGET_PHYS_ADDR_BITS > 32
- cpu_register_physical_memory(0x100000000ULL, above_4g_mem_size,
- ram_addr + below_4g_mem_size);
+ qemu_ram_register(0x100000000ULL, above_4g_mem_size,
+ ram_addr + below_4g_mem_size);
#endif
/* BIOS load */
next prev parent reply other threads:[~2010-07-11 18:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 18:09 [Qemu-devel] [RFC PATCH 0/5] QEMU VFIO device assignment Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 1/5] qemu_ram_map/unmap: Allow pre-allocated space to be mapped Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 2/5] Minimal RAM API support Alex Williamson
2010-07-11 18:18 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:20 ` Avi Kivity
2010-07-11 18:24 ` Alex Williamson
2010-07-11 18:29 ` Avi Kivity
2010-07-11 18:09 ` Alex Williamson [this message]
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 4/5] APIC/IOAPIC EOI callback Alex Williamson
2010-07-11 18:14 ` [Qemu-devel] " Avi Kivity
2010-07-11 18:26 ` Alex Williamson
2010-07-11 18:30 ` Avi Kivity
2010-07-11 18:54 ` Michael S. Tsirkin
2010-07-11 19:21 ` Alex Williamson
2010-07-11 19:23 ` Michael S. Tsirkin
2010-07-11 20:03 ` Alex Williamson
2010-07-11 20:05 ` Michael S. Tsirkin
2010-07-11 20:12 ` Michael S. Tsirkin
2010-07-11 21:59 ` Alex Williamson
2010-07-12 6:33 ` Avi Kivity
2010-07-12 9:05 ` Gleb Natapov
2010-07-12 9:13 ` Avi Kivity
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 5/5] VFIO based device assignment Alex Williamson
2010-07-11 18:27 ` [Qemu-devel] " Avi Kivity
2010-07-11 19:38 ` Alex Williamson
2010-07-12 6:37 ` Avi Kivity
2010-07-11 18:17 ` [Qemu-devel] Re: [RFC PATCH 0/5] QEMU VFIO " Avi Kivity
2010-07-11 18:37 ` Alex Williamson
2010-07-11 18:43 ` Avi Kivity
2010-07-11 20:24 ` Alex Williamson
2010-07-12 6:29 ` Avi Kivity
2010-07-12 11:03 ` Michael S. Tsirkin
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=20100711180929.20121.19946.stgit@localhost6.localdomain6 \
--to=alex.williamson@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pugs@cisco.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 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).