From: Roman Bolshakov <r.bolshakov@yadro.com>
To: "Zhang, Chen" <chen.zhang@intel.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Li Zhijian" <lizhijian@cn.fujitsu.com>,
"Jason Wang" <jasowang@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Cameron Esfahani" <dirty@apple.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2 4/4] net/colo: Match is-enabled probe to tracepoint
Date: Mon, 20 Jul 2020 13:59:06 +0300 [thread overview]
Message-ID: <20200720105906.GB73320@SPB-NB-133.local> (raw)
In-Reply-To: <3f6bcf74d3c348f9b7744305a6343a79@intel.com>
On Sat, Jul 18, 2020 at 05:58:56PM +0000, Zhang, Chen wrote:
> > -----Original Message-----
> > From: Roman Bolshakov <r.bolshakov@yadro.com>
> > Sent: Friday, July 17, 2020 5:35 PM
> > @@ -533,12 +535,12 @@ static int colo_packet_compare_udp(Packet *spkt,
> > Packet *ppkt)
> > ppkt->size - offset)) {
> > trace_colo_compare_udp_miscompare("primary pkt size", ppkt->size);
> > trace_colo_compare_udp_miscompare("Secondary pkt size", spkt-
> > >size);
> > - if
> > (trace_event_get_state_backends(TRACE_COLO_COMPARE_MISCOMPARE))
> > {
> > - qemu_hexdump((char *)ppkt->data, stderr, "colo-compare pri pkt",
> > - ppkt->size);
> > - qemu_hexdump((char *)spkt->data, stderr, "colo-compare sec pkt",
> > - spkt->size);
> > - }
> > +#ifdef DEBUG_COLO_PACKETS
> > + qemu_hexdump((char *)ppkt->data, stderr, "colo-compare pri pkt",
> > + ppkt->size);
> > + qemu_hexdump((char *)spkt->data, stderr, "colo-compare sec pkt",
> > + spkt->size);
> > +#endif
>
> I think change the " trace_event_get_state_backends()" to "trace_colo_compare_main("Dump packet hex: ")" is a better choice here.
> It will keep the original code logic and avoid the problem here.
>
Hi Chen,
Do you mean to use another is-enabled probe?
e.g. change from
"if (trace_event_get_state_backends(TRACE_COLO_COMPARE_MISCOMPARE))"
to
"if (trace_event_get_state_backends(TRACE_COLO_COMPARE_MAIN))"
Thanks,
Roman
next prev parent reply other threads:[~2020-07-20 11:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:35 [PATCH v2 0/4] Add dtrace support on macOS Roman Bolshakov
2020-07-17 9:35 ` [PATCH v2 1/4] scripts/tracetool: Fix dtrace generation for macOS Roman Bolshakov
2020-07-19 13:52 ` Philippe Mathieu-Daudé
2020-07-20 10:50 ` Roman Bolshakov
2020-07-20 10:53 ` Philippe Mathieu-Daudé
2020-07-21 12:33 ` Stefan Hajnoczi
2020-07-17 9:35 ` [PATCH v2 2/4] scripts/tracetool: Use void pointer for vcpu Roman Bolshakov
2020-07-21 12:34 ` Stefan Hajnoczi
2020-07-17 9:35 ` [PATCH v2 3/4] build: Don't make object files for dtrace on macOS Roman Bolshakov
2020-07-21 12:34 ` Stefan Hajnoczi
2020-07-24 17:00 ` Roman Bolshakov
2020-07-17 9:35 ` [PATCH v2 4/4] net/colo: Match is-enabled probe to tracepoint Roman Bolshakov
2020-07-18 17:58 ` Zhang, Chen
2020-07-20 10:59 ` Roman Bolshakov [this message]
2020-07-21 14:06 ` Daniel P. Berrangé
2020-07-29 12:33 ` Roman Bolshakov
2020-07-29 12:34 ` Daniel P. Berrangé
2020-08-05 10:53 ` Stefan Hajnoczi
2020-08-05 18:01 ` Zhang, Chen
2020-07-21 12:36 ` [PATCH v2 0/4] Add dtrace support on macOS Stefan Hajnoczi
2020-08-07 13:00 ` Stefan Hajnoczi
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=20200720105906.GB73320@SPB-NB-133.local \
--to=r.bolshakov@yadro.com \
--cc=berrange@redhat.com \
--cc=chen.zhang@intel.com \
--cc=dirty@apple.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=philmd@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).