All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Michael Tokarev <mjt@tls.msk.ru>, <qemu-devel@nongnu.org>
Cc: qemu-trivial@nongnu.org, shannon.zhao@linaro.org
Subject: Re: [Qemu-trivial] [PATCH v3 0/8] Add a member in MachineState to store irq array
Date: Thu, 18 Jun 2015 18:29:42 +0800	[thread overview]
Message-ID: <55829D96.1040607@huawei.com> (raw)
In-Reply-To: <558121F9.6010804@msgid.tls.msk.ru>



On 2015/6/17 15:30, Michael Tokarev wrote:
> 17.06.2015 05:59, Shannon Zhao wrote:
>> From: Shannon Zhao <shannon.zhao@linaro.org>
>>
>> These are relevant to memory leak in machine init function. Here we add
>> a member in MachineState to store irq array returned from
>> qemu_allocate_irqs.
>>
>> PS. These patches are split from my previous patchset [1] since they are
>> relevant to MachineState.
>>
>> Thanks,
>> Shannon
>>
>> [1] [PATCH 00/29] Fix memory leak relevant to calling qemu_allocate_irqs
>>
>> changes since v2:
>>   * Rebased on QEMU upstream
>>   * Add a member in MachineState first, then fix the memory leak [mjt]
> 
> Um.  This is not what I asked.  It was a small suggestion, to add
> infrastructure first use it in subsequent patches.
> 
> But the main question was what this infrastructure, what this patchset
> actually brings us?  You just store the irq pointer in machine state,
> that's okay, but WHAT FOR?  If your intention is to free resources,
> this intention isn't met.  The end result of this whole change is a no-op,
> there's nothing changed, the memory which has been allocated isn't being
> freed.
> 

Ok, will rethink about.

> So the actual question is: what's the point of this patchset?
> 
> Thanks,
> 
> /mjt
> 
> 
> .
> 

-- 
Shannon



WARNING: multiple messages have this Message-ID (diff)
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, shannon.zhao@linaro.org
Subject: Re: [Qemu-devel] [PATCH v3 0/8] Add a member in MachineState to store irq array
Date: Thu, 18 Jun 2015 18:29:42 +0800	[thread overview]
Message-ID: <55829D96.1040607@huawei.com> (raw)
In-Reply-To: <558121F9.6010804@msgid.tls.msk.ru>



On 2015/6/17 15:30, Michael Tokarev wrote:
> 17.06.2015 05:59, Shannon Zhao wrote:
>> From: Shannon Zhao <shannon.zhao@linaro.org>
>>
>> These are relevant to memory leak in machine init function. Here we add
>> a member in MachineState to store irq array returned from
>> qemu_allocate_irqs.
>>
>> PS. These patches are split from my previous patchset [1] since they are
>> relevant to MachineState.
>>
>> Thanks,
>> Shannon
>>
>> [1] [PATCH 00/29] Fix memory leak relevant to calling qemu_allocate_irqs
>>
>> changes since v2:
>>   * Rebased on QEMU upstream
>>   * Add a member in MachineState first, then fix the memory leak [mjt]
> 
> Um.  This is not what I asked.  It was a small suggestion, to add
> infrastructure first use it in subsequent patches.
> 
> But the main question was what this infrastructure, what this patchset
> actually brings us?  You just store the irq pointer in machine state,
> that's okay, but WHAT FOR?  If your intention is to free resources,
> this intention isn't met.  The end result of this whole change is a no-op,
> there's nothing changed, the memory which has been allocated isn't being
> freed.
> 

Ok, will rethink about.

> So the actual question is: what's the point of this patchset?
> 
> Thanks,
> 
> /mjt
> 
> 
> .
> 

-- 
Shannon

  reply	other threads:[~2015-06-18 10:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  2:59 [Qemu-trivial] [PATCH v3 0/8] Add a member in MachineState to store irq array Shannon Zhao
2015-06-17  2:59 ` [Qemu-devel] " Shannon Zhao
2015-06-17  2:59 ` [Qemu-trivial] [PATCH v3 1/8] include/hw/boards.h: " Shannon Zhao
2015-06-17  2:59   ` [Qemu-devel] " Shannon Zhao
2015-06-17  3:16   ` [Qemu-trivial] " Peter Crosthwaite
2015-06-17  3:16     ` Peter Crosthwaite
2015-06-17  2:59 ` [Qemu-trivial] [PATCH v3 2/8] hw/ppc/ppc440_bamboo.c: Store irq array in MachineState to fix memory leak Shannon Zhao
2015-06-17  2:59   ` [Qemu-devel] " Shannon Zhao
2015-06-17  2:59 ` [Qemu-trivial] [PATCH v3 3/8] hw/sparc/leon3.c: " Shannon Zhao
2015-06-17  2:59   ` [Qemu-devel] " Shannon Zhao
2015-06-17  2:59 ` [Qemu-trivial] [PATCH v3 4/8] hw/m68k/an5206.c: " Shannon Zhao
2015-06-17  2:59   ` [Qemu-devel] " Shannon Zhao
2015-06-17  2:59 ` [Qemu-trivial] [PATCH v3 5/8] hw/sh4/r2d.c: " Shannon Zhao
2015-06-17  2:59   ` [Qemu-devel] " Shannon Zhao
2015-06-17  3:00 ` [Qemu-trivial] [PATCH v3 6/8] hw/arm/palm.c: " Shannon Zhao
2015-06-17  3:00   ` [Qemu-devel] " Shannon Zhao
2015-06-17  3:00 ` [Qemu-trivial] [PATCH v3 7/8] hw/arm/spitz.c: " Shannon Zhao
2015-06-17  3:00   ` [Qemu-devel] " Shannon Zhao
2015-06-17  3:00 ` [Qemu-trivial] [PATCH v3 8/8] hw/arm/tosa.c: " Shannon Zhao
2015-06-17  3:00   ` [Qemu-devel] " Shannon Zhao
2015-06-17  7:30 ` [Qemu-trivial] [PATCH v3 0/8] Add a member in MachineState to store irq array Michael Tokarev
2015-06-17  7:30   ` [Qemu-devel] " Michael Tokarev
2015-06-18 10:29   ` Shannon Zhao [this message]
2015-06-18 10:29     ` Shannon Zhao

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=55829D96.1040607@huawei.com \
    --to=zhaoshenglong@huawei.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=shannon.zhao@linaro.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.