From mboxrd@z Thu Jan 1 00:00:00 1970 From: mark.rutland@arm.com (Mark Rutland) Date: Mon, 8 Sep 2014 15:50:48 +0100 Subject: [PATCH 1/2] arm64: psci: respect MIGRATE_INFO_TYPE In-Reply-To: References: <1409915540-20044-1-git-send-email-mark.rutland@arm.com> <1409915540-20044-2-git-send-email-mark.rutland@arm.com> <20140905141345.GF20164@leverpostej> <20140908141434.GJ12081@leverpostej> Message-ID: <20140908145047.GM12081@leverpostej> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Sep 08, 2014 at 03:25:47PM +0100, Ashwin Chaugule wrote: > On 8 September 2014 10:14, Mark Rutland wrote: > > [...] > > > >> >> Guessing there is no way for us to know which CPU the UP TOS is > >> >> running on and only deny hotplug on that CPU? > >> > > >> > In the comment above I mention we can use MIGRATE_INFO_UP_CPU for that. > >> > I started down that route, but the plumbing for it ended up looking a > >> > little crazy so I thought it was better for the moment to have a simple > >> > solution that we can backport to stable. > >> > >> Ah. I faintly recollect experiencing similar craziness when I was > >> adding v0.2 support. > > > > Yeah, it's lot of churny fun with many function prototypes changing > > about. I wasn't too keen on rushing that, though I would like to get > > around to it at some point. > > > >> > No systems with a UP trusted OS (migrateable or not) have hit my radar > >> > yet, and we're currently broken for them anyhow. So for the moment it > >> > didn't seem worthwhile implementing support for those. We can add the > >> > requisite MIGRATE_INFO_UP_CPU and MIGRATE calls in a later series. > >> > >> Ok. > >> > >> Acked-by: Ashwin Chaugule > > > > Thanks. > > > > Does that apply to both patches or just the arm64 one? > > Sorry, just looked at it. Please consider the ACK for both. Thanks for taking a look, it's much appreciated. Mark.