From: Julien Grall <julien.grall@citrix.com>
To: Julien Grall <julien.grall@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
"xen-devel@lists.xen.org" <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 D] Xen on ARM vITS Handling
Date: Thu, 4 Jun 2015 20:08:14 +0100 [thread overview]
Message-ID: <5570A21E.1080607@citrix.com> (raw)
In-Reply-To: <557090F6.8030808@citrix.com>
On 04/06/2015 18:55, Julien Grall wrote:
> After reading this draft, I think we can avoid to browse the Device
> Table and the ITT. As said on the previous paragraph, the pending_irq
> structure is linked to an irq_desc. In your proposal, you suggested to
> store the its_device in the irq_guest (part of irq_desc). If we make
> usage of pending_irq->desc to store the physical descriptor, we can have
> a mapping vLPI <=> pLPI. Therefore, this would resolve UI1 and AFAICT,
> the memory usage would be the same in Xen of the ITT/Device base solution.
BTW, I will suggest a pseudo-code based on your draft tomorrow. It may
be easier to understand.
--
Julien Grall
next prev parent reply other threads:[~2015-06-04 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 13:54 [Draft D] Xen on ARM vITS Handling Ian Campbell
2015-06-04 17:55 ` Julien Grall
2015-06-04 19:08 ` Julien Grall [this message]
2015-06-05 10:24 ` Ian Campbell
2015-06-05 12:15 ` Julien Grall
2015-06-05 13:20 ` Ian Campbell
2015-06-05 14:12 ` Julien Grall
2015-06-05 6:07 ` Vijay Kilari
2015-06-05 9:16 ` Ian Campbell
2015-06-05 9:28 ` Julien Grall
2015-06-05 9:51 ` Ian Campbell
2015-06-05 9:49 ` Ian Campbell
2015-06-05 12:41 ` Vijay Kilari
2015-06-05 13:28 ` Ian Campbell
2015-06-05 15:55 ` Vijay Kilari
2015-06-05 16:38 ` Ian Campbell
2015-06-05 17:11 ` Vijay Kilari
2015-06-08 9:59 ` 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=5570A21E.1080607@citrix.com \
--to=julien.grall@citrix.com \
--cc=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.