All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Nicholas Piggin <npiggin@gmail.com>, linux-mm@kvack.org
Cc: linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 0/3] fix vmalloc_to_page for huge vmap mappings
Date: Mon, 24 Jun 2019 11:22:37 +0530	[thread overview]
Message-ID: <f8139999-1624-617a-b7a5-df2846e6e25b@arm.com> (raw)
In-Reply-To: <20190623094446.28722-1-npiggin@gmail.com>

Hello Nicholas,

On 06/23/2019 03:14 PM, Nicholas Piggin wrote:
> This is a change broken out from the huge vmap vmalloc series as
> requested. There is a little bit of dependency juggling across

Thanks for splitting up the previous series and sending this one out.


> trees, but patches are pretty trivial. Ideally if Andrew accepts
> this patch and queues it up for next, then the arch patches would
> be merged through those trees then patch 3 gets sent by Andrew.

Fair enough.

> 
> I've tested this with other powerpc and vmalloc patches, with code
> that explicitly tests vmalloc_to_page on vmalloced memory and
> results look fine.

- Anshuman



WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Nicholas Piggin <npiggin@gmail.com>, linux-mm@kvack.org
Cc: Mark Rutland <mark.rutland@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] fix vmalloc_to_page for huge vmap mappings
Date: Mon, 24 Jun 2019 11:22:37 +0530	[thread overview]
Message-ID: <f8139999-1624-617a-b7a5-df2846e6e25b@arm.com> (raw)
In-Reply-To: <20190623094446.28722-1-npiggin@gmail.com>

Hello Nicholas,

On 06/23/2019 03:14 PM, Nicholas Piggin wrote:
> This is a change broken out from the huge vmap vmalloc series as
> requested. There is a little bit of dependency juggling across

Thanks for splitting up the previous series and sending this one out.


> trees, but patches are pretty trivial. Ideally if Andrew accepts
> this patch and queues it up for next, then the arch patches would
> be merged through those trees then patch 3 gets sent by Andrew.

Fair enough.

> 
> I've tested this with other powerpc and vmalloc patches, with code
> that explicitly tests vmalloc_to_page on vmalloced memory and
> results look fine.

- Anshuman



WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Nicholas Piggin <npiggin@gmail.com>, linux-mm@kvack.org
Cc: Christophe Leroy <christophe.leroy@c-s.fr>,
	Mark Rutland <mark.rutland@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] fix vmalloc_to_page for huge vmap mappings
Date: Mon, 24 Jun 2019 11:22:37 +0530	[thread overview]
Message-ID: <f8139999-1624-617a-b7a5-df2846e6e25b@arm.com> (raw)
In-Reply-To: <20190623094446.28722-1-npiggin@gmail.com>

Hello Nicholas,

On 06/23/2019 03:14 PM, Nicholas Piggin wrote:
> This is a change broken out from the huge vmap vmalloc series as
> requested. There is a little bit of dependency juggling across

Thanks for splitting up the previous series and sending this one out.


> trees, but patches are pretty trivial. Ideally if Andrew accepts
> this patch and queues it up for next, then the arch patches would
> be merged through those trees then patch 3 gets sent by Andrew.

Fair enough.

> 
> I've tested this with other powerpc and vmalloc patches, with code
> that explicitly tests vmalloc_to_page on vmalloced memory and
> results look fine.

- Anshuman



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

  parent reply	other threads:[~2019-06-24  5:52 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  9:44 [PATCH 0/3] fix vmalloc_to_page for huge vmap mappings Nicholas Piggin
2019-06-23  9:44 ` Nicholas Piggin
2019-06-23  9:44 ` Nicholas Piggin
2019-06-23  9:44 ` [PATCH 1/3] arm64: mm: Add p?d_large() definitions Nicholas Piggin
2019-06-23  9:44   ` Nicholas Piggin
2019-06-23  9:44   ` Nicholas Piggin
2019-07-01  9:27   ` Will Deacon
2019-07-01  9:27     ` Will Deacon
2019-07-01  9:27     ` Will Deacon
2019-07-01 10:03     ` Steven Price
2019-07-01 10:03       ` Steven Price
2019-07-01 10:03       ` Steven Price
2019-07-01 10:15       ` Will Deacon
2019-07-01 10:15         ` Will Deacon
2019-07-01 10:15         ` Will Deacon
2019-07-02  3:07         ` Nicholas Piggin
2019-07-02  3:07           ` Nicholas Piggin
2019-07-02  3:07           ` Nicholas Piggin
2019-07-02 10:46           ` Will Deacon
2019-07-02 10:46             ` Will Deacon
2019-07-02 10:46             ` Will Deacon
2019-06-23  9:44 ` [PATCH 2/3] powerpc/64s: Add p?d_large definitions Nicholas Piggin
2019-06-23  9:44   ` Nicholas Piggin
2019-06-23  9:44   ` Nicholas Piggin
2019-06-23  9:44 ` [PATCH 3/3] mm/vmalloc: fix vmalloc_to_page for huge vmap mappings Nicholas Piggin
2019-06-23  9:44   ` Nicholas Piggin
2019-06-23  9:44   ` Nicholas Piggin
2019-06-24  6:52   ` Anshuman Khandual
2019-06-24  6:52     ` Anshuman Khandual
2019-06-24  6:52     ` Anshuman Khandual
2019-06-25  0:20     ` Nicholas Piggin
2019-06-25  0:20       ` Nicholas Piggin
2019-06-25  0:20       ` Nicholas Piggin
2019-06-24  5:52 ` Anshuman Khandual [this message]
2019-06-24  5:52   ` [PATCH 0/3] " Anshuman Khandual
2019-06-24  5:52   ` Anshuman Khandual

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=f8139999-1624-617a-b7a5-df2846e6e25b@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=christophe.leroy@c-s.fr \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=npiggin@gmail.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.