qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6343] Fix false positive for AIO on OpenBSD
Date: Fri, 16 Jan 2009 12:50:18 -0600	[thread overview]
Message-ID: <4970D6EA.2020700@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580901161041v52bd5be6u74f00d8a3e1e1e8b@mail.gmail.com>

Blue Swirl wrote:
> On 1/16/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
>   
>> Blue Swirl wrote:
>>
>>     
>>> Revision: 6343
>>>
>>>       
>> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6343
>>     
>>> Author:   blueswir1
>>> Date:     2009-01-16 18:13:32 +0000 (Fri, 16 Jan 2009)
>>>
>>> Log Message:
>>> -----------
>>> Fix false positive for AIO on OpenBSD
>>>
>>>
>>>       
>>  If OpenBSD doesn't have sigqueue, we could just replace it with kill.  I
>> don't think we need to disable AIO.
>>     
>
> struct sigevent is also missing, is that a problem?
>   

It's just used for assigning the signal value.  We could have a #ifdef 
HAVE_SIGEVENT and define it if it doesn't exist--or just change the 
aioinit structure to use an int instead of the struct sigevent 
structure.  It's sigevent for glibc compatibility but that's not really 
important at this stage.

Regards,

Anthony Liguori

  reply	other threads:[~2009-01-16 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 18:13 [Qemu-devel] [6343] Fix false positive for AIO on OpenBSD Blue Swirl
2009-01-16 18:33 ` Anthony Liguori
2009-01-16 18:41   ` Blue Swirl
2009-01-16 18:50     ` Anthony Liguori [this message]
2009-01-16 19:03       ` Blue Swirl
2009-01-16 19:09         ` Anthony Liguori
2009-01-16 21:19           ` Blue Swirl
2009-01-16 21:39             ` Anthony Liguori

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=4970D6EA.2020700@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).