All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, Jay Mann <jmandawg@hotmail.com>,
	Uri Lublin <ulublin@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: Problems KVM-84
Date: Wed, 11 Mar 2009 15:19:12 -0500	[thread overview]
Message-ID: <49B81CC0.20303@codemonkey.ws> (raw)
In-Reply-To: <49B7D02E.1010307@redhat.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
>>> Scanning the file at startup is slow.  We need to find a better way.
>>
>> Any quick ideas?  Seems like this is broken by design.  
>
> I agree.
>
>> Unless we can find a quick fix, I'm going to revert this in the 
>> stable tree.
>
> We could cache the value in some unused area.  Set it up in qemu-img.  
> Don't support it on older images.
>
> But that's not a quick fix; I'd suggest reverting it in both stable 
> and mainline, and re-applying in mainline when there's a fix.

Done.  Uri, please submit the series again when you've found a solution 
to these problems.

Regards,

Anthony Liguori


WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Jay Mann <jmandawg@hotmail.com>, Uri Lublin <ulublin@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: Problems KVM-84
Date: Wed, 11 Mar 2009 15:19:12 -0500	[thread overview]
Message-ID: <49B81CC0.20303@codemonkey.ws> (raw)
In-Reply-To: <49B7D02E.1010307@redhat.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
>>> Scanning the file at startup is slow.  We need to find a better way.
>>
>> Any quick ideas?  Seems like this is broken by design.  
>
> I agree.
>
>> Unless we can find a quick fix, I'm going to revert this in the 
>> stable tree.
>
> We could cache the value in some unused area.  Set it up in qemu-img.  
> Don't support it on older images.
>
> But that's not a quick fix; I'd suggest reverting it in both stable 
> and mainline, and re-applying in mainline when there's a fix.

Done.  Uri, please submit the series again when you've found a solution 
to these problems.

Regards,

Anthony Liguori

  reply	other threads:[~2009-03-11 20:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  0:58 Problems KVM-84 Jay Mann
2009-02-27  6:52 ` Thomas Mueller
2009-03-09 10:22 ` Avi Kivity
2009-03-09 12:19   ` jmandawg
2009-03-09 12:19     ` jmandawg
2009-03-09 12:37       ` Avi Kivity
     [not found]         ` <BAY102-W25DF72B635B00AD337130D2A00@phx.gbl>
2009-03-10  8:39           ` Avi Kivity
     [not found]             ` <BAY102-W2139785413083807492C85D2A10@phx.gbl>
2009-03-10 13:47               ` Avi Kivity
2009-03-11 11:15 ` Avi Kivity
2009-03-11 11:15   ` [Qemu-devel] " Avi Kivity
2009-03-11 14:12   ` Anthony Liguori
2009-03-11 14:12     ` [Qemu-devel] " Anthony Liguori
2009-03-11 14:52     ` Avi Kivity
2009-03-11 20:19       ` Anthony Liguori [this message]
2009-03-11 20:19         ` Anthony Liguori
2009-03-11 16:06     ` Jamie Lokier
2009-03-11 16:06       ` Jamie Lokier
2009-03-11 22:59       ` Uri Lublin
2009-03-11 22:59         ` [Qemu-devel] " Uri Lublin
2009-03-11 18:37     ` Uri Lublin
2009-03-11 18:37       ` [Qemu-devel] " Uri Lublin

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=49B81CC0.20303@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jmandawg@hotmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ulublin@redhat.com \
    /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.