All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	David Hildenbrand <david@redhat.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v5 2/2] memory: Have 'info mtree' remove duplicated Address Space information
Date: Fri, 3 Sep 2021 17:53:24 +0200	[thread overview]
Message-ID: <cef9a003-e3a8-8dd1-a03b-9d0046ed3f6d@redhat.com> (raw)
In-Reply-To: <YTJBotzQOjfQ9L7p@t490s>

On 9/3/21 5:39 PM, Peter Xu wrote:
> On Fri, Sep 03, 2021 at 10:40:25AM +0200, Philippe Mathieu-Daudé wrote:
>> On 9/2/21 11:55 PM, Peter Xu wrote:
>>> Hi, Phil,
>>>
>>> On Thu, Sep 02, 2021 at 08:26:04AM +0200, Philippe Mathieu-Daudé wrote:
>>>>   address-space shared 4 times:
>>>
>>> I commented on the format of the output, I saw that it's switched back to the
>>> v1.  Any reason?
>>
>> The code uses the format you asked, I simply forgot to update the
>> commit description :/ Sorry, I'll respin.
> 
> But I'm talking actually about the code too. :) After your answer I feel like
> it's just an accident anyway.  Thanks,

Doh sorry... Not sure how I messed that bad :S



      reply	other threads:[~2021-09-03 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02  6:26 [PATCH v5 0/2] memory: Have 'info mtree' remove duplicated Address Space information Philippe Mathieu-Daudé
2021-09-02  6:26 ` [PATCH v5 1/2] memory: Split mtree_info() as mtree_info_flatview() + mtree_info_as() Philippe Mathieu-Daudé
2021-09-02 21:55   ` Peter Xu
2021-09-02  6:26 ` [PATCH v5 2/2] memory: Have 'info mtree' remove duplicated Address Space information Philippe Mathieu-Daudé
2021-09-02 21:55   ` Peter Xu
2021-09-03  8:40     ` Philippe Mathieu-Daudé
2021-09-03 15:39       ` Peter Xu
2021-09-03 15:53         ` Philippe Mathieu-Daudé [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=cef9a003-e3a8-8dd1-a03b-9d0046ed3f6d@redhat.com \
    --to=philmd@redhat.com \
    --cc=david@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@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.