From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org, Vijaya.Kumar@caviumnetworks.com,
tim@xen.org, Chen Baozi <baozich@gmail.com>,
stefano.stabellini@citrix.com
Subject: Re: [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC
Date: Thu, 19 Feb 2015 17:48:13 +0000 [thread overview]
Message-ID: <1424368093.30924.154.camel@citrix.com> (raw)
In-Reply-To: <54E61EAE.3030903@linaro.org>
On Thu, 2015-02-19 at 17:34 +0000, Julien Grall wrote:
> On 19/02/15 17:21, Ian Campbell wrote:
> > On Mon, 2015-02-16 at 14:50 +0000, Julien Grall wrote:
> >
> > All applied, thanks.
> >
> >> Most of this patches should be backported to Xen 4.5/Xen 4.5 (see each patch).
> >> Although, the one in GICv2 are not critical.
> >
> > Do you have a handy index of which ones do/don't need backporting to
> > save me trawling through the mails?
>
> The list of GICv2 patches candidate for backporting are: #10, #11, #12, #13.
>
> For GICv3, see my comment below.
>
> > Given the lack of GICv3 hardware on the market today I'm in two minds
> > about the backports to the gicv3 functionality, especially given the
> > number of patches involved and the amount of stuff they change. In
> > practical terms GICv2 support isn't much more than tech-preview in 4.5
> > anyway.
>
> I guess you mean GICv3 for the last one?
Yes.
> I agree that there is no hardware available, but someone may want to use
> the latest Xen release (currently 4.5) on their GICv3 internal board.
For new hardware people should be strongly advised to use the latest
version of Xen, not least because that is where their platform patches
need to be based and because that is where all the bleeding edge h/w
enablement is happening.
> IHMO, GICv3 was not a tech-preview on Xen 4.5. At least we never clearly
> say it was. If it's the case we should write-down on the features list.
Whether we said so or not it is clearly the case, in practical terms,
that the support is not production quality in 4.5. The question is then
whether we are willing to accept large numbers of backports trying to
remedy the situation in a stable release.
I'm willing to try applying the backport once these changes are through
staging, but at the first sign of git cherry-pick asking me to resolve a
non-trivial conflict I'd be inclined to declare that a sign that this
series is too big and/or intrusive to be considering for a backport.
Ian.
next prev parent reply other threads:[~2015-02-19 17:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 14:50 [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC Julien Grall
2015-02-16 14:50 ` [PATCH v3 01/15] xen/arm: vgic-v3: Correctly set GICD_TYPER.IDbits Julien Grall
2015-02-16 14:50 ` [PATCH v3 02/15] xen/arm: vgic-v3: Correctly set GICD_TYPER.CPUNumber Julien Grall
2015-02-16 14:50 ` [PATCH v3 03/15] xen/arm: vgic-v3: Correctly handle GICD_CTLR Julien Grall
2015-02-16 14:50 ` [PATCH v3 04/15] xen/arm: vgic-v3: Correctly handle RAZ/WI registers Julien Grall
2015-02-19 15:55 ` Ian Campbell
2015-02-16 14:50 ` [PATCH v3 05/15] xen/arm: vgic-v3: Correctly implement read into GICR_NSACR Julien Grall
2015-02-16 14:50 ` [PATCH v3 06/15] xen/arm: vgic-v3: Set stride during domain initialization Julien Grall
2015-02-19 15:58 ` Ian Campbell
2015-02-19 16:06 ` Julien Grall
2015-02-16 14:50 ` [PATCH v3 07/15] xen/arm: vgic-v3: Use a struct to describe contiguous rdist regions Julien Grall
2015-02-16 14:50 ` [PATCH v3 08/15] xen/arm: vgic-v3: Emulate correctly the re-distributor Julien Grall
2015-02-19 16:06 ` Ian Campbell
2015-02-16 14:50 ` [PATCH v3 09/15] xen/arm: vgic-v3: Clarify which distributor is used in the common emulation Julien Grall
2015-02-16 14:50 ` [PATCH v3 10/15] xen/arm: vgic-v2: Correctly set GICD_TYPER.CPUNumber Julien Grall
2015-02-16 14:50 ` [PATCH v3 11/15] xen/arm: vgic-v2: Correctly handle RAZ/WI registers Julien Grall
2015-02-19 16:07 ` Ian Campbell
2015-02-16 14:50 ` [PATCH v3 12/15] xen/arm: vgic-v2: Take the lock when writing into GICD_CTLR Julien Grall
2015-02-16 14:50 ` [PATCH v3 13/15] xen/arm: vgic-v2: GICD_I{S, C}PENDR* are only word-accessible Julien Grall
2015-02-16 14:50 ` [PATCH v3 14/15] xen/arm: vgic: Drop iactive, ipend, pendsgi field Julien Grall
2015-02-19 16:09 ` Ian Campbell
2015-02-19 16:15 ` Julien Grall
2015-02-16 14:50 ` [PATCH v3 15/15] xen/arm: gic-v3: Update some comments in the code Julien Grall
2015-02-19 16:09 ` Ian Campbell
2015-02-19 17:21 ` [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC Ian Campbell
2015-02-19 17:34 ` Julien Grall
2015-02-19 17:48 ` Ian Campbell [this message]
2015-02-19 18:01 ` Julien Grall
2015-02-20 10:14 ` Ian Campbell
2015-02-20 10:26 ` Vijay Kilari
2015-02-20 10:44 ` Ian Campbell
2015-02-20 11:15 ` Julien Grall
2015-02-21 5:36 ` Vijay Kilari
2015-02-20 11:22 ` 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=1424368093.30924.154.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=baozich@gmail.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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 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.