qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: freebsd-emulation@freebsd.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5313)
Date: Tue, 30 Sep 2008 09:51:33 -0500	[thread overview]
Message-ID: <48E23CF5.4000805@codemonkey.ws> (raw)
In-Reply-To: <200809272252.m8RMq4fu057049@saturn.kn-bremen.de>

Juergen Lock wrote:
> In article <48DE5256.5000101@codemonkey.ws> you write:
>   
>> [...]
>>     
>
>   
>>>> The one thing that really tripped me up with the whole aio kld-module 
>>>> thing.  Perhaps we should detect the presence of the module at run time and 
>>>> disable aio?  I assume kldload can only be run as root?
>>>>     
>>>>         
>>> Yes.  Atm the ports print a warning when aio is not loaded:
>>>   
>>>       
>> Yeah, I don't think this is enough.  I'd rather see AIO be disabled when 
>> modfind("aio") is not available (printing a warning along with that 
>> would be fine).  A non-privileged user cannot load the aio module so 
>> it's not very useful to tell them to load it.
>>     
>
> OK so how about the following?  (only tested with a raw image, but if
> the way its disabled for OpenBSD works for all of them this should as well.)
>
>  Oh and am I right qemu-img doesn't use aio?  If it actually does we may
> want to add the same check there instead of just disabling it.  (I kept it
> enabled for qemu-nbd since thats not built on FreeBSD anyway.)
>   

Disabling aio for everyone is not the right thing if posix-aio is broken.

What would be better is in block-raw-posix.c, to have a one type check 
of modfind() (if we're FreeBSD), and if it fails, set a flag that forces 
the aio routines to call bdrv_aio_{read,write}_em.

Regards,

Anthony Liguori

  reply	other threads:[~2008-09-30 14:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21 20:40 [Qemu-devel] qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates Juergen Lock
2008-09-22 15:30 ` Anthony Liguori
2008-09-24 21:52   ` Juergen Lock
2008-09-23 13:39 ` [Qemu-devel] " Matt
2008-09-24 22:10   ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5313) Juergen Lock
2008-09-25  2:54     ` Matt
2008-09-26 15:04       ` Anthony Liguori
2008-09-26 15:52         ` Carlos A. M. dos Santos
2008-09-26 22:04         ` Juergen Lock
2008-09-27 15:33           ` Anthony Liguori
2008-09-27 22:52             ` Juergen Lock
2008-09-30 14:51               ` Anthony Liguori [this message]
2008-09-30 22:17                 ` Juergen Lock
2008-09-27 20:47           ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5331) Juergen Lock
2008-09-28  4:04             ` Carlos A. M. dos Santos
2008-09-30 22:33               ` Juergen Lock
2008-10-11 21:41                 ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5457) Juergen Lock
2008-10-18 20:46                   ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5499) Juergen Lock
2008-09-30 14:52             ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5331) Anthony Liguori
2008-09-30 22:35               ` Juergen Lock
2008-09-25 20:17     ` [Qemu-devel] [PATCH] preprocessor issue in qemu/patch-block-raw-posix.c (was: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5313)) Juergen Lock
2008-09-25 20:39       ` [Qemu-devel] [PATCH] preprocessor issue in qemu/patch-block-raw-posix.c Anthony Liguori
2008-09-26 21:29         ` Juergen Lock
2008-09-27 15:27           ` 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=48E23CF5.4000805@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=freebsd-emulation@freebsd.org \
    --cc=nox@jelal.kn-bremen.de \
    --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).