From: Mark Rutland <mark.rutland@arm.com>
To: Mark Salter <msalter@redhat.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Date: Tue, 28 Jul 2015 16:14:47 +0100 [thread overview]
Message-ID: <20150728151447.GF15213@leverpostej> (raw)
In-Reply-To: <1438096069.14248.13.camel@redhat.com>
> > > arch/arm64/kernel/setup.c | 55
> > > +++++++++++++++++++++++++++++++++++++
> > > include/asm-generic/early_ioremap.h | 6 ++++
> > > mm/early_ioremap.c | 22 +++++++++++++++
> > > 3 files changed, 83 insertions(+)
> >
> > Any reason for not moving x86 over to the new generic version?
>
> I have a patch to do that but I'm not sure how to contrive a
> testcase to exercise it.
The easiest option might be to hack up KVM tool [1] to load a kernel an
initrd at suitable addresses.
Otherwise I'm sure someone else must have a way of exercising this.
Mark.
[1] https://git.kernel.org/cgit/linux/kernel/git/will/kvmtool.git/
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Date: Tue, 28 Jul 2015 16:14:47 +0100 [thread overview]
Message-ID: <20150728151447.GF15213@leverpostej> (raw)
In-Reply-To: <1438096069.14248.13.camel@redhat.com>
> > > arch/arm64/kernel/setup.c | 55
> > > +++++++++++++++++++++++++++++++++++++
> > > include/asm-generic/early_ioremap.h | 6 ++++
> > > mm/early_ioremap.c | 22 +++++++++++++++
> > > 3 files changed, 83 insertions(+)
> >
> > Any reason for not moving x86 over to the new generic version?
>
> I have a patch to do that but I'm not sure how to contrive a
> testcase to exercise it.
The easiest option might be to hack up KVM tool [1] to load a kernel an
initrd at suitable addresses.
Otherwise I'm sure someone else must have a way of exercising this.
Mark.
[1] https://git.kernel.org/cgit/linux/kernel/git/will/kvmtool.git/
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Mark Salter <msalter@redhat.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Date: Tue, 28 Jul 2015 16:14:47 +0100 [thread overview]
Message-ID: <20150728151447.GF15213@leverpostej> (raw)
In-Reply-To: <1438096069.14248.13.camel@redhat.com>
> > > arch/arm64/kernel/setup.c | 55
> > > +++++++++++++++++++++++++++++++++++++
> > > include/asm-generic/early_ioremap.h | 6 ++++
> > > mm/early_ioremap.c | 22 +++++++++++++++
> > > 3 files changed, 83 insertions(+)
> >
> > Any reason for not moving x86 over to the new generic version?
>
> I have a patch to do that but I'm not sure how to contrive a
> testcase to exercise it.
The easiest option might be to hack up KVM tool [1] to load a kernel an
initrd at suitable addresses.
Otherwise I'm sure someone else must have a way of exercising this.
Mark.
[1] https://git.kernel.org/cgit/linux/kernel/git/will/kvmtool.git/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-07-28 15:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 14:32 [PATCH 0/2] arm64: support initrd outside of mapped RAM Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` [PATCH 1/2] mm: add utility for early copy from unmapped ram Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` [PATCH 2/2] arm64: support initrd outside kernel linear map Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:59 ` [PATCH 0/2] arm64: support initrd outside of mapped RAM Mark Rutland
2015-07-28 14:59 ` Mark Rutland
2015-07-28 14:59 ` Mark Rutland
2015-07-28 15:07 ` Mark Salter
2015-07-28 15:07 ` Mark Salter
2015-07-28 15:07 ` Mark Salter
2015-07-28 15:14 ` Mark Rutland [this message]
2015-07-28 15:14 ` Mark Rutland
2015-07-28 15:14 ` Mark Rutland
2015-07-29 9:20 ` Jon Medhurst (Tixy)
2015-07-29 9:20 ` Jon Medhurst (Tixy)
2015-07-29 9:20 ` Jon Medhurst (Tixy)
2015-07-29 9:25 ` Mark Rutland
2015-07-29 9:25 ` Mark Rutland
2015-07-29 9:25 ` Mark Rutland
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=20150728151447.GF15213@leverpostej \
--to=mark.rutland@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=msalter@redhat.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.