[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3] memory: Have 'info mtree' remove duplicated Address Space
|
From: |
Philippe Mathieu-Daudé |
|
Subject: |
Re: [PATCH v3] memory: Have 'info mtree' remove duplicated Address Space information |
|
Date: |
Mon, 23 Aug 2021 12:11:00 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 |
On 8/23/21 11:35 AM, David Hildenbrand wrote:
> On 23.08.21 11:28, Peter Maydell wrote:
>> On Mon, 23 Aug 2021 at 10:20, David Hildenbrand <david@redhat.com> wrote:
>>>
>>> On 23.08.21 10:54, Philippe Mathieu-Daudé wrote:
>>>> +static void mtree_print_as(gpointer key, gpointer value, gpointer
>>>> user_data)
>>>> +{
>>>> + MemoryRegion *mr = key;
>>>> + GSList *as_same_root_mr_list = value;
>>>> + struct AddressSpaceInfo *asi = user_data;
>>>
>>> Reverse Christmas tree?
I simply followed to order of the arguments as a no-brainer ;)
>> This has never been part of the QEMU style guidelines
>> and I would oppose our adding it. It would gain us very little,
>> the codebase doesn't consistently follow that rule today so
>> it wouldn't be preserving an existing consistency of style,
>> and it would be yet another weird stylistic issue that trips
>> people up and requires patch repins.
(in this particular case I've to respin for a typo).
> Ah right, it used very inconsistently in the QEMU codebase and even in
> this file (I spotted it's the case in the entry of mtree_info() and
> wondered if it's the case for this file -- turns out it's absolutely not).