qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Roman Bolshakov <r.bolshakov@yadro.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: zhangchen.fnst@cn.fujitsu.com,
	"Li Zhijian" <lizhijian@cn.fujitsu.com>,
	"Jason Wang" <jasowang@redhat.com>,
	qemu-devel@nongnu.org, "Zhang Chen" <chen.zhang@intel.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH-for-5.1] net/colo: Remove unused trace event
Date: Wed, 15 Jul 2020 22:27:21 +0300	[thread overview]
Message-ID: <20200715192721.GD90799@SPB-NB-133.local> (raw)
In-Reply-To: <20200715151302.GE88416@redhat.com>

On Wed, Jul 15, 2020 at 04:13:02PM +0100, Daniel P. Berrangé wrote:
> On Wed, Jul 15, 2020 at 04:31:30PM +0200, Philippe Mathieu-Daudé wrote:
> > Unused trace event cause build failure when using the dtrace backend:
> > 
> >   "probe colo_compare_miscompare doesn't exist"
> > 
> > Fixes: f4b618360e ("colo-compare: add TCP, UDP, ICMP packet comparison")
> > Reported-by: Roman Bolshakov <r.bolshakov@yadro.com>
> 
> Note Roman indicated on IRC that this is seen with dtrace on macOS and
> there were other problems too.
> 
> Unless someone knows that QEMU's dtrace support worked on macOS in the
> past, I think we don't need  and simply consider dtrace unsupported on
> macOS right now until someone can get it into more robust shape on
> macOS.
> 

Hi Daniel,

I've got it working and I can see qemu trace points from
  sudo dtrace -m qemu-system-x86_64 -l

I'm wrapping a series that resolves all the issues along the way.

Thanks,
Roman


  reply	other threads:[~2020-07-15 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 14:31 [PATCH-for-5.1] net/colo: Remove unused trace event Philippe Mathieu-Daudé
2020-07-15 14:56 ` no-reply
2020-07-15 15:02   ` Philippe Mathieu-Daudé
2020-07-15 15:02 ` no-reply
2020-07-15 15:13 ` Daniel P. Berrangé
2020-07-15 19:27   ` Roman Bolshakov [this message]
2020-07-15 18:36 ` Roman Bolshakov

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=20200715192721.GD90799@SPB-NB-133.local \
    --to=r.bolshakov@yadro.com \
    --cc=berrange@redhat.com \
    --cc=chen.zhang@intel.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=zhangchen.fnst@cn.fujitsu.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).