Skip to contentSkip to conversation

accel/tcg/plugin: host insn size for plugin

PATCH In review Fei Wu 3 participants 18 messages Apr 6, 2023 – Apr 21, 2023

lore
Share & tools
lore

Fei Wu

author
#0 lore raw

cover accel/tcg/plugin: host insn size for plugin

The translation ratio of host to guest instruction count is one of the key performance factor of binary translation. It's better to have this kind of information exported to plugin for analysis. As the host insn size is not determined at guest->IR time, its address is recorded for later dereference, and plugin inline mode is not supported.

Here is an example of the output with modified plugin hotblocks:

    pc, tcount, icount, ecount, host isize
    0xffffffff8041ad6c, 1, 9, 130450345, 456
    0xffffffff800084f0, 1, 9, 88273714, 264
    0xffffffff800084e4, 1, 3, 88264146, 135
    0xffffffff8041abd0, 1, 1, 46032689, 123
    0xffffffff8041ab3c, 1, 1, 46021650, 123
    0xffffffff8045ffe8, 1, 5, 40927215, 328

Fei Wu (2):
accel/tcg/plugin: export host insn size
plugins/hotblocks: add host insn size

 accel/tcg/plugin-gen.c       |  1 +
 contrib/plugins/hotblocks.c  | 24 +++++++++++++++---------
 include/qemu/plugin.h        |  2 ++
 include/qemu/qemu-plugin.h   |  8 ++++++++
 plugins/api.c                |  5 +++++
 plugins/qemu-plugins.symbols |  1 +
 6 files changed, 32 insertions(+), 9 deletions(-)
Signature · 1 line
2.25.1
author
#16 lore raw

PATCH 2/2 plugins/hotblocks: add host insn size

It's only valid when inline=false, otherwise it's default to 0.

---
 contrib/plugins/hotblocks.c | 24 +++++++++++++++---------
 1 file changed, 15 insertions(+), 9 deletions(-)
contrib/plugins/hotblocks.c +15 -9
index 062200a7a4..c9716da7fe 100644
@@ -37,6 +37,8 @@ typedef struct {
     uint64_t exec_count;
     int      trans_count;
     unsigned long insns;
+    void    *p_host_insn_size;
+    uint64_t host_insn_size;
 } ExecCount;
 
 static gint cmp_exec_count(gconstpointer a, gconstpointer b)
@@ -59,13 +61,17 @@ static void plugin_exit(qemu_plugin_id_t id, void *p)
     it = g_list_sort(counts, cmp_exec_count);
 
     if (it) {
-        g_string_append_printf(report, "pc, tcount, icount, ecount\n");
+        g_string_append_printf(report,
+                               "host isize is only valid when inline=false\n"
+                               "pc, tcount, icount, ecount, host isize\n");
 
         for (i = 0; i < limit && it->next; i++, it = it->next) {
             ExecCount *rec = (ExecCount *) it->data;
-            g_string_append_printf(report, "0x%016"PRIx64", %d, %ld, %"PRId64"\n",
+            g_string_append_printf(report, "0x%016"PRIx64", %d, %ld, %"PRId64
+                                   ", %"PRIu64"\n",
                                    rec->start_addr, rec->trans_count,
-                                   rec->insns, rec->exec_count);
+                                   rec->insns, rec->exec_count,
+                                   rec->host_insn_size);
         }
 
         g_list_free(it);
@@ -82,14 +88,13 @@ static void plugin_init(void)
 
 static void vcpu_tb_exec(unsigned int cpu_index, void *udata)
 {
-    ExecCount *cnt;
-    uint64_t hash = (uint64_t) udata;
+    ExecCount *cnt = (ExecCount *) udata;
 
     g_mutex_lock(&lock);
-    cnt = (ExecCount *) g_hash_table_lookup(hotblocks, (gconstpointer) hash);
-    /* should always succeed */
-    g_assert(cnt);
     cnt->exec_count++;
+    if (cnt->host_insn_size == 0) {
+        cnt->host_insn_size = *((uint64_t *)cnt->p_host_insn_size);
+    }
     g_mutex_unlock(&lock);
 }
 
@@ -114,6 +119,7 @@ static void vcpu_tb_trans(qemu_plugin_id_t id, struct qemu_plugin_tb *tb)
         cnt->start_addr = pc;
         cnt->trans_count = 1;
         cnt->insns = insns;
+        cnt->p_host_insn_size = qemu_plugin_tb_host_insn_size(tb);
         g_hash_table_insert(hotblocks, (gpointer) hash, (gpointer) cnt);
     }
 
@@ -125,7 +131,7 @@ static void vcpu_tb_trans(qemu_plugin_id_t id, struct qemu_plugin_tb *tb)
     } else {
         qemu_plugin_register_vcpu_tb_exec_cb(tb, vcpu_tb_exec,
                                              QEMU_PLUGIN_CB_NO_REGS,
-                                             (void *)hash);
+                                             (void *)cnt);
     }
 }
 
Signature · 1 line
2.25.1
author
#1 lore raw

PATCH 1/2 accel/tcg/plugin: export host insn size

In reply to Fei Wu

The translation ratio of host to guest instruction count is one of the key performance factor of binary translation. TCG doesn't collect host instruction count at present, it does collect host instruction size instead, although they are not the same thing as instruction size might not be fixed, instruction size is still a valid estimation.

---
 accel/tcg/plugin-gen.c       | 1 +
 include/qemu/plugin.h        | 2 ++
 include/qemu/qemu-plugin.h   | 8 ++++++++
 plugins/api.c                | 5 +++++
 plugins/qemu-plugins.symbols | 1 +
 5 files changed, 17 insertions(+)
accel/tcg/plugin-gen.c +1 -0
index 5efb8db258..4a3ca8fa2f 100644
@@ -881,6 +881,7 @@ bool plugin_gen_tb_start(CPUState *cpu, const DisasContextBase *db,
         ptb->haddr2 = NULL;
         ptb->mem_only = mem_only;
         ptb->mem_helper = false;
+        ptb->host_insn_size = &db->tb->tc.size;
 
         plugin_gen_empty_callback(PLUGIN_GEN_FROM_TB);
     }
include/qemu/plugin.h +2 -0
index bc0781cab8..b38fd139e1 100644
@@ -151,6 +151,8 @@ struct qemu_plugin_tb {
     /* if set, the TB calls helpers that might access guest memory */
     bool mem_helper;
 
+    uint64_t *host_insn_size;
+
     GArray *cbs[PLUGIN_N_CB_SUBTYPES];
 };
 
include/qemu/qemu-plugin.h +8 -0
index 50a9957279..2397574a21 100644
@@ -336,6 +336,14 @@ void qemu_plugin_register_vcpu_insn_exec_inline(struct qemu_plugin_insn *insn,
  */
 size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb);
 
+/**
+ * qemu_plugin_tb_n_insns() - query helper for host insns size in TB
+ * @tb: opaque handle to TB passed to callback
+ *
+ * Returns: address of host insns size of this block
+ */
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb);
+
 /**
  * qemu_plugin_tb_vaddr() - query helper for vaddr of TB start
  * @tb: opaque handle to TB passed to callback
plugins/api.c +5 -0
index 2078b16edb..0d70cb1f0f 100644
@@ -188,6 +188,11 @@ size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb)
     return tb->n;
 }
 
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb)
+{
+    return tb->host_insn_size;
+}
+
 uint64_t qemu_plugin_tb_vaddr(const struct qemu_plugin_tb *tb)
 {
     return tb->vaddr;
plugins/qemu-plugins.symbols +1 -0
index 71f6c90549..3e92c3b8ba 100644
@@ -39,6 +39,7 @@
   qemu_plugin_start_code;
   qemu_plugin_tb_get_insn;
   qemu_plugin_tb_n_insns;
+  qemu_plugin_tb_host_insn_size;
   qemu_plugin_tb_vaddr;
   qemu_plugin_uninstall;
   qemu_plugin_vcpu_for_each;
Signature · 1 line
2.25.1
#2 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 5 lines · Fei Wu

The translation ratio of host to guest instruction count is one of the key performance factor of binary translation. TCG doesn't collect host instruction count at present, it does collect host instruction size instead, although they are not the same thing as instruction size might not be fixed, instruction size is still a valid estimation.

I'm not so sure about exposing this information to plugins because we try to avoid leaking internal implementation details to plugins. Aside from that the very act of instrumenting will increase the size of the target buffer.

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.

Richard, what do you think?

Quoted 40 lines
---
 accel/tcg/plugin-gen.c       | 1 +
 include/qemu/plugin.h        | 2 ++
 include/qemu/qemu-plugin.h   | 8 ++++++++
 plugins/api.c                | 5 +++++
 plugins/qemu-plugins.symbols | 1 +
 5 files changed, 17 insertions(+)
accel/tcg/plugin-gen.c +1 -0
index 5efb8db258..4a3ca8fa2f 100644
@@ -881,6 +881,7 @@ bool plugin_gen_tb_start(CPUState *cpu, const DisasContextBase *db,
         ptb->haddr2 = NULL;
         ptb->mem_only = mem_only;
         ptb->mem_helper = false;
+        ptb->host_insn_size = &db->tb->tc.size;
 
         plugin_gen_empty_callback(PLUGIN_GEN_FROM_TB);
     }
include/qemu/plugin.h +2 -0
index bc0781cab8..b38fd139e1 100644
@@ -151,6 +151,8 @@ struct qemu_plugin_tb {
     /* if set, the TB calls helpers that might access guest memory */
     bool mem_helper;
 
+    uint64_t *host_insn_size;
+
     GArray *cbs[PLUGIN_N_CB_SUBTYPES];
 };
 
include/qemu/qemu-plugin.h +0 -0
index 50a9957279..2397574a21 100644

include/qemu/qemu-plugin.h void qemu_plugin_register_vcpu_insn_exec_inline(struct qemu_plugin_insn *insn, · line 343

Quoted 8 lines
include/qemu/qemu-plugin.h +5 -0
@@ -336,6 +336,14 @@ void qemu_plugin_register_vcpu_insn_exec_inline(struct qemu_plugin_insn *insn,
  */
 size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb);
 
+/**
+ * qemu_plugin_tb_n_insns() - query helper for host insns size in TB
+ * @tb: opaque handle to TB passed to callback
+ *
+ * Returns: address of host insns size of this block

If we went ahead with this we need to be very clear when you can call this helper because the data will only be valid at certain points (which is another argument against this).

Quoted 34 lines
include/qemu/qemu-plugin.h +3 -0
+ */
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb);
+
 /**
  * qemu_plugin_tb_vaddr() - query helper for vaddr of TB start
  * @tb: opaque handle to TB passed to callback
plugins/api.c +5 -0
index 2078b16edb..0d70cb1f0f 100644
@@ -188,6 +188,11 @@ size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb)
     return tb->n;
 }
 
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb)
+{
+    return tb->host_insn_size;
+}
+
 uint64_t qemu_plugin_tb_vaddr(const struct qemu_plugin_tb *tb)
 {
     return tb->vaddr;
plugins/qemu-plugins.symbols +1 -0
index 71f6c90549..3e92c3b8ba 100644
@@ -39,6 +39,7 @@
   qemu_plugin_start_code;
   qemu_plugin_tb_get_insn;
   qemu_plugin_tb_n_insns;
+  qemu_plugin_tb_host_insn_size;
   qemu_plugin_tb_vaddr;
   qemu_plugin_uninstall;
   qemu_plugin_vcpu_for_each;
Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
#17 lore raw

Re: [PATCH 2/2] plugins/hotblocks: add host insn size

In reply to Fei Wu
Quoted 46 lines · Fei Wu

It's only valid when inline=false, otherwise it's default to 0.

---
 contrib/plugins/hotblocks.c | 24 +++++++++++++++---------
 1 file changed, 15 insertions(+), 9 deletions(-)
contrib/plugins/hotblocks.c +9 -4
index 062200a7a4..c9716da7fe 100644
@@ -37,6 +37,8 @@ typedef struct {
     uint64_t exec_count;
     int      trans_count;
     unsigned long insns;
+    void    *p_host_insn_size;
+    uint64_t host_insn_size;
 } ExecCount;
 
 static gint cmp_exec_count(gconstpointer a, gconstpointer b)
@@ -59,13 +61,17 @@ static void plugin_exit(qemu_plugin_id_t id, void *p)
     it = g_list_sort(counts, cmp_exec_count);
 
     if (it) {
-        g_string_append_printf(report, "pc, tcount, icount, ecount\n");
+        g_string_append_printf(report,
+                               "host isize is only valid when inline=false\n"
+                               "pc, tcount, icount, ecount, host isize\n");
 
         for (i = 0; i < limit && it->next; i++, it = it->next) {
             ExecCount *rec = (ExecCount *) it->data;
-            g_string_append_printf(report, "0x%016"PRIx64", %d, %ld, %"PRId64"\n",
+            g_string_append_printf(report, "0x%016"PRIx64", %d, %ld, %"PRId64
+                                   ", %"PRIu64"\n",
                                    rec->start_addr, rec->trans_count,
-                                   rec->insns, rec->exec_count);
+                                   rec->insns, rec->exec_count,
+                                   rec->host_insn_size);
         }
 
         g_list_free(it);
@@ -82,14 +88,13 @@ static void plugin_init(void)
 
 static void vcpu_tb_exec(unsigned int cpu_index, void *udata)
 {
-    ExecCount *cnt;

contrib/plugins/hotblocks.c static void plugin_init(void) · line 96

Quoted 10 lines
contrib/plugins/hotblocks.c +3 -4
-    uint64_t hash = (uint64_t) udata;
+    ExecCount *cnt = (ExecCount *) udata;
 
     g_mutex_lock(&lock);
-    cnt = (ExecCount *) g_hash_table_lookup(hotblocks, (gconstpointer) hash);
-    /* should always succeed */
-    g_assert(cnt);
     cnt->exec_count++;
+    if (cnt->host_insn_size == 0) {
+        cnt->host_insn_size = *((uint64_t *)cnt->p_host_insn_size);

No - passing an internal TCG pointer across different phases of translation/execution is a definite no no. We explicitly state that handles are only valid for callbacks in the docs:

Lifetime of the query handle
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Each callback provides an opaque anonymous information handle which can usually be further queried to find out information about a translation, instruction or operation. The handles themselves are only valid during the lifetime of the callback so it is important that any information that is needed is extracted during the callback and saved by the plugin.

to avoid this sort of tangling of implementation details into the plugins.

Quoted 20 lines
contrib/plugins/hotblocks.c +3 -1
+    }
     g_mutex_unlock(&lock);
 }
 
@@ -114,6 +119,7 @@ static void vcpu_tb_trans(qemu_plugin_id_t id, struct qemu_plugin_tb *tb)
         cnt->start_addr = pc;
         cnt->trans_count = 1;
         cnt->insns = insns;
+        cnt->p_host_insn_size = qemu_plugin_tb_host_insn_size(tb);
         g_hash_table_insert(hotblocks, (gpointer) hash, (gpointer) cnt);
     }
 
@@ -125,7 +131,7 @@ static void vcpu_tb_trans(qemu_plugin_id_t id, struct qemu_plugin_tb *tb)
     } else {
         qemu_plugin_register_vcpu_tb_exec_cb(tb, vcpu_tb_exec,
                                              QEMU_PLUGIN_CB_NO_REGS,
-                                             (void *)hash);
+                                             (void *)cnt);
     }
 }
Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
author
#3 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

In reply to Alex Bennée
Quoted 14 lines · Alex Bennée
Quoted 5 lines · Fei Wu

The translation ratio of host to guest instruction count is one of the key performance factor of binary translation. TCG doesn't collect host instruction count at present, it does collect host instruction size instead, although they are not the same thing as instruction size might not be fixed, instruction size is still a valid estimation.

I'm not so sure about exposing this information to plugins because we try to avoid leaking internal implementation details to plugins. Aside from that the very act of instrumenting will increase the size of the target buffer.

Quoted 5 lines

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.

"info jit" collects the translation time expansion ratio, it doesn't distinguish between hot and cold blocks:
TB avg target size 14 max=1918 bytes
TB avg host size 287 bytes (expansion ratio: 19.7)

My primary aim is to collect the runtime expansion ratio, so hot blocks weigh more than cold blocks. My concern is this series might not be the proper way to implement it, just as you mentioned in another reply.

Thanks,
Fei.

Quoted 91 lines

Richard, what do you think?

Quoted 40 lines
---
 accel/tcg/plugin-gen.c       | 1 +
 include/qemu/plugin.h        | 2 ++
 include/qemu/qemu-plugin.h   | 8 ++++++++
 plugins/api.c                | 5 +++++
 plugins/qemu-plugins.symbols | 1 +
 5 files changed, 17 insertions(+)
accel/tcg/plugin-gen.c +1 -0
index 5efb8db258..4a3ca8fa2f 100644
@@ -881,6 +881,7 @@ bool plugin_gen_tb_start(CPUState *cpu, const DisasContextBase *db,
         ptb->haddr2 = NULL;
         ptb->mem_only = mem_only;
         ptb->mem_helper = false;
+        ptb->host_insn_size = &db->tb->tc.size;
 
         plugin_gen_empty_callback(PLUGIN_GEN_FROM_TB);
     }
include/qemu/plugin.h +2 -0
index bc0781cab8..b38fd139e1 100644
@@ -151,6 +151,8 @@ struct qemu_plugin_tb {
     /* if set, the TB calls helpers that might access guest memory */
     bool mem_helper;
 
+    uint64_t *host_insn_size;
+
     GArray *cbs[PLUGIN_N_CB_SUBTYPES];
 };
 
include/qemu/qemu-plugin.h +0 -0
index 50a9957279..2397574a21 100644

include/qemu/qemu-plugin.h void qemu_plugin_register_vcpu_insn_exec_inline(struct qemu_plugin_insn *insn, · line 343

Quoted 8 lines
include/qemu/qemu-plugin.h +5 -0
@@ -336,6 +336,14 @@ void qemu_plugin_register_vcpu_insn_exec_inline(struct qemu_plugin_insn *insn,
  */
 size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb);
 
+/**
+ * qemu_plugin_tb_n_insns() - query helper for host insns size in TB
+ * @tb: opaque handle to TB passed to callback
+ *
+ * Returns: address of host insns size of this block

If we went ahead with this we need to be very clear when you can call this helper because the data will only be valid at certain points (which is another argument against this).

Quoted 34 lines
include/qemu/qemu-plugin.h +3 -0
+ */
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb);
+
 /**
  * qemu_plugin_tb_vaddr() - query helper for vaddr of TB start
  * @tb: opaque handle to TB passed to callback
plugins/api.c +5 -0
index 2078b16edb..0d70cb1f0f 100644
@@ -188,6 +188,11 @@ size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb)
     return tb->n;
 }
 
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb)
+{
+    return tb->host_insn_size;
+}
+
 uint64_t qemu_plugin_tb_vaddr(const struct qemu_plugin_tb *tb)
 {
     return tb->vaddr;
plugins/qemu-plugins.symbols +1 -0
index 71f6c90549..3e92c3b8ba 100644
@@ -39,6 +39,7 @@
   qemu_plugin_start_code;
   qemu_plugin_tb_get_insn;
   qemu_plugin_tb_n_insns;
+  qemu_plugin_tb_host_insn_size;
   qemu_plugin_tb_vaddr;
   qemu_plugin_uninstall;
   qemu_plugin_vcpu_for_each;
#5 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

In reply to Alex Bennée
Quoted 6 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.

Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

r~

#6 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Quoted 3 lines

r~

Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
#4 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

In reply to Wu, Fei
Quoted 20 lines · Fei
Quoted 14 lines · Alex Bennée
Quoted 5 lines · Fei Wu

The translation ratio of host to guest instruction count is one of the key performance factor of binary translation. TCG doesn't collect host instruction count at present, it does collect host instruction size instead, although they are not the same thing as instruction size might not be fixed, instruction size is still a valid estimation.

I'm not so sure about exposing this information to plugins because we try to avoid leaking internal implementation details to plugins. Aside from that the very act of instrumenting will increase the size of the target buffer.

Quoted 5 lines

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.

Quoted 8 lines

"info jit" collects the translation time expansion ratio, it doesn't distinguish between hot and cold blocks:
TB avg target size 14 max=1918 bytes
TB avg host size 287 bytes (expansion ratio: 19.7)

My primary aim is to collect the runtime expansion ratio, so hot blocks weigh more than cold blocks. My concern is this series might not be the proper way to implement it, just as you mentioned in another reply.

See my reply to Richard but:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

may be of interest?

Quoted 95 lines

Thanks,
Fei.

Quoted 91 lines

Richard, what do you think?

Quoted 40 lines
---
 accel/tcg/plugin-gen.c       | 1 +
 include/qemu/plugin.h        | 2 ++
 include/qemu/qemu-plugin.h   | 8 ++++++++
 plugins/api.c                | 5 +++++
 plugins/qemu-plugins.symbols | 1 +
 5 files changed, 17 insertions(+)
accel/tcg/plugin-gen.c +1 -0
index 5efb8db258..4a3ca8fa2f 100644
@@ -881,6 +881,7 @@ bool plugin_gen_tb_start(CPUState *cpu, const DisasContextBase *db,
         ptb->haddr2 = NULL;
         ptb->mem_only = mem_only;
         ptb->mem_helper = false;
+        ptb->host_insn_size = &db->tb->tc.size;
 
         plugin_gen_empty_callback(PLUGIN_GEN_FROM_TB);
     }
include/qemu/plugin.h +2 -0
index bc0781cab8..b38fd139e1 100644
@@ -151,6 +151,8 @@ struct qemu_plugin_tb {
     /* if set, the TB calls helpers that might access guest memory */
     bool mem_helper;
 
+    uint64_t *host_insn_size;
+
     GArray *cbs[PLUGIN_N_CB_SUBTYPES];
 };
 
include/qemu/qemu-plugin.h +0 -0
index 50a9957279..2397574a21 100644

include/qemu/qemu-plugin.h void qemu_plugin_register_vcpu_insn_exec_inline(struct qemu_plugin_insn *insn, · line 343

Quoted 8 lines
include/qemu/qemu-plugin.h +5 -0
@@ -336,6 +336,14 @@ void qemu_plugin_register_vcpu_insn_exec_inline(struct qemu_plugin_insn *insn,
  */
 size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb);
 
+/**
+ * qemu_plugin_tb_n_insns() - query helper for host insns size in TB
+ * @tb: opaque handle to TB passed to callback
+ *
+ * Returns: address of host insns size of this block

If we went ahead with this we need to be very clear when you can call this helper because the data will only be valid at certain points (which is another argument against this).

Quoted 34 lines
include/qemu/qemu-plugin.h +3 -0
+ */
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb);
+
 /**
  * qemu_plugin_tb_vaddr() - query helper for vaddr of TB start
  * @tb: opaque handle to TB passed to callback
plugins/api.c +5 -0
index 2078b16edb..0d70cb1f0f 100644
@@ -188,6 +188,11 @@ size_t qemu_plugin_tb_n_insns(const struct qemu_plugin_tb *tb)
     return tb->n;
 }
 
+void *qemu_plugin_tb_host_insn_size(const struct qemu_plugin_tb *tb)
+{
+    return tb->host_insn_size;
+}
+
 uint64_t qemu_plugin_tb_vaddr(const struct qemu_plugin_tb *tb)
 {
     return tb->vaddr;
plugins/qemu-plugins.symbols +1 -0
index 71f6c90549..3e92c3b8ba 100644
@@ -39,6 +39,7 @@
   qemu_plugin_start_code;
   qemu_plugin_tb_get_insn;
   qemu_plugin_tb_n_insns;
+  qemu_plugin_tb_host_insn_size;
   qemu_plugin_tb_vaddr;
   qemu_plugin_uninstall;
   qemu_plugin_vcpu_for_each;
Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
author
#7 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

In reply to Alex Bennée
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html

Thanks,
Fei.

Quoted 5 lines
Quoted 3 lines

r~

#8 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html

I have a v10 branch here:

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

Quoted 9 lines

Thanks,
Fei.

Quoted 5 lines
Quoted 3 lines

r~

Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
author
#9 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 47 lines · Alex Bennée
Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html
Quoted 8 lines

I have a v10 branch here:

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

I'd like to try it. Why has it not been merged upstream?

Thanks,
Fei.

Quoted 11 lines
Quoted 9 lines

Thanks,
Fei.

Quoted 5 lines
Quoted 3 lines

r~

#10 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 50 lines · Fei
Quoted 49 lines · Alex Bennée
Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html

I have a v10 branch here:

Quoted 7 lines
Quoted 6 lines

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

I'd like to try it. Why has it not been merged upstream?

Bits have been merged (the perf jit support) but the original GSoC student moved on and I ran out of time to work on it. It became yet another back burner series that awaits some spare hacking time.

Quoted 15 lines

Thanks,
Fei.

Quoted 11 lines
Quoted 9 lines

Thanks,
Fei.

Quoted 5 lines
Quoted 3 lines

r~

Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
author
#11 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 59 lines · Alex Bennée
Quoted 56 lines · Fei
Quoted 55 lines · Alex Bennée
Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html

I have a v10 branch here:

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

Quoted 6 lines
Quoted 1 line

I'd like to try it. Why has it not been merged upstream?

Bits have been merged (the perf jit support) but the original GSoC student moved on and I ran out of time to work on it. It became yet another back burner series that awaits some spare hacking time.

Got it, let's see if I can help.

Thanks,
Fei.

author
#12 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

In reply to Alex Bennée
Quoted 47 lines · Alex Bennée
Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html
Quoted 8 lines

I have a v10 branch here:

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

I have rebased the patches to upstream here:
https://github.com/atwufei/qemu/tree/tbstats

I try to keep the patches as possible as they are, but there are lots of changes since then, so changes are inevitable, e.g. CF_NOCACHE has been removed from upstream, I just removed its usage in the corresponding patch, which might not be preferred.

I did some basic tests and they worked (the output of info goes to qemu console, instead of telnet terminal), including:
* tb_stats start
* info tb-list
* info tb 10

Alex, would you please take a look?

Thanks,
Fei.

#13 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 56 lines · Fei
Quoted 47 lines · Alex Bennée
Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html
Quoted 8 lines

I have a v10 branch here:

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

Quoted 7 lines

I have rebased the patches to upstream here:
https://github.com/atwufei/qemu/tree/tbstats

I try to keep the patches as possible as they are, but there are lots of changes since then, so changes are inevitable, e.g. CF_NOCACHE has been removed from upstream, I just removed its usage in the corresponding patch, which might not be preferred.

Yeah that fine. CF_NOCACHE was removed to avoid special cases in the generation code - we simply don't link or store the TBs in the QHT anymore. As long as the guest isn't executing a lot of non-RAM code we won't run out of translation buffer too quickly.

Quoted 8 lines

I did some basic tests and they worked (the output of info goes to qemu console, instead of telnet terminal), including:
* tb_stats start
* info tb-list
* info tb 10

Alex, would you please take a look?

That looks pretty good, glad it wasn't too painful a re-base.

The next question is do you want to pick up the series and put through a review cycle or two to get merged? It would probably be worth checking the last posting thread to see if their are any outstanding review comments.

Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
author
#14 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 79 lines · Alex Bennée
Quoted 56 lines · Fei
Quoted 47 lines · Alex Bennée
Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html
Quoted 8 lines

I have a v10 branch here:

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

Quoted 7 lines

I have rebased the patches to upstream here:
https://github.com/atwufei/qemu/tree/tbstats

I try to keep the patches as possible as they are, but there are lots of changes since then, so changes are inevitable, e.g. CF_NOCACHE has been removed from upstream, I just removed its usage in the corresponding patch, which might not be preferred.

Yeah that fine. CF_NOCACHE was removed to avoid special cases in the generation code - we simply don't link or store the TBs in the QHT anymore. As long as the guest isn't executing a lot of non-RAM code we won't run out of translation buffer too quickly.

Quoted 7 lines

I did some basic tests and they worked (the output of info goes to qemu console, instead of telnet terminal), including:
* tb_stats start
* info tb-list
* info tb 10

Quoted 9 lines
Quoted 1 line

Alex, would you please take a look?

That looks pretty good, glad it wasn't too painful a re-base.

The next question is do you want to pick up the series and put through a review cycle or two to get merged? It would probably be worth checking the last posting thread to see if their are any outstanding review comments.

Yes, I can do it. I have something else in hand right now, so the review request may be sent out in a few days.

Thanks,
Fei.

author
#15 lore raw

Re: [PATCH 1/2] accel/tcg/plugin: export host insn size

Quoted 84 lines · Fei
Quoted 83 lines · Alex Bennée
Quoted 56 lines · Fei
Quoted 47 lines · Alex Bennée
Quoted 29 lines · Fei
Quoted 28 lines · Alex Bennée
Quoted 9 lines · Richard Henderson
Quoted 5 lines · Alex Bennée

If your aim is to examine JIT efficiency what is wrong with the current "info jit" that you can access via the HMP? Also I'm wondering if its time to remove the #ifdefs from CONFIG_PROFILER because I doubt the extra data it collects is that expensive.
Richard, what do you think?

What is it that you want from CONFIG_PROFILER that you can't get from perf? I've been tempted to remove CONFIG_PROFILER entirely.

I think perf is pretty good at getting the hot paths in the translator and pretty much all of the timer related stuff in CONFIG_PROFILER could be dropped. However some of the additional information about TCG ops usage and distribution is useful. That said last time I had a tilt at this on the back of a GSoC project:

Subject: [PATCH v9 00/13] TCG code quality tracking and perf integration
Date: Mon, 7 Oct 2019 16:28:26 +0100
Message-Id: <[email protected]>

The series ended up moving all the useful bits of CONFIG_PROFILER into tb stats which was dynamically controlled on a per TB basis. Now that the perf integration stuff was merged maybe there is a simpler series to be picked out of the remains?

Quoted 8 lines
Quoted 6 lines

Fei Wu,

Have you looked at the above series? Is that gathering the sort of things you need? Is this all in service of examining the translation quality of hot code?

Yes, it does have what I want, I suppose this wiki is for the series:
https://wiki.qemu.org/Features/TCGCodeQuality

Yes.

Quoted 3 lines

btw, the archive seems broken and cannot show the whole series:

    https://www.mail-archive.com/[email protected]/msg650258.html
Quoted 8 lines

I have a v10 branch here:

https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10

I think the top two patches can be dropped on a re-base as the JIT/perf integration is already merged. It might be a tricky re-base though. Depends on how much churn there has been in the tree since.

Quoted 7 lines

I have rebased the patches to upstream here:
https://github.com/atwufei/qemu/tree/tbstats

I try to keep the patches as possible as they are, but there are lots of changes since then, so changes are inevitable, e.g. CF_NOCACHE has been removed from upstream, I just removed its usage in the corresponding patch, which might not be preferred.

Yeah that fine. CF_NOCACHE was removed to avoid special cases in the generation code - we simply don't link or store the TBs in the QHT anymore. As long as the guest isn't executing a lot of non-RAM code we won't run out of translation buffer too quickly.

Quoted 8 lines

I did some basic tests and they worked (the output of info goes to qemu console, instead of telnet terminal), including:
* tb_stats start
* info tb-list
* info tb 10

Alex, would you please take a look?

That looks pretty good, glad it wasn't too painful a re-base.

Quoted 8 lines
Quoted 5 lines

The next question is do you want to pick up the series and put through a review cycle or two to get merged? It would probably be worth checking the last posting thread to see if their are any outstanding review comments.

Yes, I can do it. I have something else in hand right now, so the review request may be sent out in a few days.

I have sent the review out here, hope you have received it:
https://www.mail-archive.com/[email protected]/msg955889.html

I just received the cover letter w/o the following patches, I do subscribe to [email protected], not sure why.

Thanks,
Fei.

Quoted 2 lines

Thanks,
Fei.