public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Use qemu_memalign instead of qemu_malloc
Date: Wed, 25 Jun 2008 16:29:31 +0200	[thread overview]
Message-ID: <4862564B.8080108@suse.de> (raw)
In-Reply-To: <48625404.9070803@us.ibm.com>

Anthony Liguori schrieb:
> Kevin Wolf wrote:
>> Anthony Liguori schrieb:
>>  
>> Yes, if it fails, the EINVAL is no surprise. I meant what code path it
>> was using. Obviously we missed something in our patch and I'd like to
>> fix that. Did the error occur on raw images or something like qcow2?
>>   
> 
> It's a raw image and the calls are being made via
> bdrv_aio_read/bdrv_aio_write.  It doesn't occur with a qcow2 but then
> cache=off doesn't seem to do what it's supposed to with cache=off (I
> believe the underlying backing file is not opened O_DIRECT?).

This is really strange. In raw_aio_read/write there is a check like this:

    if (unlikely(s->aligned_buf != NULL && ((uintptr_t) buf % 512))) {
        // emulate it using raw_pread/write which uses
        // s->aligned_buf for the request then
    }

For qcow2 I think O_DIRECT actually is in effect. Otherwise it would
have worked even without our patch, and it didn't. And indeed, looking
at the code, it passes flags to bdrv_file_open when it opens the image file.

Kevin

  reply	other threads:[~2008-06-25 14:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 18:49 [PATCH] Use qemu_memalign instead of qemu_malloc Anthony Liguori
2008-06-25  9:19 ` Kevin Wolf
2008-06-25 13:48   ` Anthony Liguori
2008-06-25 14:15     ` Kevin Wolf
2008-06-25 14:19       ` Anthony Liguori
2008-06-25 14:29         ` Kevin Wolf [this message]
2008-06-25 15:22           ` Anthony Liguori
2008-06-25 15:29             ` Kevin Wolf
2008-06-25 15:44               ` Anthony Liguori
2008-06-25 14:55       ` Laurent Vivier
2008-06-25 15:14         ` Kevin Wolf

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=4862564B.8080108@suse.de \
    --to=kwolf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.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