From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/8] rcu: add rcutorture
Date: Fri, 16 Jan 2015 12:22:29 +0100 [thread overview]
Message-ID: <54B8F475.8070007@redhat.com> (raw)
In-Reply-To: <20150116020439.GD3079@ad.nay.redhat.com>
On 16/01/2015 03:04, Fam Zheng wrote:
> On Tue, 01/13 18:52, Paolo Bonzini wrote:
>> +int main(int argc, char *argv[])
>> +{
>> + int nreaders = 1;
>> + int duration = 1;
>> +
>> + if (argc >= 2 && argv[1][0] == '-') {
>> + g_test_init(&argc, &argv, NULL);
>> + g_test_add_func("/rcu/torture/short/1reader", gtest_stress_1_1);
>> + g_test_add_func("/rcu/torture/short/10readers", gtest_stress_10_1);
>> + g_test_add_func("/rcu/torture/long/1reader", gtest_stress_1_5);
>> + g_test_add_func("/rcu/torture/long/10readers", gtest_stress_10_5);
>
> Why do we need short tests when we have long tests? What are different other
> than the durations?
Nothing really. I guess long tests could be made optional (-m slow).
>> + return g_test_run();
>> + }
>> +
>> + if (argc >= 2) {
>> + nreaders = strtoul(argv[1], NULL, 0);
>> + }
>> + if (argc > 3) {
>> + duration = strtoul(argv[3], NULL, 0);
>> + }
>> + if (argc < 3 || strcmp(argv[2], "stress") == 0) {
>> + stresstest(nreaders, duration);
>> + } else if (strcmp(argv[2], "rperf") == 0) {
>> + rperftest(nreaders, duration);
>> + } else if (strcmp(argv[2], "uperf") == 0) {
>> + uperftest(nreaders, duration);
>> + } else if (strcmp(argv[2], "perf") == 0) {
>> + perftest(nreaders, duration);
>> + }
>> + usage(argc, argv);
>> + return 0;
>> +}
>> diff --git a/util/rcu.c b/util/rcu.c
>> index f8f52ae..8df16d9 100644
>> --- a/util/rcu.c
>> +++ b/util/rcu.c
>> @@ -169,5 +169,4 @@ static void __attribute__((__constructor__)) rcu_init(void)
>> {
>> qemu_mutex_init(&rcu_gp_lock);
>> qemu_event_init(&rcu_gp_event, true);
>> - rcu_register_thread();
>
> Maybe don't add this line in patch 2?
More like don't remove it in patch 3. ;)
Paolo
next prev parent reply other threads:[~2015-01-16 11:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 17:52 [Qemu-devel] [PATCH 0/8] RCUification of the memory API, part 1 Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 1/8] tls: require compiler support for __thread Paolo Bonzini
2015-01-13 18:40 ` Peter Maydell
2015-01-13 19:48 ` Paolo Bonzini
2015-01-13 20:00 ` Peter Maydell
2015-01-13 20:27 ` Paolo Bonzini
2015-01-13 22:07 ` Peter Maydell
2015-04-28 21:04 ` Emilio G. Cota
2015-04-29 11:09 ` Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 2/8] rcu: add rcu library Paolo Bonzini
2015-01-15 10:39 ` Fam Zheng
2015-01-15 11:08 ` Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 3/8] rcu: add rcutorture Paolo Bonzini
2015-01-16 2:04 ` Fam Zheng
2015-01-16 11:22 ` Paolo Bonzini [this message]
2015-01-13 17:52 ` [Qemu-devel] [PATCH 4/8] rcu: allow nesting of rcu_read_lock/rcu_read_unlock Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 5/8] rcu: add call_rcu Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 6/8] memory: remove assertion on memory_region_destroy Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 7/8] memory: protect current_map by RCU Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 8/8] memory: avoid ref/unref in memory_region_find Paolo Bonzini
2015-01-16 13:04 ` [Qemu-devel] [PATCH 0/8] RCUification of the memory API, part 1 Christian Borntraeger
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=54B8F475.8070007@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).