diff mbox series

[v7,05/27] tcg: add options for enabling MTTCG

Message ID 20170119170507.16185-6-alex.bennee@linaro.org
State Superseded
Headers show
Series Remaining MTTCG Base patches and ARM enablement | expand

Commit Message

Alex Bennée Jan. 19, 2017, 5:04 p.m. UTC
From: KONRAD Frederic <fred.konrad@greensocs.com>


We know there will be cases where MTTCG won't work until additional work
is done in the front/back ends to support. It will however be useful to
be able to turn it on.

As a result MTTCG will default to off unless the combination is
supported. However the user can turn it on for the sake of testing.

Signed-off-by: KONRAD Frederic <fred.konrad@greensocs.com>

[AJB: move to -accel tcg,thread=multi|single, defaults]
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>

Reviewed-by: Richard Henderson <rth@twiddle.net>

---
v1:
  - merge with add mttcg option.
  - update commit message
v2:
  - machine_init->opts_init
v3:
  - moved from -tcg to -accel tcg,thread=single|multi
  - fix checkpatch warnings
v4:
  - make mttcg_enabled extern, qemu_tcg_mttcg_enabled() now just macro
  - qemu_tcg_configure now propagates Error instead of exiting
  - better error checking of thread=foo
  - use CONFIG flags for default_mttcg_enabled()
  - disable mttcg with icount, error if both forced on
v7
  - explicitly disable MTTCG for TCG_OVERSIZED_GUEST
  - use check_tcg_memory_orders_compatible() instead of CONFIG_MTTCG_HOST
  - change CONFIG_MTTCG_TARGET to TARGET_SUPPORTS_MTTCG
---
 cpus.c                | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++
 include/qom/cpu.h     |  9 +++++++
 include/sysemu/cpus.h |  2 ++
 qemu-options.hx       | 20 +++++++++++++++
 tcg/tcg.h             |  9 +++++++
 vl.c                  | 49 +++++++++++++++++++++++++++++++++++-
 6 files changed, 158 insertions(+), 1 deletion(-)

-- 
2.11.0

Comments

Pranith Kumar Jan. 20, 2017, 1:28 a.m. UTC | #1
Alex Bennée writes:

> From: KONRAD Frederic <fred.konrad@greensocs.com>

>

> We know there will be cases where MTTCG won't work until additional work

> is done in the front/back ends to support. It will however be useful to

> be able to turn it on.

>

> As a result MTTCG will default to off unless the combination is

> supported. However the user can turn it on for the sake of testing.

>


<snip>

>  static TimersState timers_state;

> +bool mttcg_enabled;

> +

> +/*

> + * We default to false if we know other options have been enabled

> + * which are currently incompatible with MTTCG. Otherwise when each

> + * guest (target) has been updated to support:

> + *   - atomic instructions

> + *   - memory ordering primitives (barriers)

> + * they can set the appropriate CONFIG flags in ${target}-softmmu.mak

> + *

> + * Once a guest architecture has been converted to the new primitives

> + * there are two remaining limitations to check.

> + *

> + * - The guest can't be oversized (e.g. 64 bit guest on 32 bit host)

> + * - The host must have a stronger memory order than the guest

> + *

> + * It may be possible in future to support strong guests on weak hosts

> + * but that will require tagging all load/stores in a guest with their

> + * implicit memory order requirements which would likely slow things

> + * down a lot.

> + */

> +

> +static bool check_tcg_memory_orders_compatible(void)

> +{

> +#if defined(TCG_DEFAULT_MO) && defined(TCG_TARGET_DEFAULT_MO)

> +    return (TCG_DEFAULT_MO & ~TCG_TARGET_DEFAULT_MO) == 0;


I am not sure this is what we intended. If the guest is weaker than the host,
we can still run the guest if we translate the guest barriers. With the above,
a strong host cannot run a weaker host.

I think what we want is to disallow weak hosts from running stronger guests,
since we do not enforce the implicit ordering semantics of the guest as of
now.  In that case you can filter them out using the following:

TCG_DEFAULT_MO | (TCG_DEFAULT_MO ^ ~TCG_TARGET_DEFAULT_MO) == TCG_MO_ALL

We want our guest execution to prevent all possible re-ordering. The first
term above is the host memory order. If the host is SC, we do not need to
check anything else. If not, the second term tells us the difference in
ordering between the guest and the host. It gives the kind of barriers
which will be translated from guest to host. Both these together should cover
all the cases for the memory order to be compatible.

Thoughts?

Thanks,
--
Pranith
Alex Bennée Jan. 20, 2017, 2:50 p.m. UTC | #2
Pranith Kumar <bobby.prani@gmail.com> writes:

> Alex Bennée writes:

>

>> From: KONRAD Frederic <fred.konrad@greensocs.com>

>>

>> We know there will be cases where MTTCG won't work until additional work

>> is done in the front/back ends to support. It will however be useful to

>> be able to turn it on.

>>

>> As a result MTTCG will default to off unless the combination is

>> supported. However the user can turn it on for the sake of testing.

>>

>

> <snip>

>

>>  static TimersState timers_state;

>> +bool mttcg_enabled;

>> +

>> +/*

>> + * We default to false if we know other options have been enabled

>> + * which are currently incompatible with MTTCG. Otherwise when each

>> + * guest (target) has been updated to support:

>> + *   - atomic instructions

>> + *   - memory ordering primitives (barriers)

>> + * they can set the appropriate CONFIG flags in ${target}-softmmu.mak

>> + *

>> + * Once a guest architecture has been converted to the new primitives

>> + * there are two remaining limitations to check.

>> + *

>> + * - The guest can't be oversized (e.g. 64 bit guest on 32 bit host)

>> + * - The host must have a stronger memory order than the guest

>> + *

>> + * It may be possible in future to support strong guests on weak hosts

>> + * but that will require tagging all load/stores in a guest with their

>> + * implicit memory order requirements which would likely slow things

>> + * down a lot.

>> + */

>> +

>> +static bool check_tcg_memory_orders_compatible(void)

>> +{

>> +#if defined(TCG_DEFAULT_MO) && defined(TCG_TARGET_DEFAULT_MO)

>> +    return (TCG_DEFAULT_MO & ~TCG_TARGET_DEFAULT_MO) == 0;

>

> I am not sure this is what we intended. If the guest is weaker than the host,

> we can still run the guest if we translate the guest barriers. With the above,

> a strong host cannot run a weaker host.


I think this is confusing because of QEMU's overload of the term target.
TCG_TARGET_DEFAULT_MO is the memory order of the host. So if there is
any expected memory order on the guest side (TCG_DEFAULT_MO) that isn't
met by the host then we fail. In ARMs case TCG_DEFAULT_MO is 0 so it
will always pass.

> I think what we want is to disallow weak hosts from running stronger guests,

> since we do not enforce the implicit ordering semantics of the guest as of

> now.  In that case you can filter them out using the following:

>

> TCG_DEFAULT_MO | (TCG_DEFAULT_MO ^ ~TCG_TARGET_DEFAULT_MO) == TCG_MO_ALL

>

> We want our guest execution to prevent all possible re-ordering. The first

> term above is the host memory order. If the host is SC, we do not need to

> check anything else. If not, the second term tells us the difference in

> ordering between the guest and the host. It gives the kind of barriers

> which will be translated from guest to host. Both these together should cover

> all the cases for the memory order to be compatible.

>

> Thoughts?


That's the wrong way round. TCG_DEFAULT_MO is the guest memory order.
Maybe I should rename them to be explicitly:

TCG_GUEST_DEFAULT_MO
TCG_HOST_DEFAULT_MO

But that introduces another terminology into the TCG code.

>

> Thanks,



--
Alex Bennée
Pranith Kumar Jan. 20, 2017, 3:03 p.m. UTC | #3
On Fri, Jan 20, 2017 at 9:50 AM, Alex Bennée <alex.bennee@linaro.org> wrote:
>

> That's the wrong way round. TCG_DEFAULT_MO is the guest memory order.

> Maybe I should rename them to be explicitly:

>

> TCG_GUEST_DEFAULT_MO

> TCG_HOST_DEFAULT_MO

>

> But that introduces another terminology into the TCG code.

>


Ah, that's not the first time I got confused. May be just add a comment?


-- 
Pranith
Richard Henderson Jan. 23, 2017, 7:06 p.m. UTC | #4
On 01/19/2017 09:04 AM, Alex Bennée wrote:
> +void qemu_tcg_configure(QemuOpts *opts, Error **errp)

> +{

> +    const char *t = qemu_opt_get(opts, "thread");

> +    if (t) {

> +        if (strcmp(t, "multi") == 0) {

> +            if (TCG_OVERSIZED_GUEST) {

> +                error_setg(errp, "No MTTCG when guest word size > hosts");


I agree with this, since I don't ever imagine it'll be fixed.  It's a silly use
case in the first place considering the ubiquity of 64-bit hosts.

> +            } else if (!check_tcg_memory_orders_compatible()) {

> +                error_setg(errp,

> +                           "No MTTCG when guest MO is stronger than host MO");


This, on the other hand, means that one cannot even force multi for testing.  A
warning perhaps?  And how shall we handle a guest translate adding barriers as
necessary to satisfy host memory ordering?


r~
Alex Bennée Jan. 24, 2017, 8:25 p.m. UTC | #5
Richard Henderson <rth@twiddle.net> writes:

> On 01/19/2017 09:04 AM, Alex Bennée wrote:

>> +void qemu_tcg_configure(QemuOpts *opts, Error **errp)

>> +{

>> +    const char *t = qemu_opt_get(opts, "thread");

>> +    if (t) {

>> +        if (strcmp(t, "multi") == 0) {

>> +            if (TCG_OVERSIZED_GUEST) {

>> +                error_setg(errp, "No MTTCG when guest word size > hosts");

>

> I agree with this, since I don't ever imagine it'll be fixed.  It's a silly use

> case in the first place considering the ubiquity of 64-bit hosts.


Funnily enough I know one kernel hacker who does use this to test their
arm64 kernels on their re-purposed armhf chromebooks. I've already
explained coming their way ;-)

>

>> +            } else if (!check_tcg_memory_orders_compatible()) {

>> +                error_setg(errp,

>> +                           "No MTTCG when guest MO is stronger than host MO");

>

> This, on the other hand, means that one cannot even force multi for testing.  A

> warning perhaps?


I did toy with making that a warning when I first wrote it. I'll make it so.

> And how shall we handle a guest translate adding barriers as

> necessary to satisfy host memory ordering?


We are talking about doing the necessary annotation to all a givens
targets loads and stores? I figured this code would morph and be tweaked
when (if?) we get there.

--
Alex Bennée
Richard Henderson Jan. 24, 2017, 8:48 p.m. UTC | #6
On 01/24/2017 12:25 PM, Alex Bennée wrote:
> We are talking about doing the necessary annotation to all a givens

> targets loads and stores? I figured this code would morph and be tweaked

> when (if?) we get there.


Fair enough.


r~
diff mbox series

Patch

diff --git a/cpus.c b/cpus.c
index 5213351c6d..eaefaebffc 100644
--- a/cpus.c
+++ b/cpus.c
@@ -25,6 +25,7 @@ 
 /* Needed early for CONFIG_BSD etc. */
 #include "qemu/osdep.h"
 #include "qemu-common.h"
+#include "qemu/config-file.h"
 #include "cpu.h"
 #include "monitor/monitor.h"
 #include "qapi/qmp/qerror.h"
@@ -148,6 +149,75 @@  typedef struct TimersState {
 } TimersState;
 
 static TimersState timers_state;
+bool mttcg_enabled;
+
+/*
+ * We default to false if we know other options have been enabled
+ * which are currently incompatible with MTTCG. Otherwise when each
+ * guest (target) has been updated to support:
+ *   - atomic instructions
+ *   - memory ordering primitives (barriers)
+ * they can set the appropriate CONFIG flags in ${target}-softmmu.mak
+ *
+ * Once a guest architecture has been converted to the new primitives
+ * there are two remaining limitations to check.
+ *
+ * - The guest can't be oversized (e.g. 64 bit guest on 32 bit host)
+ * - The host must have a stronger memory order than the guest
+ *
+ * It may be possible in future to support strong guests on weak hosts
+ * but that will require tagging all load/stores in a guest with their
+ * implicit memory order requirements which would likely slow things
+ * down a lot.
+ */
+
+static bool check_tcg_memory_orders_compatible(void)
+{
+#if defined(TCG_DEFAULT_MO) && defined(TCG_TARGET_DEFAULT_MO)
+    return (TCG_DEFAULT_MO & ~TCG_TARGET_DEFAULT_MO) == 0;
+#else
+    return false;
+#endif
+}
+
+static bool default_mttcg_enabled(void)
+{
+    QemuOpts *icount_opts = qemu_find_opts_singleton("icount");
+    const char *rr = qemu_opt_get(icount_opts, "rr");
+
+    if (rr || TCG_OVERSIZED_GUEST) {
+        return false;
+    } else {
+#ifdef TARGET_SUPPORTS_MTTCG
+        return check_tcg_memory_orders_compatible();
+#else
+        return false;
+#endif
+    }
+}
+
+void qemu_tcg_configure(QemuOpts *opts, Error **errp)
+{
+    const char *t = qemu_opt_get(opts, "thread");
+    if (t) {
+        if (strcmp(t, "multi") == 0) {
+            if (TCG_OVERSIZED_GUEST) {
+                error_setg(errp, "No MTTCG when guest word size > hosts");
+            } else if (!check_tcg_memory_orders_compatible()) {
+                error_setg(errp,
+                           "No MTTCG when guest MO is stronger than host MO");
+            } else {
+                mttcg_enabled = true;
+            }
+        } else if (strcmp(t, "single") == 0) {
+            mttcg_enabled = false;
+        } else {
+            error_setg(errp, "Invalid 'thread' setting %s", t);
+        }
+    } else {
+        mttcg_enabled = default_mttcg_enabled();
+    }
+}
 
 int64_t cpu_get_icount_raw(void)
 {
diff --git a/include/qom/cpu.h b/include/qom/cpu.h
index 3f79a8e955..541785aeda 100644
--- a/include/qom/cpu.h
+++ b/include/qom/cpu.h
@@ -407,6 +407,15 @@  extern struct CPUTailQ cpus;
 extern __thread CPUState *current_cpu;
 
 /**
+ * qemu_tcg_mttcg_enabled:
+ * Check whether we are running MultiThread TCG or not.
+ *
+ * Returns: %true if we are in MTTCG mode %false otherwise.
+ */
+extern bool mttcg_enabled;
+#define qemu_tcg_mttcg_enabled() (mttcg_enabled)
+
+/**
  * cpu_paging_enabled:
  * @cpu: The CPU whose state is to be inspected.
  *
diff --git a/include/sysemu/cpus.h b/include/sysemu/cpus.h
index 3728a1ea7e..a73b5d4bce 100644
--- a/include/sysemu/cpus.h
+++ b/include/sysemu/cpus.h
@@ -36,4 +36,6 @@  extern int smp_threads;
 
 void list_cpus(FILE *f, fprintf_function cpu_fprintf, const char *optarg);
 
+void qemu_tcg_configure(QemuOpts *opts, Error **errp);
+
 #endif
diff --git a/qemu-options.hx b/qemu-options.hx
index c534a2f7f9..e61c26a9d2 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -96,6 +96,26 @@  STEXI
 Select CPU model (@code{-cpu help} for list and additional feature selection)
 ETEXI
 
+DEF("accel", HAS_ARG, QEMU_OPTION_accel,
+    "-accel [accel=]accelerator[,thread=single|multi]\n"
+    "               select accelerator ('-accel help for list')\n"
+    "               thread=single|multi (enable multi-threaded TCG)", QEMU_ARCH_ALL)
+STEXI
+@item -accel @var{name}[,prop=@var{value}[,...]]
+@findex -accel
+This is used to enable an accelerator. Depending on the target architecture,
+kvm, xen, or tcg can be available. By default, tcg is used. If there is more
+than one accelerator specified, the next one is used if the previous one fails
+to initialize.
+@table @option
+@item thread=single|multi
+Controls number of TCG threads. When the TCG is multi-threaded there will be one
+thread per vCPU therefor taking advantage of additional host cores. The default
+is to enable multi-threading where both the back-end and front-ends support it and
+no incompatible TCG features have been enabled (e.g. icount/replay).
+@end table
+ETEXI
+
 DEF("smp", HAS_ARG, QEMU_OPTION_smp,
     "-smp [cpus=]n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]\n"
     "                set the number of CPUs to 'n' [default=1]\n"
diff --git a/tcg/tcg.h b/tcg/tcg.h
index f946452049..4c7f258220 100644
--- a/tcg/tcg.h
+++ b/tcg/tcg.h
@@ -80,6 +80,15 @@  typedef uint64_t tcg_target_ulong;
 #error unsupported
 #endif
 
+/* Oversized TCG guests make things like MTTCG hard
+ * as we can't use atomics for cputlb updates.
+ */
+#if TARGET_LONG_BITS > TCG_TARGET_REG_BITS
+#define TCG_OVERSIZED_GUEST 1
+#else
+#define TCG_OVERSIZED_GUEST 0
+#endif
+
 #if TCG_TARGET_NB_REGS <= 32
 typedef uint32_t TCGRegSet;
 #elif TCG_TARGET_NB_REGS <= 64
diff --git a/vl.c b/vl.c
index c643d3ff3a..d6a9e119a7 100644
--- a/vl.c
+++ b/vl.c
@@ -296,6 +296,26 @@  static QemuOptsList qemu_machine_opts = {
     },
 };
 
+static QemuOptsList qemu_accel_opts = {
+    .name = "accel",
+    .implied_opt_name = "accel",
+    .head = QTAILQ_HEAD_INITIALIZER(qemu_accel_opts.head),
+    .merge_lists = true,
+    .desc = {
+        {
+            .name = "accel",
+            .type = QEMU_OPT_STRING,
+            .help = "Select the type of accelerator",
+        },
+        {
+            .name = "thread",
+            .type = QEMU_OPT_STRING,
+            .help = "Enable/disable multi-threaded TCG",
+        },
+        { /* end of list */ }
+    },
+};
+
 static QemuOptsList qemu_boot_opts = {
     .name = "boot-opts",
     .implied_opt_name = "order",
@@ -3000,7 +3020,8 @@  int main(int argc, char **argv, char **envp)
     const char *boot_once = NULL;
     DisplayState *ds;
     int cyls, heads, secs, translation;
-    QemuOpts *hda_opts = NULL, *opts, *machine_opts, *icount_opts = NULL;
+    QemuOpts *opts, *machine_opts;
+    QemuOpts *hda_opts = NULL, *icount_opts = NULL, *accel_opts = NULL;
     QemuOptsList *olist;
     int optind;
     const char *optarg;
@@ -3055,6 +3076,7 @@  int main(int argc, char **argv, char **envp)
     qemu_add_opts(&qemu_trace_opts);
     qemu_add_opts(&qemu_option_rom_opts);
     qemu_add_opts(&qemu_machine_opts);
+    qemu_add_opts(&qemu_accel_opts);
     qemu_add_opts(&qemu_mem_opts);
     qemu_add_opts(&qemu_smp_opts);
     qemu_add_opts(&qemu_boot_opts);
@@ -3748,6 +3770,26 @@  int main(int argc, char **argv, char **envp)
                 qdev_prop_register_global(&kvm_pit_lost_tick_policy);
                 break;
             }
+            case QEMU_OPTION_accel:
+                accel_opts = qemu_opts_parse_noisily(qemu_find_opts("accel"),
+                                                     optarg, true);
+                optarg = qemu_opt_get(accel_opts, "accel");
+
+                olist = qemu_find_opts("machine");
+                if (strcmp("kvm", optarg) == 0) {
+                    qemu_opts_parse_noisily(olist, "accel=kvm", false);
+                } else if (strcmp("xen", optarg) == 0) {
+                    qemu_opts_parse_noisily(olist, "accel=xen", false);
+                } else if (strcmp("tcg", optarg) == 0) {
+                    qemu_opts_parse_noisily(olist, "accel=tcg", false);
+                } else {
+                    if (!is_help_option(optarg)) {
+                        error_printf("Unknown accelerator: %s", optarg);
+                    }
+                    error_printf("Supported accelerators: kvm, xen, tcg\n");
+                    exit(1);
+                }
+                break;
             case QEMU_OPTION_usb:
                 olist = qemu_find_opts("machine");
                 qemu_opts_parse_noisily(olist, "usb=on", false);
@@ -4053,6 +4095,8 @@  int main(int argc, char **argv, char **envp)
 
     replay_configure(icount_opts);
 
+    qemu_tcg_configure(accel_opts, &error_fatal);
+
     machine_class = select_machine();
 
     set_memory_options(&ram_slots, &maxram_size, machine_class);
@@ -4417,6 +4461,9 @@  int main(int argc, char **argv, char **envp)
         if (kvm_enabled() || xen_enabled()) {
             error_report("-icount is not allowed with kvm or xen");
             exit(1);
+        } else if (qemu_tcg_mttcg_enabled()) {
+            error_report("-icount does not currently work with MTTCG");
+            exit(1);
         }
         configure_icount(icount_opts, &error_abort);
         qemu_opts_del(icount_opts);