All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: manish.jaggi@caviumnetworks.com,
	Julien Grall <julien.grall@linaro.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Vijay Kilari <vijay.kilari@gmail.com>
Subject: Re: [Draft E] Xen on ARM vITS Handling
Date: Wed, 10 Jun 2015 10:03:25 +0100	[thread overview]
Message-ID: <1433927005.30003.8.camel@citrix.com> (raw)
In-Reply-To: <1433864565.7108.565.camel@citrix.com>

On Tue, 2015-06-09 at 16:42 +0100, Ian Campbell wrote:
> Draft E follows. Also at:
> http://xenbits.xen.org/people/ianc/vits/draftE.{pdf,html}
> 
> The major change here arises from the realisation that it is not
> possible to associate a vPLI with a single pLPI, which has ramifications
> for the management of enabling/disabling pLPIs and the handling of
> spurious pLPIs which we are now expecting to see as a consequence. On
> the plus side this ended up taking care of UI1 and there are now no
> major stumbling blocks that I can see.

One thing which I realised is not covered is where the `struct
pending_irq` for vLPIs comes from. I propose to make that a dynamically
allocated array (allocated on domain construction) in `struct domain`
alongside the similar array for SPIs

This avoids the need to manage allocations and tree insertions etc
during command processing.

I won't send a draft F for just that though.

Ian.

  parent reply	other threads:[~2015-06-10  9:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 15:42 [Draft E] Xen on ARM vITS Handling Ian Campbell
2015-06-09 15:50 ` Manish Jaggi
2015-06-10  9:03 ` Ian Campbell [this message]
2015-06-10  9:18 ` Ian Campbell
2015-06-10 13:37   ` Julien Grall
2015-06-10 14:30     ` Ian Campbell
2015-06-10 14:40 ` Julien Grall
2015-06-10 14:45   ` Ian Campbell
2015-06-10 14:52     ` Julien Grall
2015-06-10 15:52       ` 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=1433927005.30003.8.camel@citrix.com \
    --to=ian.campbell@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.