xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 2/3] xen/arm: vgic-v3: Correctly retrieve the vCPU associated to a re-distributor
Date: Tue, 29 Sep 2015 13:28:44 +0100	[thread overview]
Message-ID: <560A83FC.2080908@citrix.com> (raw)
In-Reply-To: <5FC3163CFD30C246ABAA99954A238FA81728A6F4@lhreml504-mbs>

On 29/09/15 13:24, Shameerali Kolothum Thodi wrote:
> 
> 
>> -----Original Message-----
>> From: Julien Grall [mailto:julien.grall@citrix.com]
>> Sent: 28 September 2015 21:32
>> To: xen-devel@lists.xenproject.org
>> Cc: ian.campbell@citrix.com; stefano.stabellini@eu.citrix.com; Julien
>> Grall; Shameerali Kolothum Thodi; Wei Liu
>> Subject: [PATCH 2/3] xen/arm: vgic-v3: Correctly retrieve the vCPU
>> associated to a re-distributor
>>
>> When the guest is accessing the re-distributor, Xen retrieves the base
>> of the re-distributor using a mask based on the stride.
>>
> ....
>  
>>     with multiple bit set [1]. Although, we don't support such platform
>>     right now. So I would rather defer this change to Xen 4.6.1 and
>>     avoid possible downside/bug in this patch.
>>
>>     Shamaeerali, I've only tested quickly on the foundation model. Can
>>     you give a try on your platform to check if it fixes DOM0 boot?
> 
> 
> I tried and it fixes the issue on our platform :). 

Great, thank you for testing! Can I add your Tested-by?

> (I applied only the first two patches in the series).

The last one is only a clean up so it's fine.

>>     [1] http://lists.xen.org/archives/html/xen-devel/2015-
>> 09/msg03372.html
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 


-- 
Julien Grall

  reply	other threads:[~2015-09-29 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 20:31 [PATCH 0/3] xen/arm: vgic-v3: Correctly retrieved the vCPU associated to a re-distributor Julien Grall
2015-09-28 20:31 ` [PATCH 1/3] xen/arm: io: Extend write/read handler to pass private data Julien Grall
2015-09-29 13:50   ` Ian Campbell
2015-09-28 20:31 ` [PATCH 2/3] xen/arm: vgic-v3: Correctly retrieve the vCPU associated to a re-distributor Julien Grall
2015-09-29  9:46   ` Wei Liu
2015-09-29 12:24   ` Shameerali Kolothum Thodi
2015-09-29 12:28     ` Julien Grall [this message]
2015-09-29 13:56   ` Ian Campbell
2015-09-29 14:15     ` Julien Grall
2015-09-29 14:28       ` Ian Campbell
2015-09-28 20:31 ` [PATCH 3/3] xen/arm: io: Shorten the name of the fields and clean up Julien Grall
2015-09-29 13:58   ` Ian Campbell
2015-09-28 20:40 ` [PATCH 0/3] xen/arm: vgic-v3: Correctly retrieved the vCPU associated to a re-distributor Julien Grall

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=560A83FC.2080908@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).