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

On Fri, 2015-06-05 at 21:25 +0530, Vijay Kilari wrote:
> Let xen mark those phantom devices added using MAPD as dummy and
> just emulate and does not translate ITS commands for these devices.

But we think guests might use this mechanism to drive completion
(instead of polling), so we have to translate INT commands for such
devices, don't we? Otherwise such guests won't work.

> >> So deviceid of any MAPD command for all the guests should be have been
> >> within pre-identified list.
> >
> > I don't think that is true for a domU, not necessarily for a dom0 given
> > that any device id can be used with INT.
> 
>    If the INT command is with valid device (not phantom) then Xen can translate
> and send to ITS hardware

That is not what this design says, Xen will translate and call
vgic_interrupt_inject, which doesn't go via the hardware ITS at all,
since it doesn't need to.

[...]
> Sorry. I correct it as "So effectively no physical commands are sent
> to ITS hardware that are related to dummy/phantom devices"

Remember that in this design the vits doesn't generate any commands to
the physical its _at all_ even for real devices. It just calls
core/generic APIs.

Ian.

  reply	other threads:[~2015-06-05 16:38 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
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 [this message]
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=1433522336.7108.359.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.