linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ashwin.chaugule@linaro.org (Ashwin Chaugule)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: psci: respect MIGRATE_INFO_TYPE
Date: Mon, 8 Sep 2014 10:25:47 -0400	[thread overview]
Message-ID: <CAJ5Y-eZVus1TjEXSoq9edJbYYTneH0jm=Tbx0LfVQG8ZSeJDEg@mail.gmail.com> (raw)
In-Reply-To: <20140908141434.GJ12081@leverpostej>

On 8 September 2014 10:14, Mark Rutland <mark.rutland@arm.com> 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 <ashwin.chaugule@linaro.org>
>
> Thanks.
>
> Does that apply to both patches or just the arm64 one?

Sorry, just looked at it. Please consider the ACK for both.

Thanks,
Ashwin

  reply	other threads:[~2014-09-08 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1409915540-20044-1-git-send-email-mark.rutland@arm.com>
     [not found] ` <1409915540-20044-2-git-send-email-mark.rutland@arm.com>
     [not found]   ` <CAJ5Y-eZqWsLT1ERWsdzCQASgzCfFTgn6fCBCpc7ceMoU2ONkNA@mail.gmail.com>
     [not found]     ` <20140905141345.GF20164@leverpostej>
2014-09-05 18:22       ` [PATCH 1/2] arm64: psci: respect MIGRATE_INFO_TYPE Ashwin Chaugule
2014-09-08 14:14         ` Mark Rutland
2014-09-08 14:25           ` Ashwin Chaugule [this message]
2014-09-08 14:50             ` Mark Rutland
2014-09-05 11:22 [PATCH 0/2] PSCI: don't call CPU_OFF when it might fail Mark Rutland
2014-09-05 11:22 ` [PATCH 1/2] arm64: psci: respect MIGRATE_INFO_TYPE Mark Rutland
2014-09-05 11:58   ` Sergei Shtylyov
2014-09-05 12:39     ` 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='CAJ5Y-eZVus1TjEXSoq9edJbYYTneH0jm=Tbx0LfVQG8ZSeJDEg@mail.gmail.com' \
    --to=ashwin.chaugule@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).