All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Kevin Wolf <kwolf@suse.de>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Use qemu_memalign instead of qemu_malloc
Date: Wed, 25 Jun 2008 09:19:48 -0500	[thread overview]
Message-ID: <48625404.9070803@us.ibm.com> (raw)
In-Reply-To: <486252FA.6030804@suse.de>

Kevin Wolf wrote:
> Anthony Liguori schrieb:
>   
>> Kevin Wolf wrote:
>>     
>>> Anthony Liguori schrieb:
>>>  
>>>       
>>>> I guess the main block code is not as defensive as I thought it was. 
>>>> This patch
>>>> uses qemu_memalign to allocate the buffers for IO so that you don't
>>>> get errors
>>>> when using O_DIRECT.
>>>>     
>>>>         
>>> Actually, the block code should be able to deal with unaligned buffers
>>> since qemu rev. 4599. This change seems to be present in current KVM.
>>>   
>>>       
>> That was what I thought at first too.
>>
>>     
>>> Can you tell exactly which operation failed?
>>>       
>> The aio requests fail with -22 (EINVAL).
>>     
>
> 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?).

Regards,

Anthony Liguori

> Kevin
>   


  reply	other threads:[~2008-06-25 14:20 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 [this message]
2008-06-25 14:29         ` Kevin Wolf
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=48625404.9070803@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.