[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] hmp: Improve 'info mtree' with optional parm fo
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH] hmp: Improve 'info mtree' with optional parm for mapinfo |
Date: |
Tue, 20 Sep 2016 09:56:04 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
On 20/09/2016 02:51, Laszlo Ersek wrote:
> Here's an example, from one of your sample outputs: you currently have
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 00000000000c0000-00000000000c3fff (prio 1, RW): alias pam-ram @pc.ram
> 00000000000c0000-00000000000c3fff [disabled]
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 00000000000c0000-00000000000c3fff (prio 1, RW): alias pam-pci @pc.ram
> 00000000000c0000-00000000000c3fff [disabled]
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> 00000000000c0000-00000000000c3fff (prio 1, R-): alias pam-rom @pc.ram
> 00000000000c0000-00000000000c3fff
> ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
> 00000000000c0000-00000000000c3fff (prio 1, RW): alias pam-pci @pci
> 00000000000c0000-00000000000c3fff [disabled]
>
> with
>
> @: alias region mapped at sample
> ~: alias region mappable but disabled at sample
> o: region occluded by some other region at sample
>
> If you have an address in the c0000-c3fff range, you have to consult all four
> lines to see which region will match.
>
> Working off of the FlatView, first I think you would find the right
> resolution for the output "for free" (you wouldn't need a user sample size --
> the interval c0000-c3fff would neither need further subdivision nor be
> blurred by over-coarse resolution). You could represent the c0000-c3fff
> interval (and every other interval too) with a single letter, such as P,
> where P would stand for "alias pam-rom @pc.ram
> 00000000000c0000-00000000000c3fff".
>
> Second, given an address in c0000-c3fff, there would be only one range to
> consult (same as QEMU itself does with FlatView), and you'd find the
> MemoryRegion visible in that range at once.
>
> ... I hope Paolo will correct me if I misunderstood his suggestion.
Yes, this would work. Alternatively, dumping the flat-view would give
you something much simpler:
0000000000000000-000000000009ffff (RW): pc.ram
00000000000a0000-00000000000bffff (RW): vga-lowmem
00000000000c0000-00000000000fffff (R-): pc.ram @ 00000000000c0000
0000000000100000-0000000007ffffff (RW): pc.ram @ 0000000000100000
00000000fd000000-00000000fdffffff (RW): vga.vram
00000000febc0000-00000000febdffff (RW): e1000-mmio
00000000febf0000-00000000febf0fff (RW): vga.mmio
00000000febf0400-00000000febf041f (RW): vga ioports remapped
00000000febf0500-00000000febf0515 (RW): bochs dispi interface
00000000febf0600-00000000febf0607 (RW): qemu extended regs
00000000fec00000-00000000fec00fff (RW): ioapic
00000000fed00000-00000000fed003ff (RW): hpet
00000000fee00000-00000000feefffff (RW): apic-msi
00000000fffc0000-00000000ffffffff (R-): pc.bios
This is less information of course, but it may good idea depending on
_why_ you're doing that.
Paolo
signature.asc
Description: OpenPGP digital signature