xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@de.bosch.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH v2] xen/arm: domain_build: Add PSCI 1.0 compatibility
Date: Fri, 22 Apr 2016 18:21:44 +0100	[thread overview]
Message-ID: <571A5DA8.3010607@arm.com> (raw)
In-Reply-To: <571A465D.8080401@arm.com>



On 22/04/16 16:42, Julien Grall wrote:
> (CC Wei for release-ack)
>
> Hello Dirk,
>
> On 21/04/16 06:33, Dirk Behme wrote:
>> Xen needs to blacklist any PSCI node as it will be recreated for DOM0.
>> Up to now, this was done only for arm,psci and arm,psci-0.2 compatible
>> nodes. Add PSCI 1.0 compatibility to make device tree nodes with
>>
>> compatible = "arm,psci-1.0";
>>
>> blacklisted, too
>>
>> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
>
> Acked-by: Julien Grall <julien.grall@arm.com>
>
> I think this is a bug fix for Xen 4.7. The impact is very limited and
> will help to boot Xen on platform when only PSCI 1.0 is supported.
>
> The patch should also be backported to Xen 4.6 where the support of PSCI
> 1.0 has been added for the first time.

Hmmm, I messed up my tig command line. The support of PSCI v1.0 is only 
in Xen 4.7. So there is no need to backport this patch.

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-04-22 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21  5:33 [PATCH v2] xen/arm: domain_build: Add PSCI 1.0 compatibility Dirk Behme
2016-04-22 15:42 ` Julien Grall
2016-04-22 15:49   ` Wei Liu
2016-04-22 17:28     ` Stefano Stabellini
2016-04-22 17:21   ` Julien Grall [this message]

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=571A5DA8.3010607@arm.com \
    --to=julien.grall@arm.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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).