From: Pedro Alves <palves@redhat.com>
To: Wei-cheng Wang <cole945@gmail.com>,
uweigand@de.ibm.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/5 v4] Fix argument to compiled_cond, and add cases for compiled-condition.
Date: Tue, 30 Jun 2015 09:57:00 -0000 [thread overview]
Message-ID: <55926811.6020505@redhat.com> (raw)
In-Reply-To: <1435422102-39438-3-git-send-email-cole945@gmail.com>
On 06/27/2015 05:21 PM, Wei-cheng Wang wrote:
> Hi,
>
> Ulrich Weigand wrote:
>> > Ah, when I said to add new test cases in a separate patch, what I meant was:
>> > - use a separate patch (applied *first*) that adds the *new tests* (to be
>> > run on existing platforms), i.e. test_ftrace_condition
>> > - as part of the patch that actually adds powerpc support, add all the small
>> > test case snippets that specifically enable the test cases for powerpc
>> > This is again so that each set in a series is meaningful in itself (and
>> > does not introduce testsuite regressions when applied alone).
> ...
>> > Wei-cheng Wang wrote:
>>> > >if (tpoint->compiled_cond)
>>> > > err = ((condfn) (uintptr_t) (tpoint->compiled_cond)) (ctx, &value);
>>> > >
>>> > >I think probably either we could pass ctx->regs to compiled_cond instead,
>>> > >or move the declarations of fast_tracepoint_ctx (and others) to tracepoint.h,
>>> > >so we can use "offsetof (fast_tracepoint_ctx, regs)" instead.
>>> > >Any suggestion?
>> > FWIW, passing the regs buffer directly to the compiled routine seems
>> > more straightforward to me ...
> Some of the new cases are used to testing emit-reg, and emit-reg for x86
> doesn't work due to the incorrect argument to compiled_cond - "regs" buffer
> is expected, but tracepoint context is passed
>
> This case also includes the fix for complied_cond in order for x86 to
> pass testing for emit-reg op.
>
> Testing result on my x86_64 Ubuntu 14.04.2 TLS
>
> before w/ new cases only w/ the fix
> PASS 2625 2759 2765
> FAIL 33 39 33
> XFAIL 16 16 16
> KFAIL 2 2 2
> UNTESTED 1 1 1
> UNSUPPORTED 3 3 3
>
> Thanks,
> Wei-cheng
>
> ---
>
> * Fix generating emit-reg op by passing register buffer to compiled_cond.
> * Add a new function for testing compiled-cond by checking whether
> based on a given CONDEXP, a list of expected values should be collected.
>
> ---
FWIW, looks good to me too. Thanks for the new tests!
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-06-30 9:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 16:21 [PATCH 1/5 v4] Remove tracepoint_action ops Wei-cheng Wang
2015-06-27 16:22 ` [PATCH 4/5 v4] Tracepoint for ppc64 Wei-cheng Wang
2015-06-28 6:21 ` Wei-cheng Wang
2015-06-29 15:54 ` Pierre Langlois
2015-07-03 16:37 ` Ulrich Weigand
2015-06-27 16:22 ` [PATCH 2/5 v4] powerpc: Support z-point type in gdbserver Wei-cheng Wang
2015-07-03 15:17 ` Ulrich Weigand
2016-02-24 12:05 ` Marcin Kościelnicki
2016-02-24 17:37 ` Ulrich Weigand
2016-02-24 17:39 ` Marcin Kościelnicki
2015-06-27 16:22 ` [PATCH 5/5 v4] Allow target to decide where to map jump-pad Wei-cheng Wang
2015-07-03 16:38 ` Ulrich Weigand
2015-06-27 16:22 ` [PATCH 3/5 v4] Fix argument to compiled_cond, and add cases for compiled-condition Wei-cheng Wang
2015-06-30 9:57 ` Pedro Alves [this message]
2015-09-14 14:04 ` Pierre Langlois
2015-09-16 16:15 ` Yao Qi
2015-06-30 9:57 ` [PATCH 1/5 v4] Remove tracepoint_action ops Pedro Alves
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=55926811.6020505@redhat.com \
--to=palves@redhat.com \
--cc=cole945@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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