From: Kees Cook <keescook@chromium.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Steve Capper <steve.capper@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] ARM: mm: report both sections from PMD
Date: Fri, 14 Feb 2014 11:31:21 -0800 [thread overview]
Message-ID: <CAGXu5jK6Ro+u1VBsnQvNMZz4+iUZPLSRsd98oBgXCQAx=vW2YA@mail.gmail.com> (raw)
In-Reply-To: <20140214192322.GJ30257@n2100.arm.linux.org.uk>
On Fri, Feb 14, 2014 at 11:23 AM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
>> https://lkml.org/lkml/2014/2/12/662
>
> It's not that simple, because APX in section descriptors doesn't exist
> on pre-v6 ARMs. This needs to be conditional upon the CPU arch.
Ah! Okay, do we need a single #define to describe the expected masks
and values? What should it look like for pre-v6 ARMs?
-Kees
--
Kees Cook
Chrome OS Security
WARNING: multiple messages have this Message-ID (diff)
From: keescook@chromium.org (Kees Cook)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: mm: report both sections from PMD
Date: Fri, 14 Feb 2014 11:31:21 -0800 [thread overview]
Message-ID: <CAGXu5jK6Ro+u1VBsnQvNMZz4+iUZPLSRsd98oBgXCQAx=vW2YA@mail.gmail.com> (raw)
In-Reply-To: <20140214192322.GJ30257@n2100.arm.linux.org.uk>
On Fri, Feb 14, 2014 at 11:23 AM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
>> https://lkml.org/lkml/2014/2/12/662
>
> It's not that simple, because APX in section descriptors doesn't exist
> on pre-v6 ARMs. This needs to be conditional upon the CPU arch.
Ah! Okay, do we need a single #define to describe the expected masks
and values? What should it look like for pre-v6 ARMs?
-Kees
--
Kees Cook
Chrome OS Security
next prev parent reply other threads:[~2014-02-14 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 19:52 [PATCH v3] ARM: mm: report both sections from PMD Kees Cook
2014-02-13 19:52 ` Kees Cook
2014-02-14 10:17 ` Catalin Marinas
2014-02-14 10:17 ` Catalin Marinas
2014-02-14 19:13 ` Kees Cook
2014-02-14 19:13 ` Kees Cook
2014-02-14 19:23 ` Russell King - ARM Linux
2014-02-14 19:23 ` Russell King - ARM Linux
2014-02-14 19:31 ` Kees Cook [this message]
2014-02-14 19:31 ` Kees Cook
2014-02-14 17:05 ` Steve Capper
2014-02-14 17:05 ` Steve Capper
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='CAGXu5jK6Ro+u1VBsnQvNMZz4+iUZPLSRsd98oBgXCQAx=vW2YA@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=steve.capper@linaro.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 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.