All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Jingoo Han <jingoohan1@gmail.com>,
	Joao Pinto <Joao.Pinto@synopsys.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH v2 00/10] PCI: leak fixes, removable generic PCI host, assorted stuff
Date: Thu, 3 May 2018 09:52:16 +0200	[thread overview]
Message-ID: <cc97108e-f3db-fc0c-3a88-ced7291be617@siemens.com> (raw)
In-Reply-To: <e15c1cf5-0844-e5f1-d7af-e196207be6d4@mentor.com>

Hey Vladimir,

On 2018-05-03 09:12, Vladimir Zapolskiy wrote:
> Hi Jan,
> 
> On 04/30/2018 08:48 AM, Jan Kiszka wrote:
>> Changes in v2:
>>  - patch 1: commit message reworking as suggested by Lorenzo
>>  - patch 3-6: split-up as suggested by Bjorn
>>  - patch 8: new
>>  - patch 10: select PCI_DOMAINS from PCI_HOST_GENERIC, rather than
>>    allowing manual choice, as suggested by Lorenzo
>>
>> This primarily enables to unbind the generic PCI host controller without
>> leaving lots of memory leaks behind. A previous proposal patch 5 was
>> rejected because of those issues [1].
>>
>> The fixes have been validated in the Jailhouse setup, where we add and
>> remove a virtual PCI host controller on hypervisor activation/
>> deactivation, with the help of kmemleak.
> 
> by chance I was looking into a memleak in of_pci_get_host_bridge_resources(),
> so I can give you a number of review tags.

Thanks for the reviews and tests! And the pointer for the maintainers to
the conflict around patch 7.

> 
> FWIW the state of unfixably broken https://patchwork.kernel.org/patch/9662893/
> should be changed to obsoleted/deprecated/rejected.

Indeed.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Jingoo Han <jingoohan1@gmail.com>,
	Joao Pinto <Joao.Pinto@synopsys.com>,
	Will Deacon <will.deacon@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH v2 00/10] PCI: leak fixes, removable generic PCI host, assorted stuff
Date: Thu, 3 May 2018 09:52:16 +0200	[thread overview]
Message-ID: <cc97108e-f3db-fc0c-3a88-ced7291be617@siemens.com> (raw)
In-Reply-To: <e15c1cf5-0844-e5f1-d7af-e196207be6d4@mentor.com>

Hey Vladimir,

On 2018-05-03 09:12, Vladimir Zapolskiy wrote:
> Hi Jan,
> 
> On 04/30/2018 08:48 AM, Jan Kiszka wrote:
>> Changes in v2:
>>  - patch 1: commit message reworking as suggested by Lorenzo
>>  - patch 3-6: split-up as suggested by Bjorn
>>  - patch 8: new
>>  - patch 10: select PCI_DOMAINS from PCI_HOST_GENERIC, rather than
>>    allowing manual choice, as suggested by Lorenzo
>>
>> This primarily enables to unbind the generic PCI host controller without
>> leaving lots of memory leaks behind. A previous proposal patch 5 was
>> rejected because of those issues [1].
>>
>> The fixes have been validated in the Jailhouse setup, where we add and
>> remove a virtual PCI host controller on hypervisor activation/
>> deactivation, with the help of kmemleak.
> 
> by chance I was looking into a memleak in of_pci_get_host_bridge_resources(),
> so I can give you a number of review tags.

Thanks for the reviews and tests! And the pointer for the maintainers to
the conflict around patch 7.

> 
> FWIW the state of unfixably broken https://patchwork.kernel.org/patch/9662893/
> should be changed to obsoleted/deprecated/rejected.

Indeed.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: jan.kiszka@siemens.com (Jan Kiszka)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 00/10] PCI: leak fixes, removable generic PCI host, assorted stuff
Date: Thu, 3 May 2018 09:52:16 +0200	[thread overview]
Message-ID: <cc97108e-f3db-fc0c-3a88-ced7291be617@siemens.com> (raw)
In-Reply-To: <e15c1cf5-0844-e5f1-d7af-e196207be6d4@mentor.com>

Hey Vladimir,

On 2018-05-03 09:12, Vladimir Zapolskiy wrote:
> Hi Jan,
> 
> On 04/30/2018 08:48 AM, Jan Kiszka wrote:
>> Changes in v2:
>>  - patch 1: commit message reworking as suggested by Lorenzo
>>  - patch 3-6: split-up as suggested by Bjorn
>>  - patch 8: new
>>  - patch 10: select PCI_DOMAINS from PCI_HOST_GENERIC, rather than
>>    allowing manual choice, as suggested by Lorenzo
>>
>> This primarily enables to unbind the generic PCI host controller without
>> leaving lots of memory leaks behind. A previous proposal patch 5 was
>> rejected because of those issues [1].
>>
>> The fixes have been validated in the Jailhouse setup, where we add and
>> remove a virtual PCI host controller on hypervisor activation/
>> deactivation, with the help of kmemleak.
> 
> by chance I was looking into a memleak in of_pci_get_host_bridge_resources(),
> so I can give you a number of review tags.

Thanks for the reviews and tests! And the pointer for the maintainers to
the conflict around patch 7.

> 
> FWIW the state of unfixably broken https://patchwork.kernel.org/patch/9662893/
> should be changed to obsoleted/deprecated/rejected.

Indeed.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-05-03  7:52 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30  5:48 [PATCH v2 00/10] PCI: leak fixes, removable generic PCI host, assorted stuff Jan Kiszka
2018-04-30  5:48 ` Jan Kiszka
2018-04-30  5:48 ` [PATCH v2 01/10] PCI: Make pci_get_new_domain_nr() static Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-04-30  5:48 ` [PATCH v2 02/10] PCI: Fix memory leak of devm_pci_alloc_host_bridge() Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-04-30  5:48 ` [PATCH v2 03/10] PCI: Factor out __of_pci_get_host_bridge_resources() Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-05-03  7:14   ` Vladimir Zapolskiy
2018-05-03  7:14     ` Vladimir Zapolskiy
2018-04-30  5:48 ` [PATCH v2 04/10] PCI: Add dev parameter to __of_pci_get_host_bridge_resources() Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-05-03  7:14   ` Vladimir Zapolskiy
2018-05-03  7:14     ` Vladimir Zapolskiy
2018-04-30  5:48 ` [PATCH v2 05/10] PCI: Replace pr_*() with dev_*() in __of_pci_get_host_bridge_resources() Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-05-03  7:15   ` Vladimir Zapolskiy
2018-05-03  7:15     ` Vladimir Zapolskiy
2018-05-03  7:15     ` Vladimir Zapolskiy
2018-04-30  5:48 ` [PATCH v2 06/10] PCI: Introduce devm_of_pci_get_host_bridge_resources() Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-05-03  7:15   ` Vladimir Zapolskiy
2018-05-03  7:15     ` Vladimir Zapolskiy
2018-04-30  5:48 ` [PATCH v2 07/10] PCI: Convert of_pci_get_host_bridge_resources() users to devm variant Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-05-03  7:18   ` Vladimir Zapolskiy
2018-05-03  7:18     ` Vladimir Zapolskiy
2018-05-04 16:44     ` Lorenzo Pieralisi
2018-05-04 16:44       ` Lorenzo Pieralisi
2018-05-04 16:44       ` Lorenzo Pieralisi
2018-05-05  7:42       ` Vladimir Zapolskiy
2018-05-05  7:42         ` Vladimir Zapolskiy
2018-05-05  7:42         ` Vladimir Zapolskiy
2018-04-30  5:48 ` [PATCH v2 08/10] PCI: Deprecate of_pci_get_host_bridge_resources() Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-05-02 12:39   ` Christoph Hellwig
2018-05-02 12:39     ` Christoph Hellwig
2018-05-02 12:39     ` Christoph Hellwig
2018-05-03  7:53     ` Jan Kiszka
2018-05-03  7:53       ` Jan Kiszka
2018-05-03  7:53       ` Jan Kiszka
2018-05-08 13:29       ` Bjorn Helgaas
2018-05-08 13:29         ` Bjorn Helgaas
2018-05-08 13:29         ` Bjorn Helgaas
2018-05-09 19:03         ` [PATCH v3 08/10] PCI: Remove of_pci_get_host_bridge_resources() Jan Kiszka
2018-05-09 19:03           ` Jan Kiszka
2018-04-30  5:48 ` [PATCH v2 09/10] PCI: Add support for unbinding the generic PCI host controller Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-04-30  5:48 ` [PATCH v2 10/10] PCI: Enable PCI_DOMAINS along with " Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-04-30  5:48   ` Jan Kiszka
2018-05-03  7:12 ` [PATCH v2 00/10] PCI: leak fixes, removable generic PCI host, assorted stuff Vladimir Zapolskiy
2018-05-03  7:12   ` Vladimir Zapolskiy
2018-05-03  7:12   ` Vladimir Zapolskiy
2018-05-03  7:52   ` Jan Kiszka [this message]
2018-05-03  7:52     ` Jan Kiszka
2018-05-03  7:52     ` Jan Kiszka
2018-05-10 22:51 ` Bjorn Helgaas
2018-05-10 22:51   ` Bjorn Helgaas
2018-05-10 22:51   ` Bjorn Helgaas

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=cc97108e-f3db-fc0c-3a88-ced7291be617@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=bhelgaas@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=vladimir_zapolskiy@mentor.com \
    --cc=will.deacon@arm.com \
    /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.