All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vga optmization
Date: Fri, 07 Nov 2008 11:33:58 +0000	[thread overview]
Message-ID: <491427A6.3070407@eu.citrix.com> (raw)
In-Reply-To: <20081107111547.GB15827@poweredge.glommer>

Glauber Costa wrote:

> On Wed, Nov 05, 2008 at 02:42:22PM +0000, Stefano Stabellini wrote:
>> Glauber Costa wrote:
>>
>>>> That's also how currently qemu-xen works.
>>>> I am glad that we agree :)
>>> I'm attaching a new version. Let me know if it's better this way.
>>>
>>
>>
>> Yes, this is much better thanks.
>>
>> I still have comments about possible improvements, so I wrote patch
>> (against your patch).
>> This patch is not meant to be applied, is only meant to be read (I believe
>> that C code is more meaningful than English :).
>>
>> Some of the changes include:
>>
>> - instead of adding cirrus_lfb_addr, add a more generic lfb_addr to
>> VGAState, so that can be reused in the future for possible stdvga only
>> mappings;
>>
>> - instead of using cirrus_lfb_mapped as a boolean, use it as the
>> mapping address, it is more useful that way;
>>
>> - instead of keeping the kvm dirty map always enabled, enable it only
>> when the framebuffer is linear and in graphical mode;
>>
>> - look at the changes to vga.c, there is a simple check to reduce the
>> dirty area to sync.
>>
>> It would be nice to check if the last two changes are actually a
>> performance improvement.
> I'm not opposed to the changes. I'll redo a patch and resend it today.
> However, I'm not planning to include the last optimization you sent.
> It is better that we do it in a separate commit. If you can get numbers,
> even better. I'll try it myself too.

Fine with me.

      reply	other threads:[~2008-11-07 11:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 17:31 [Qemu-devel] vga optmization Glauber Costa
2008-11-03 17:43 ` Stefano Stabellini
2008-11-03 17:52   ` Glauber Costa
2008-11-03 18:06     ` Stefano Stabellini
2008-11-03 18:03 ` Blue Swirl
2008-11-03 18:14   ` Glauber Costa
2008-11-03 18:41     ` Blue Swirl
2008-11-03 18:47       ` Glauber Costa
2008-11-03 18:13 ` Fabrice Bellard
2008-11-03 18:18   ` Glauber Costa
2008-11-04  7:23 ` Avi Kivity
2008-11-04  9:31 ` andrzej zaborowski
2008-11-04 11:40   ` Stefano Stabellini
2008-11-04 13:43     ` Glauber Costa
2008-11-04 14:51     ` Avi Kivity
2008-11-04 14:52       ` Anthony Liguori
2008-11-04 14:55       ` Glauber Costa
2008-11-04 15:13         ` Stefano Stabellini
2008-11-04 20:42         ` Avi Kivity
2008-11-04 20:51           ` Anthony Liguori
2008-11-04 15:01       ` Stefano Stabellini
2008-11-04 20:28         ` Glauber Costa
2008-11-04 20:40           ` Anthony Liguori
2008-11-05 14:42           ` Stefano Stabellini
2008-11-07 11:15             ` Glauber Costa
2008-11-07 11:33               ` Stefano Stabellini [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=491427A6.3070407@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=aliguori@us.ibm.com \
    --cc=glommer@redhat.com \
    --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 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.