public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64 pt dumper changes
Date: Fri, 22 Apr 2016 15:25:18 +0100	[thread overview]
Message-ID: <20160422142518.GM10606@leverpostej> (raw)
In-Reply-To: <CAKv+Gu-vvVp=5J5W=o9rspWGAGujm23mtMXiXbMGpm0svUds7Q@mail.gmail.com>

On Fri, Apr 22, 2016 at 04:15:03PM +0200, Ard Biesheuvel wrote:
> On 22 April 2016 at 16:11, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > Hi Ard,
> >
> > On Mon, Feb 22, 2016 at 11:00:36AM +0100, Ard Biesheuvel wrote:
> >> This series updates the kernel page table dumper to:
> >> - not initialize the vmemmap region markers dynamically
> >> - show region boundaries for the kasan shadow region
> >> - include the UEFI runtime services mappings
> >>
> >> Ard Biesheuvel (3):
> >>   arm64: ptdump: use static initializers for vmemmap region boundaries
> >>   arm64: ptdump: add region marker for kasan shadow region
> >>   arm64: ptdump: include UEFI runtime service mappings
> >>
> >>  arch/arm64/mm/dump.c               | 58 ++++++++------------
> >>  drivers/firmware/efi/arm-runtime.c |  2 +-
> >>  2 files changed, 24 insertions(+), 36 deletions(-)
> >
> > What's the plan with these patches? They no longer apply cleanly on top
> > of arm64 for-next/core.
> >
> 
> I will respin #1 and #2. Regarding patch #3, I think Mark wanted a
> more flexible approach?

My complaint was with placing the EFI table dump in the kernel table
dump, as the EFI page tables are distinct, and that VA range is shared
by other tables we map from time-to-time, e.g. the idmap.

So I would like to see the EFI tables exposed by a separate file.

I had patches [1] which librify the existing code and do just that, but
I haven't had the time to rebase and rework those. If you have the time,
feel free to pick that up!

Thanks,
Mark.

[1] https://git.kernel.org/cgit/linux/kernel/git/mark/linux.git/log/?h=arm64/ptdump/librify

      reply	other threads:[~2016-04-22 14:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 10:00 [PATCH 0/3] arm64 pt dumper changes Ard Biesheuvel
2016-02-22 10:00 ` [PATCH 1/3] arm64: ptdump: use static initializers for vmemmap region boundaries Ard Biesheuvel
2016-02-22 11:33   ` Mark Rutland
2016-02-22 19:37     ` Laura Abbott
2016-02-22 10:00 ` [PATCH 2/3] arm64: ptdump: add region marker for kasan shadow region Ard Biesheuvel
2016-02-22 11:33   ` Mark Rutland
2016-02-22 10:00 ` [PATCH 3/3] arm64: ptdump: include UEFI runtime service mappings Ard Biesheuvel
2016-02-22 11:29   ` Mark Rutland
2016-02-22 11:51     ` Ard Biesheuvel
2016-02-22 19:04       ` Kees Cook
2016-04-22 14:11 ` [PATCH 0/3] arm64 pt dumper changes Catalin Marinas
2016-04-22 14:15   ` Ard Biesheuvel
2016-04-22 14:25     ` Mark Rutland [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=20160422142518.GM10606@leverpostej \
    --to=mark.rutland@arm.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