qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org, freebsd-emulation@freebsd.org
Subject: Re: [Qemu-devel] testing qemu svn r6367 on FreeBSD - sigev_signo; vmmouse, -vga vmware broken, slirp...
Date: Sat, 24 Jan 2009 13:55:38 +0200	[thread overview]
Message-ID: <f43fc5580901240355k7c82a5bcq99863d9e6fe91adb@mail.gmail.com> (raw)
In-Reply-To: <20090118231436.GA9565@saturn.kn-bremen.de>

On 1/19/09, Juergen Lock <nox@jelal.kn-bremen.de> wrote:
> Hi!
>
>   I've made another experimental FreeBSD qemu-devel port update,
>         http://people.freebsd.org/~nox/qemu/qemu-devel-20090118.patch
>  and of the few things I've tested so far I only found vmmouse and -vga vmware
>  broken now, vmmouse leaves the mouse cursor stuck in the top left corner,
>  and -vga vmware causes a broken display at least with xorg's vmware driver.
>  (both of these worked at least with the r6082, 2008-12-18 snapshot as
>  posted in
>         http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg01417.html
>  )
>
>   virtio and hpet still seem to work, and slirp indeed seems to finally work
>  on amd64 hosts.
>
>   FreeBSD has a #define sigev_signo      __sigev_u.__sigev_signo
>  in <sys/signal.h> so I've had to patch it to something different in
>  the posix-aio-compat code:
>
>  Index: qemu/posix-aio-compat.h
>  @@ -29,7 +29,7 @@
>      int aio_fildes;
>      void *aio_buf;
>      size_t aio_nbytes;
>  -    int sigev_signo;
>  +    int ev_signo;
>      off_t aio_offset;
>
>      /* private */
>  Index: qemu/posix-aio-compat.c
>  @@ -94,7 +94,7 @@
>          idle_threads++;
>          pthread_mutex_unlock(&lock);
>
>  -        kill(getpid(), aiocb->sigev_signo);
>  +        kill(getpid(), aiocb->ev_signo);
>      }
>
>      idle_threads--;
>  Index: qemu/block-raw-posix.c
>  @@ -579,7 +579,7 @@
>      if (!acb)
>          return NULL;
>      acb->aiocb.aio_fildes = s->fd;
>  -    acb->aiocb.sigev_signo = SIGUSR2;
>  +    acb->aiocb.ev_signo = SIGUSR2;
>      acb->aiocb.aio_buf = buf;
>      if (nb_sectors < 0)
>          acb->aiocb.aio_nbytes = -nb_sectors;
>
>   More tests welcome...

Thanks, applied.

      parent reply	other threads:[~2009-01-24 11:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 23:14 [Qemu-devel] testing qemu svn r6367 on FreeBSD - sigev_signo; vmmouse, -vga vmware broken, slirp Juergen Lock
2009-01-20 14:19 ` Jędrzej Kalinowski
2009-01-20 19:31   ` Matt
2009-01-20 23:12   ` More displaystate fallout? (was: Re: [Qemu-devel] testing qemu svn r6367 on FreeBSD - sigev_signo; vmmouse, -vga vmware broken, slirp...) Juergen Lock
2009-01-21 11:15     ` [Qemu-devel] Re: More displaystate fallout? (was: Re: [Qemu- devel] testing qemu svn r6367 on FreeB SD - sigev_signo; vmmouse, -vga vmware broken , slirp...) Jędrzej Kalinowski
2009-01-21 12:28       ` [Qemu-devel] Re: More displaystate fallout? Stefano Stabellini
2009-01-21 17:46         ` Stefan Weil
2009-01-21 18:15           ` Stefano Stabellini
2009-01-21 21:34             ` Stefan Weil
2009-01-22 14:11               ` Stefano Stabellini
2009-01-27 14:23                 ` Stefano Stabellini
2009-01-29 14:55               ` Stefano Stabellini
2009-01-24 11:55 ` Blue Swirl [this message]

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=f43fc5580901240355k7c82a5bcq99863d9e6fe91adb@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=freebsd-emulation@freebsd.org \
    --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).