public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kani, Toshi" <toshi.kani@hpe.com>
To: "cpandya@codeaurora.org" <cpandya@codeaurora.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"arnd@arndb.de" <arnd@arndb.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"takahiro.akashi@linaro.org" <takahiro.akashi@linaro.org>,
	"james.morse@arm.com" <james.morse@arm.com>,
	"kristina.martsenko@arm.com" <kristina.martsenko@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v1 0/4] Fix issues with huge mapping in ioremap
Date: Wed, 14 Mar 2018 14:38:00 +0000	[thread overview]
Message-ID: <1521038277.2693.131.camel@hpe.com> (raw)
In-Reply-To: <1521017305-28518-1-git-send-email-cpandya@codeaurora.org>

On Wed, 2018-03-14 at 14:18 +0530, Chintan Pandya wrote:
> Note: I was working on these patches for quite sometime
> and realized that Toshi Kani has shared some patches
> addressing the same isssue with subject
> "[PATCH 0/2] fix memory leak / panic in ioremap huge pages".
> I've taken slightly different approach here, so sending
> to the list, finally.

Hi Chintan,

Do you have any issue in my patchset?  If so, can you please comment on
them?  It complicates the thing when you send a different approach
without telling why a different approach is needed.  Your approach
purges TLB after updating pmd/pud, which I think is broken.  Can you
work on top of my patchset and properly implement pXd_free_pte_page()
for arm64?  I will send out my v2 today.
  
Thanks,
-Toshi

  parent reply	other threads:[~2018-03-14 14:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  8:48 [PATCH v1 0/4] Fix issues with huge mapping in ioremap Chintan Pandya
2018-03-14  8:48 ` Chintan Pandya
2018-03-14  8:48 ` [PATCH v1 1/4] asm/tlbflush: Add flush_tlb_pgtable() for ARM64 Chintan Pandya
2018-03-14  8:48   ` Chintan Pandya
2018-03-16  8:26   ` kbuild test robot
2018-03-16  8:26     ` kbuild test robot
2018-03-14  8:48 ` [PATCH v1 2/4] ioremap: Invalidate TLB after huge mappings Chintan Pandya
2018-03-14  8:48   ` Chintan Pandya
2018-03-14 10:48   ` Mark Rutland
2018-03-14 10:48     ` Mark Rutland
2018-03-14 11:20     ` Chintan Pandya
2018-03-14 11:20       ` Chintan Pandya
2018-03-14 11:48       ` Mark Rutland
2018-03-14 11:48         ` Mark Rutland
2018-03-14  8:48 ` [PATCH v1 3/4] arm64: Fix the page leak in pud/pmd_set_huge Chintan Pandya
2018-03-14  8:48   ` Chintan Pandya
2018-03-14 10:35   ` Marc Zyngier
2018-03-14 10:35     ` Marc Zyngier
2018-03-14 10:53   ` Mark Rutland
2018-03-14 10:53     ` Mark Rutland
2018-03-14 11:27     ` Chintan Pandya
2018-03-14 11:27       ` Chintan Pandya
2018-03-14 11:50       ` Mark Rutland
2018-03-14 11:50         ` Mark Rutland
2018-03-16 14:50   ` kbuild test robot
2018-03-16 14:50     ` kbuild test robot
2018-03-14  8:48 ` [PATCH v1 4/4] Revert "arm64: Enforce BBM for huge IO/VMAP mappings" Chintan Pandya
2018-03-14  8:48   ` Chintan Pandya
2018-03-14 10:46   ` Marc Zyngier
2018-03-14 10:46     ` Marc Zyngier
2018-03-14 11:32     ` Chintan Pandya
2018-03-14 11:32       ` Chintan Pandya
2018-03-14 14:38 ` Kani, Toshi [this message]
2018-03-14 14:38   ` [PATCH v1 0/4] Fix issues with huge mapping in ioremap Kani, Toshi
2018-03-15  7:17   ` Chintan Pandya
2018-03-15  7:17     ` Chintan Pandya
2018-03-15 14:38     ` Kani, Toshi
2018-03-15 14:38       ` Kani, Toshi

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=1521038277.2693.131.camel@hpe.com \
    --to=toshi.kani@hpe.com \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=cpandya@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.morse@arm.com \
    --cc=kristina.martsenko@arm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox