From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: manish.jaggi@caviumnetworks.com,
Julien Grall <julien.grall@linaro.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Vijay Kilari <vijay.kilari@gmail.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Draft F] Xen on ARM vITS Handling
Date: Fri, 12 Jun 2015 14:16:50 +0100 [thread overview]
Message-ID: <1434115010.30003.209.camel@citrix.com> (raw)
In-Reply-To: <557ADA1C.8050700@citrix.com>
On Fri, 2015-06-12 at 09:09 -0400, Julien Grall wrote:
> Hi Ian,
>
> On 12/06/2015 04:52, Ian Campbell wrote:
> > On Fri, 2015-06-12 at 14:07 +0530, Vijay Kilari wrote:
> > So pLPIs must be routed at device assignment time because in the vLPI
> > configuration table trap there is no mapping back to a single pLPI.
>
> I just remembered the exact reason that made use to differ SPI enabling.
I can't parse this sentence, differ how?
> When the device is assigned, the domain VCPUs are still down (even VCPU0).
>
> If we receive an interrupt before the VCPU0 is unpaused, the interrupt
> will be lost. Same if the interrupt is not yet configured (i.e before
> the vITS setup correctly the table) with your proposal.
Is this any different to booting with the ITT not setup?
(SPIs are a slightly different case because they don't need h/w routing)
> This could happen when the device is not quiescent. We had this issue on
> the vexpress at boot time when the network card was trying to send an
> interrupt before DOM0 is setup.
I don't fully understand the issue you are trying to describe, but do
you want to propose a change to the spec?
Ian.
next prev parent reply other threads:[~2015-06-12 13:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 9:40 [Draft F] Xen on ARM vITS Handling Ian Campbell
2015-06-11 12:02 ` Ian Campbell
2015-06-12 8:37 ` Vijay Kilari
2015-06-12 8:52 ` Ian Campbell
2015-06-12 13:09 ` Julien Grall
2015-06-12 13:16 ` Ian Campbell [this message]
2015-06-12 13:32 ` Julien Grall
2015-06-12 14:05 ` Julien Grall
2015-06-12 14:12 ` Ian Campbell
2015-06-12 14:24 ` Ian Campbell
2015-06-12 17:55 ` Julien Grall
2015-06-16 15:10 ` Ian Campbell
2015-06-16 16:14 ` Julien Grall
2015-06-12 12:55 ` Ian Campbell
2015-06-12 13:14 ` Julien Grall
2015-06-12 13:26 ` Ian Campbell
2015-06-16 14:50 ` Vijay Kilari
2015-06-16 15:07 ` Ian Campbell
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=1434115010.30003.209.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=julien.grall@linaro.org \
--cc=manish.jaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=vijay.kilari@gmail.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 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.