From: "Zhang, Xiantao" <xiantao.zhang@intel.com>
To: kvm-ia64@vger.kernel.org
Subject: [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping
Date: Tue, 28 Apr 2009 09:29:19 +0000 [thread overview]
Message-ID: <706158FABBBA044BAD4FE898A02E4BC236A2BC03@pdsmsx503.ccr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
From d184d9b0a91ca674961000ed3d35b7fc25d29e03 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang <xiantao.zhang@intel.com>
Date: Tue, 28 Apr 2009 16:59:36 +0800
Subject: [PATCH] qemu-kvm: other archs should maintain memory mapping also.
Currently, use TARGET_I386 to comment out the mapping machanism
for other archs, but mapping machanism should be useful for other archs
to maintain guest's memory mapping.
Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
---
qemu-kvm.c | 6 +-----
1 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/qemu-kvm.c b/qemu-kvm.c
index 68a9218..4f71192 100644
--- a/qemu-kvm.c
+++ b/qemu-kvm.c
@@ -846,6 +846,7 @@ static int must_use_aliases_target(target_phys_addr_t addr)
return true;
return false;
}
+#endif
static struct mapping {
target_phys_addr_t phys;
@@ -885,7 +886,6 @@ static void drop_mapping(target_phys_addr_t start_addr)
if (p)
*p = mappings[--nr_mappings];
}
-#endif
void kvm_cpu_register_physical_memory(target_phys_addr_t start_addr,
unsigned long size,
@@ -893,9 +893,7 @@ void kvm_cpu_register_physical_memory(target_phys_addr_t start_addr,
{
int r = 0;
unsigned long area_flags;
-#ifdef TARGET_I386
struct mapping *p;
-#endif
if (start_addr + size > phys_ram_size) {
phys_ram_size = start_addr + size;
@@ -955,13 +953,11 @@ void kvm_cpu_register_physical_memory(target_phys_addr_t start_addr,
exit(1);
}
-#ifdef TARGET_I386
drop_mapping(start_addr);
p = &mappings[nr_mappings++];
p->phys = start_addr;
p->ram = phys_offset;
p->len = size;
-#endif
return;
}
--
1.6.0
[-- Attachment #2: 0004-qemu-kvm-other-archs-should-maintain-memory-mapping.patch --]
[-- Type: application/octet-stream, Size: 1698 bytes --]
From d184d9b0a91ca674961000ed3d35b7fc25d29e03 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang <xiantao.zhang@intel.com>
Date: Tue, 28 Apr 2009 16:59:36 +0800
Subject: [PATCH] qemu-kvm: other archs should maintain memory mapping also.
Currently, use TARGET_I386 to comment out the mapping machanism
for other archs, but mapping machanism should be useful for other archs
to maintain guest's memory mapping.
Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
---
qemu-kvm.c | 6 +-----
1 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/qemu-kvm.c b/qemu-kvm.c
index 68a9218..4f71192 100644
--- a/qemu-kvm.c
+++ b/qemu-kvm.c
@@ -846,6 +846,7 @@ static int must_use_aliases_target(target_phys_addr_t addr)
return true;
return false;
}
+#endif
static struct mapping {
target_phys_addr_t phys;
@@ -885,7 +886,6 @@ static void drop_mapping(target_phys_addr_t start_addr)
if (p)
*p = mappings[--nr_mappings];
}
-#endif
void kvm_cpu_register_physical_memory(target_phys_addr_t start_addr,
unsigned long size,
@@ -893,9 +893,7 @@ void kvm_cpu_register_physical_memory(target_phys_addr_t start_addr,
{
int r = 0;
unsigned long area_flags;
-#ifdef TARGET_I386
struct mapping *p;
-#endif
if (start_addr + size > phys_ram_size) {
phys_ram_size = start_addr + size;
@@ -955,13 +953,11 @@ void kvm_cpu_register_physical_memory(target_phys_addr_t start_addr,
exit(1);
}
-#ifdef TARGET_I386
drop_mapping(start_addr);
p = &mappings[nr_mappings++];
p->phys = start_addr;
p->ram = phys_offset;
p->len = size;
-#endif
return;
}
--
1.6.0
next reply other threads:[~2009-04-28 9:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:29 Zhang, Xiantao [this message]
2009-04-28 9:39 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Avi Kivity
2009-04-29 14:59 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Jes Sorensen
2009-04-29 15:04 ` Re: [PATCH 04/04] qemu-kvm: other archs should maintain memory Jes Sorensen
2009-04-29 15:06 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Jes Sorensen
2009-05-04 8:51 ` Avi Kivity
2009-05-04 8:59 ` Avi Kivity
2009-05-04 9:17 ` Jes Sorensen
2009-05-04 9:25 ` Jes Sorensen
2009-05-04 21:57 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory Hollis Blanchard
2009-05-11 10:15 ` Zhang, Xiantao
2009-05-11 11:18 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Jes Sorensen
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=706158FABBBA044BAD4FE898A02E4BC236A2BC03@pdsmsx503.ccr.corp.intel.com \
--to=xiantao.zhang@intel.com \
--cc=kvm-ia64@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).