diff for duplicates of <20141006112640.GF24686@leverpostej> diff --git a/a/1.txt b/N1/1.txt index 0fdbe7b..45900c1 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Mon, Oct 06, 2014 at 06:14:36AM +0100, Ganapatrao Kulkarni wrote: > Hi Mark, > -> On Fri, Oct 3, 2014 at 5:43 PM, Mark Rutland <mark.rutland@arm.com> wrote: +> On Fri, Oct 3, 2014 at 5:43 PM, Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote: > > On Thu, Sep 25, 2014 at 10:03:59AM +0100, Ganapatrao Kulkarni wrote: > >> Adding numa support for arm64 based platforms. > >> This version creates numa mapping by parsing the dt table. @@ -121,9 +121,9 @@ here -- the function has no need to care about the value of numa_off. > >> + if (type == NULL) { > >> + /* > >> + * The longtrail doesn't have a device_type on the -> >> + * /memory node, so look for the node called /memory at 0. +> >> + * /memory node, so look for the node called /memory@0. > >> + */ -> >> + if (depth != 1 || strcmp(uname, "memory at 0") != 0) +> >> + if (depth != 1 || strcmp(uname, "memory@0") != 0) > >> + return 0; > > > > This has no place on arm64. @@ -133,7 +133,7 @@ here -- the function has no need to care about the value of numa_off. I meant the longtrail workaround, hence my comments on that below. > > We limited to longtrail workaround in the core memory parsing to PPC32 -> > only in commit b44aa25d20e2ef6b (of: Handle memory at 0 node on PPC32 +> > only in commit b44aa25d20e2ef6b (of: Handle memory@0 node on PPC32 > > only). This code doesn't need it enabled ever. > > > > Are you booting using UEFI? This isn't going to work when the memory map @@ -150,3 +150,7 @@ the EFI memory map is used, so this is just another configuration that your binding has to consider. Mark. +-- +To unsubscribe from this list: send the line "unsubscribe devicetree" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 09ab289..6361f2d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,16 +2,28 @@ "ref\01411635840-24038-5-git-send-email-ganapatrao.kulkarni@caviumnetworks.com\0" "ref\020141003121343.GG26643@leverpostej\0" "ref\0CAFpQJXVJtn=PTYTd5icHhfYxsQnEzUP+w9kXXDJSs-M=eGNWVw@mail.gmail.com\0" - "From\0mark.rutland@arm.com (Mark Rutland)\0" - "Subject\0[RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms.\0" + "ref\0CAFpQJXVJtn=PTYTd5icHhfYxsQnEzUP+w9kXXDJSs-M=eGNWVw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0" + "From\0Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>\0" + "Subject\0Re: [RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms.\0" "Date\0Mon, 6 Oct 2014 12:26:40 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Ganapatrao Kulkarni <gpkulkarni-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0" + "Cc\0Ganapatrao Kulkarni <ganapatrao.kulkarni-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>" + Catalin Marinas <Catalin.Marinas-5wv7dgnIgG8@public.gmane.org> + Will Deacon <Will.Deacon-5wv7dgnIgG8@public.gmane.org> + grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> + robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org> + leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + roy.franz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + " msalter-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org\0" "\00:1\0" "b\0" "On Mon, Oct 06, 2014 at 06:14:36AM +0100, Ganapatrao Kulkarni wrote:\n" "> Hi Mark,\n" "> \n" - "> On Fri, Oct 3, 2014 at 5:43 PM, Mark Rutland <mark.rutland@arm.com> wrote:\n" + "> On Fri, Oct 3, 2014 at 5:43 PM, Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote:\n" "> > On Thu, Sep 25, 2014 at 10:03:59AM +0100, Ganapatrao Kulkarni wrote:\n" "> >> Adding numa support for arm64 based platforms.\n" "> >> This version creates numa mapping by parsing the dt table.\n" @@ -131,9 +143,9 @@ "> >> + if (type == NULL) {\n" "> >> + /*\n" "> >> + * The longtrail doesn't have a device_type on the\n" - "> >> + * /memory node, so look for the node called /memory at 0.\n" + "> >> + * /memory node, so look for the node called /memory@0.\n" "> >> + */\n" - "> >> + if (depth != 1 || strcmp(uname, \"memory at 0\") != 0)\n" + "> >> + if (depth != 1 || strcmp(uname, \"memory@0\") != 0)\n" "> >> + return 0;\n" "> >\n" "> > This has no place on arm64.\n" @@ -143,7 +155,7 @@ "I meant the longtrail workaround, hence my comments on that below.\n" "\n" "> > We limited to longtrail workaround in the core memory parsing to PPC32\n" - "> > only in commit b44aa25d20e2ef6b (of: Handle memory at 0 node on PPC32\n" + "> > only in commit b44aa25d20e2ef6b (of: Handle memory@0 node on PPC32\n" "> > only). This code doesn't need it enabled ever.\n" "> >\n" "> > Are you booting using UEFI? This isn't going to work when the memory map\n" @@ -159,6 +171,10 @@ "the EFI memory map is used, so this is just another configuration that\n" "your binding has to consider.\n" "\n" - Mark. + "Mark.\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -0b23bb0fd7d6767919332f267c949cebd57dbbc371ee2def9455ca4e97e6830e +3bf43515f0499cb5cf6214a802232ff1725736b948cf5e2f1f115dfc7d343c7f
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.