qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vga optmization
Date: Mon, 3 Nov 2008 20:03:41 +0200	[thread overview]
Message-ID: <f43fc5580811031003i4eea1fb0pc93c5e45f807767e@mail.gmail.com> (raw)
In-Reply-To: <20081103173111.GC30410@poweredge.glommer>

On 11/3/08, Glauber Costa <glommer@redhat.com> wrote:
> Hi guys,
>
>  this is a port of current kvm vga memory optimization to our new
>  infrastructure proposed by anthony. It's goal is to use as few
>  kvm specific hooks as possible. In fact, the only one I'm relying
>  on is enabling/disabling of logging. The rest, is pretty much general.
>
>  We map the linear frame buffer area as RAM, and then use dirty tracking
>  to decide whether or not to update it. To be consistent with qemu,
>  this version, differently from upstream kvm, tracks memory based on its
>  physical address, represented by vram_offset, instead of vram_ptr, or
>  any other construct.
>
>  Let me know what you think

The patch does not apply, because of the kvm files. What patches do I
need to apply first? I'd like to see how does the optimization apply
to TCX.

This also may mean that some of my comments below can be invalid.

>  +void set_vram_mapping(target_phys_addr_t begin, target_phys_addr_t end, ram_addr_t target)

No "static"?

>  +{
>  +    /* align begin and end address */
>  +    begin = begin & TARGET_PAGE_MASK;
>  +    end = begin + VGA_RAM_SIZE;
>  +    end = (end + TARGET_PAGE_SIZE -1 ) & TARGET_PAGE_MASK;

This will fail if "end" is at the last page of the memory.

>  +void unset_vram_mapping(target_phys_addr_t begin, target_phys_addr_t end)

No "static"?

>  +{
>  +    /* align begin and end address */
>  +    end = begin + VGA_RAM_SIZE;
>  +    begin = begin & TARGET_PAGE_MASK;
>  +    end = (end + TARGET_PAGE_SIZE -1 ) & TARGET_PAGE_MASK;

This will fail if "end" is at the last page of the memory.

>  +void unmap_linear_vram(CirrusVGAState *s)

No "static"?

>  +    uint32_t vga_io_memory;                                             \

cpu_register_io_memory() returns an "int".

  parent reply	other threads:[~2008-11-03 18:03 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 [this message]
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

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=f43fc5580811031003i4eea1fb0pc93c5e45f807767e@mail.gmail.com \
    --to=blauwirbel@gmail.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 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).