From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/6] kvm: vga optimization.
Date: Wed, 19 Nov 2008 11:26:45 -0600 [thread overview]
Message-ID: <49244C55.6040900@codemonkey.ws> (raw)
In-Reply-To: <5d6222a80811190919m22e55172xdd6ab4bf6e514c7f@mail.gmail.com>
Glauber Costa wrote:
>>> + if (!s->map_addr)
>>> + return;
>>> +
>>> + if (cirrus_lfb_is_mapped(s)) {
>>> + cpu_register_physical_memory(isa_mem_base + 0xa0000, 0x8000,
>>> + (s->vram_offset +
>>> s->cirrus_bank_base[0]) | IO_MEM_RAM);
>>> + cpu_register_physical_memory(isa_mem_base + 0xa8000, 0x8000,
>>> + (s->vram_offset +
>>> s->cirrus_bank_base[1]) | IO_MEM_RAM);
>>>
>>>
>> Isn't necessary to reregister 0xa0000 too?
>>
>
> ENOFOLLOW. This is exactly what I'm doing.
>
I was confused about isa_mem_base. Just ignore me :-).
Regards,
Anthony Liguori
>>> + if (kvm_enabled()) {
>>> + kvm_log_start(0xa0000, 0x8000);
>>> + kvm_log_start(0xa8000, 0x8000);
>>> + }
>>>
>>>
>> Why would you enable logging on a different region from what you've
>> registered? Shouldn't you enable logging on both regions? If we're going
>> to enable logging based on target_phys_addr_t instead of ram_addr_t (and I
>> think we should), then we should enable it on all target_phys_addr_ts.
>>
>
> Again, I don't follow. We map 0xa0000 and 0xa8000 to some ram_addr_t,
> and then enable logging in the very 0xa0000 and 0xa8000. What's the problem
> with that? One late nitpick, it is that for consistency, I registered
> 0xa0000 + isa_mem_base,
> (usually 0), and should use it in kvm_log_start.
>
>
>>> + }
>>> + else {
>>>
>>>
>> This is formatted incorrectly.
>>
>>
>>> +
>>> /*
>>> * graphic modes
>>> */
>>>
>>>
>> More extra whitespace.
>>
>> Regards,
>>
>> Anthony Liguori
>>
>>
>>
>>
>
>
>
>
prev parent reply other threads:[~2008-11-19 17:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 15:26 [Qemu-devel] [PATCH 0/6] New shot at VGA optimization Glauber Costa
2008-11-19 14:23 ` Avi Kivity
2008-11-19 14:34 ` Glauber Costa
2008-11-19 15:26 ` [Qemu-devel] [PATCH 1/6] kvm: memory aliasing support for kvm Glauber Costa
2008-11-19 15:07 ` Anthony Liguori
2008-11-19 15:26 ` [Qemu-devel] [PATCH 2/6] better type checking for vga Glauber Costa
2008-11-19 15:08 ` Anthony Liguori
2008-11-19 15:26 ` [Qemu-devel] [PATCH 3/6] move vga_io_address to VGA State Glauber Costa
2008-11-19 15:26 ` [Qemu-devel] [PATCH 4/6] kvm: de-register mem region for MMIO Glauber Costa
2008-11-19 15:10 ` Anthony Liguori
2008-11-19 15:26 ` [Qemu-devel] [PATCH 5/6] Introduce kvm logging interface Glauber Costa
2008-11-19 15:18 ` Anthony Liguori
2008-11-19 17:23 ` Glauber Costa
2008-11-19 17:51 ` Anthony Liguori
2008-11-19 15:26 ` [Qemu-devel] [PATCH 6/6] kvm: vga optimization Glauber Costa
2008-11-19 15:23 ` Anthony Liguori
2008-11-19 17:19 ` Glauber Costa
2008-11-19 17:26 ` Anthony Liguori [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=49244C55.6040900@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).