From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/6] hypertrace: [*-user] Add QEMU-side proxy to "guest_hypertrace" event
Date: Tue, 23 Aug 2016 11:52:24 -0400 [thread overview]
Message-ID: <20160823155224.GA3948@stefanha-x1.localdomain> (raw)
In-Reply-To: <87inuupbbw.fsf@fimbulvetr.bsc.es>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
On Sun, Aug 21, 2016 at 02:15:31PM +0200, Lluís Vilanova wrote:
> > Can this approach be made thread-safe?
>
> > If not then it would be good to consider the problem right away and
> > switch to something that is thread-safe, even if it depends on the
> > target architecture.
>
> Kind of. The easiest solution is to have each thread have an mmap of its own of
> the device (and moving qemu_control_{0,1} into CPUState). This would be
> completely explicit and easy to understand.
Yes. I don't know if the TCG and -user folks will accept the SIGSEGV
approach, but I'd be okay with it if the multi-threading issue is solved
by 1 device per thread.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-23 21:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 16:59 [Qemu-devel] [PATCH 0/6] hypertrace: Lightweight guest-to-QEMU trace channel Lluís Vilanova
2016-08-05 16:59 ` [Qemu-devel] [PATCH 1/6] hypertrace: Add documentation Lluís Vilanova
2016-08-05 17:17 ` Eric Blake
2016-08-08 13:02 ` Lluís Vilanova
2016-08-05 16:59 ` [Qemu-devel] [PATCH 2/6] hypertrace: Add tracing event "guest_hypertrace" Lluís Vilanova
2016-08-18 9:59 ` Stefan Hajnoczi
2016-08-18 10:32 ` Lluís Vilanova
2016-08-05 16:59 ` [Qemu-devel] [PATCH 3/6] hypertrace: [*-user] Add QEMU-side proxy to "guest_hypertrace" event Lluís Vilanova
2016-08-05 17:23 ` Eric Blake
2016-08-08 13:08 ` Lluís Vilanova
2016-08-18 10:17 ` Stefan Hajnoczi
2016-08-21 12:15 ` Lluís Vilanova
2016-08-23 15:52 ` Stefan Hajnoczi [this message]
2016-08-05 16:59 ` [Qemu-devel] [PATCH 4/6] hypertrace: [softmmu] " Lluís Vilanova
2016-08-05 16:59 ` [Qemu-devel] [PATCH 5/6] hypertrace: Add guest-side user-level library Lluís Vilanova
2016-08-05 16:59 ` [Qemu-devel] [PATCH 6/6] hypertrace: Add guest-side Linux module Lluís Vilanova
2016-08-18 9:47 ` [Qemu-devel] [PATCH 0/6] hypertrace: Lightweight guest-to-QEMU trace channel Stefan Hajnoczi
2016-08-18 10:22 ` Lluís Vilanova
2016-08-18 13:53 ` Stefan Hajnoczi
2016-08-18 14:21 ` Luiz Capitulino
2016-08-21 12:17 ` Lluís Vilanova
2016-08-18 10:54 ` Stefan Hajnoczi
2016-08-18 13:37 ` Luiz Capitulino
2016-08-19 4:45 ` Masami Hiramatsu
2016-08-18 16:19 ` Steven Rostedt
2016-08-19 10:02 ` Stefan Hajnoczi
2016-08-19 13:30 ` Steven Rostedt
2016-08-21 12:32 ` Lluís Vilanova
2016-08-23 15:54 ` Stefan Hajnoczi
2016-08-24 10:25 ` Lluís Vilanova
2016-08-29 13:45 ` Stefan Hajnoczi
2016-08-29 18:46 ` Lluís Vilanova
2016-08-31 16:35 ` Stefan Hajnoczi
2016-09-05 14:37 ` Lluís Vilanova
2016-09-05 19:20 ` Masami Hiramatsu
2016-09-06 12:59 ` Lluís Vilanova
2016-09-13 13:52 ` Stefan Hajnoczi
2016-09-13 16:50 ` Lluís Vilanova
2016-09-05 14:59 ` Daniel P. Berrange
2016-09-05 18:29 ` Lluís Vilanova
2016-09-05 18:59 ` Daniel P. Berrange
2016-09-06 8:54 ` Lluís Vilanova
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=20160823155224.GA3948@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=stefanha@gmail.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).