qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel Developers <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [RFC] darwin: work around sigfd
Date: Mon, 30 May 2011 10:03:06 +0200	[thread overview]
Message-ID: <4DE34F3A.4010103@redhat.com> (raw)
In-Reply-To: <1C4D237A-A027-4758-9E4C-EFEEE88EF00F@web.de>

On 05/29/2011 06:50 PM, Andreas Färber wrote:
> Am 08.05.2011 um 11:15 schrieb Andreas Färber:
>
>> Am 05.05.2011 um 15:15 schrieb Alexander Graf:
>>
>>> On 05.05.2011, at 14:56, Paolo Bonzini wrote:
>>>
>>>> On 05/05/2011 11:36 AM, Alexander Graf wrote:
>>>>> When running qemu-system on Darwin, the vcpu processes guest code, but
>>>>> I don't get to see anything on the cocoa screen.
>>>>
>>>> Out of curiosity, does it work with iothread?
>>>
>>> Seems to work with -nographic, yes. With cocoa it doesn't seem as
>>> happy :o. It certainly gets a lot further than without.
>>
>> -nographic has issues with --enable-io-thread, too.
>
> Ping?

The patch is obviously masking the real issue, I don't think Alex meant 
it to be applied.

I would really like to look at iothread under Mac OS X, but I just don't 
have the time right now.

Paolo

  reply	other threads:[~2011-05-30  8:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05  9:36 [Qemu-devel] [RFC] darwin: work around sigfd Alexander Graf
2011-05-05 12:56 ` Paolo Bonzini
2011-05-05 13:15   ` Alexander Graf
2011-05-05 13:23     ` Paolo Bonzini
2011-05-05 13:24       ` Alexander Graf
2011-05-08  9:15     ` Andreas Färber
2011-05-08 10:10       ` Andreas Färber
2011-05-09 14:04         ` Alexander Graf
2011-05-29 16:50       ` Andreas Färber
2011-05-30  8:03         ` Paolo Bonzini [this message]
2011-05-31 21:44           ` Andreas Färber

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=4DE34F3A.4010103@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=andreas.faerber@web.de \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    /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).