linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: toshi.kani@hpe.com (Kani, Toshi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/4] Fix issues with huge mapping in ioremap
Date: Thu, 15 Mar 2018 14:38:27 +0000	[thread overview]
Message-ID: <1521124702.2693.145.camel@hpe.com> (raw)
In-Reply-To: <9954bd28-0457-b80e-8af7-6259b63533f2@codeaurora.org>

On Thu, 2018-03-15 at 12:47 +0530, Chintan Pandya wrote:
> 
> On 3/14/2018 8:08 PM, Kani, Toshi wrote:
> > 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,
> 
> Hi Toshi
> > 
> > Do you have any issue in my patchset?  If so, can you please comment on
> 
> Not functional issues. But I didn't see issues you mentioned in your
> commit text being solved for ARM64 in your patches. It is just being
> masked which they were already by Will's patch. In my approach, end
> goal was to get benefits of huge mapping back for ARM64.

Right, my patchset does not implement the fix for arm64.  The stub
version is only a workaround and is meant to be replaced by the fix.

> > them?  It complicates the thing when you send a different approach
> > without telling why a different approach is needed.  Your approach
> 
> See my reply above. I just had my original patches and I sent it.
> 
> > purges TLB after updating pmd/pud, which I think is broken.  Can you
> 
> Yes, they are broken. I understood the issues after Mark and Marc's
> review comments.
> 
> > work on top of my patchset and properly implement pXd_free_pte_page()
> 
> I have realized that if I address Mark's comments, my new patch will
> look similar to what you have done. So, I will work on top of your
> patches.

Sounds great.

Thanks,
-Toshi

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

Thread overview: 19+ 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 ` [PATCH v1 1/4] asm/tlbflush: Add flush_tlb_pgtable() for ARM64 Chintan Pandya
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 10:48   ` Mark Rutland
2018-03-14 11:20     ` Chintan Pandya
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 10:35   ` Marc Zyngier
2018-03-14 10:53   ` Mark Rutland
2018-03-14 11:27     ` Chintan Pandya
2018-03-14 11:50       ` Mark Rutland
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 10:46   ` Marc Zyngier
2018-03-14 11:32     ` Chintan Pandya
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 14:38     ` Kani, Toshi [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=1521124702.2693.145.camel@hpe.com \
    --to=toshi.kani@hpe.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).