From: Mark Rutland <mark.rutland@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>,
"Kani, Toshimitsu" <toshi.kani@hpe.com>,
"Knippers, Linda" <linda.knippers@hpe.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>
Subject: Re: arm64/efi handling of persistent memory
Date: Fri, 18 Dec 2015 11:52:24 +0000 [thread overview]
Message-ID: <20151218115224.GE29219@leverpostej> (raw)
In-Reply-To: <20151218110651.GL25034@bivouac.eciton.net>
On Fri, Dec 18, 2015 at 11:06:51AM +0000, Leif Lindholm wrote:
> On Fri, Dec 18, 2015 at 01:33:25AM +0000, Elliott, Robert (Persistent Memory) wrote:
> > Similar to the questions about the arm64 efi boot stub
> > handing persistent memory, some of the arm64 kernel code
> > looks fishy.
[...]
> > 2. is_reserve_region() treating EFI_PERSISTENT_MEMORY the same
> > as EFI_CONVENTIONAL_MEMORY looks wrong.
>
> Yeah... That one was introduced by
> ad5fb870c486 ("e820, efi: add ACPI 6.0 persistent memory types")
> without any ACKs from ARM people :/
Do we need to do anythign to avoid his kind of thing in future? e.g. a
MAINTAINERS patch for the ARM EFI bits?
Or do we just need to pay attention to linux-efi?
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64/efi handling of persistent memory
Date: Fri, 18 Dec 2015 11:52:24 +0000 [thread overview]
Message-ID: <20151218115224.GE29219@leverpostej> (raw)
In-Reply-To: <20151218110651.GL25034@bivouac.eciton.net>
On Fri, Dec 18, 2015 at 11:06:51AM +0000, Leif Lindholm wrote:
> On Fri, Dec 18, 2015 at 01:33:25AM +0000, Elliott, Robert (Persistent Memory) wrote:
> > Similar to the questions about the arm64 efi boot stub
> > handing persistent memory, some of the arm64 kernel code
> > looks fishy.
[...]
> > 2. is_reserve_region() treating EFI_PERSISTENT_MEMORY the same
> > as EFI_CONVENTIONAL_MEMORY looks wrong.
>
> Yeah... That one was introduced by
> ad5fb870c486 ("e820, efi: add ACPI 6.0 persistent memory types")
> without any ACKs from ARM people :/
Do we need to do anythign to avoid his kind of thing in future? e.g. a
MAINTAINERS patch for the ARM EFI bits?
Or do we just need to pay attention to linux-efi?
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>,
"Kani, Toshimitsu" <toshi.kani@hpe.com>,
"Knippers, Linda" <linda.knippers@hpe.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>
Subject: Re: arm64/efi handling of persistent memory
Date: Fri, 18 Dec 2015 11:52:24 +0000 [thread overview]
Message-ID: <20151218115224.GE29219@leverpostej> (raw)
In-Reply-To: <20151218110651.GL25034@bivouac.eciton.net>
On Fri, Dec 18, 2015 at 11:06:51AM +0000, Leif Lindholm wrote:
> On Fri, Dec 18, 2015 at 01:33:25AM +0000, Elliott, Robert (Persistent Memory) wrote:
> > Similar to the questions about the arm64 efi boot stub
> > handing persistent memory, some of the arm64 kernel code
> > looks fishy.
[...]
> > 2. is_reserve_region() treating EFI_PERSISTENT_MEMORY the same
> > as EFI_CONVENTIONAL_MEMORY looks wrong.
>
> Yeah... That one was introduced by
> ad5fb870c486 ("e820, efi: add ACPI 6.0 persistent memory types")
> without any ACKs from ARM people :/
Do we need to do anythign to avoid his kind of thing in future? e.g. a
MAINTAINERS patch for the ARM EFI bits?
Or do we just need to pay attention to linux-efi?
Mark.
next prev parent reply other threads:[~2015-12-18 11:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 1:33 arm64/efi handling of persistent memory Elliott, Robert (Persistent Memory)
2015-12-18 1:33 ` Elliott, Robert (Persistent Memory)
2015-12-18 1:33 ` Elliott, Robert (Persistent Memory)
2015-12-18 11:06 ` Leif Lindholm
2015-12-18 11:06 ` Leif Lindholm
2015-12-18 11:06 ` Leif Lindholm
2015-12-18 11:45 ` Mark Rutland
2015-12-18 11:45 ` Mark Rutland
2015-12-18 11:45 ` Mark Rutland
2015-12-18 13:07 ` Ard Biesheuvel
2015-12-18 13:07 ` Ard Biesheuvel
2015-12-18 13:07 ` Ard Biesheuvel
2016-01-20 14:23 ` Mark Rutland
2016-01-20 14:23 ` Mark Rutland
2016-01-20 14:23 ` Mark Rutland
2015-12-18 11:52 ` Mark Rutland [this message]
2015-12-18 11:52 ` Mark Rutland
2015-12-18 11:52 ` Mark Rutland
2015-12-18 12:11 ` Leif Lindholm
2015-12-18 12:11 ` Leif Lindholm
2015-12-18 12:11 ` Leif Lindholm
2015-12-18 13:27 ` Matt Fleming
2015-12-18 13:27 ` Matt Fleming
2015-12-18 13:27 ` Matt Fleming
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=20151218115224.GE29219@leverpostej \
--to=mark.rutland@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=leif.lindholm@linaro.org \
--cc=linda.knippers@hpe.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=matt@codeblueprint.co.uk \
--cc=toshi.kani@hpe.com \
--cc=will.deacon@arm.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.