public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: avi@redhat.com, mtosatti@redhat.com
Cc: kvm@vger.kernel.org
Subject: [PATCH 2/3 kvm-unit-tests] dirty-log-perf: Split guest memory into two slots
Date: Sun, 15 Jan 2012 12:44:30 +0900	[thread overview]
Message-ID: <20120115124430.2485071dee7e99b37d4d1776@gmail.com> (raw)
In-Reply-To: <20120115124131.3b460d1d85194edaa251e635@gmail.com>

VGA frame buffer logging may be affected by other large slots like RAM,
so make it possible to test such cases.

E.g. 8K pages for the logged slot and 256K pages for the entire memory
space can be considered as 32MB framebuffer in 1GB memory space.

Signed-off-by: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
---
 api/dirty-log-perf.cc |   11 ++++++++---
 1 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/api/dirty-log-perf.cc b/api/dirty-log-perf.cc
index b9e9796..f48bc95 100644
--- a/api/dirty-log-perf.cc
+++ b/api/dirty-log-perf.cc
@@ -10,6 +10,7 @@ namespace {
 
 const int page_size		= 4096;
 const int64_t nr_total_pages	= 256 * 1024;
+const int64_t nr_slot_pages	= 256 * 1024;
 
 // Return the current time in nanoseconds.
 uint64_t time_ns()
@@ -50,8 +51,8 @@ void check_dirty_log(kvm::vcpu& vcpu, mem_slot& slot, void* slot_head)
     slot.set_dirty_logging(true);
     slot.update_dirty_log();
 
-    for (int64_t i = 1; i <= nr_total_pages; i *= 2) {
-        do_guest_write(vcpu, slot_head, i, nr_total_pages);
+    for (int64_t i = 1; i <= nr_slot_pages; i *= 2) {
+        do_guest_write(vcpu, slot_head, i, nr_slot_pages);
 
         uint64_t start_ns = time_ns();
         slot.update_dirty_log();
@@ -84,7 +85,11 @@ int main(int ac, char **av)
     identity::vm ident_vm(vm, memmap, hole);
     kvm::vcpu vcpu(vm, 0);
 
-    mem_slot slot(memmap, mem_addr, mem_size, mem_head);
+    uint64_t slot_size = nr_slot_pages * page_size;
+    uint64_t next_addr = mem_addr + slot_size;
+    uint64_t next_size = mem_size - slot_size;
+    mem_slot slot(memmap, mem_addr, slot_size, mem_head);
+    mem_slot other_slot(memmap, next_addr, next_size, (void *)next_addr);
 
     // pre-allocate shadow pages
     do_guest_write(vcpu, mem_head, nr_total_pages, nr_total_pages);
-- 
1.7.5.4


  parent reply	other threads:[~2012-01-15  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15  3:41 [PATCH 0/3 kvm-unit-tests] Dirty logging performance test Takuya Yoshikawa
2012-01-15  3:43 ` [PATCH v2 1/3 kvm-unit-tests] Add dirty " Takuya Yoshikawa
2012-01-15  3:44 ` Takuya Yoshikawa [this message]
2012-01-15  3:45 ` [PATCH 3/3 kvm-unit-tests] dirty-log-perf: Take slot size from command line Takuya Yoshikawa
2012-01-18 13:50 ` [PATCH 0/3 kvm-unit-tests] Dirty logging performance test Marcelo Tosatti

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=20120115124430.2485071dee7e99b37d4d1776@gmail.com \
    --to=takuya.yoshikawa@gmail.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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