From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anup Patel <anup.patel@linaro.org>,
Vijay Kilari <vijay.kilari@gmail.com>,
Prasun Kapoor <prasun.Kapoor@caviumnetworks.com>,
manish.jaggi@caviumnetworks.com,
Julien Grall <julien.grall@linaro.org>,
xen-devel <xen-devel@lists.xen.org>,
psawargaonkar@linaro.org, Matt.Evans@arm.com,
Dave.Martin@arm.com, manish jaggi <manishjaggi.oss@gmail.com>
Subject: Re: [RFC + Queries] Flow of PCI passthrough in ARM
Date: Fri, 3 Oct 2014 10:01:10 +0100 [thread overview]
Message-ID: <1412326870.423.14.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410021757040.17038@kaball.uk.xensource.com>
On Thu, 2014-10-02 at 17:59 +0100, Stefano Stabellini wrote:
> On Thu, 2 Oct 2014, Stefano Stabellini wrote:
> > > >> >> using this the ITS emulation code in xen is able to trap ITS command
> > > >> >> writes by driver.
> > > >> >> But we are facing a problem now, where your help is needed
>
> Actually given that you are talking about the virtual ITS, why do you
> need the real Device ID or Stream ID of the passthrough device in the
> guest at all? Shouldn't you just be generating a bunch of virtual IDs
> instead?
>
> Let's take a step back: why do you need *real* IDs to program a
> *virtual* ITS?
Ack, I'm having a great deal of trouble figuring out why the guest would
ever see a physical hardware identifier of any kind.
Ian.
next prev parent reply other threads:[~2014-10-03 9:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 11:34 [RFC + Queries] Flow of PCI passthrough in ARM manish jaggi
2014-09-22 10:45 ` Stefano Stabellini
2014-09-22 11:09 ` Ian Campbell
2014-09-24 10:56 ` manish jaggi
2014-09-24 10:53 ` manish jaggi
2014-09-24 12:13 ` Jan Beulich
2014-09-24 14:10 ` Stefano Stabellini
2014-09-24 18:32 ` manish jaggi
2014-09-25 10:27 ` Stefano Stabellini
2014-10-01 10:37 ` manish jaggi
2014-10-02 16:41 ` Stefano Stabellini
2014-10-02 16:59 ` Stefano Stabellini
2014-10-03 9:01 ` Ian Campbell [this message]
2014-10-03 9:33 ` manish jaggi
2014-10-03 9:32 ` manish jaggi
2014-10-06 11:05 ` manish jaggi
2014-10-06 14:11 ` Stefano Stabellini
2014-10-06 15:38 ` Ian Campbell
2014-10-06 17:39 ` manish jaggi
2014-10-06 17:39 ` manish jaggi
2014-10-07 18:17 ` Stefano Stabellini
2014-10-08 11:46 ` manish jaggi
2014-10-08 12:46 ` Konrad Rzeszutek Wilk
2014-10-08 13:37 ` manish jaggi
2014-10-08 13:45 ` Ian Campbell
2014-10-08 13:47 ` manish jaggi
2014-10-08 13:58 ` Ian Campbell
2014-10-08 14:51 ` Konrad Rzeszutek Wilk
2014-10-20 13:30 ` manish jaggi
2014-10-20 14:54 ` Stefano Stabellini
2014-11-06 15:28 ` manish jaggi
2014-11-06 15:48 ` Stefano Stabellini
2014-11-06 15:55 ` manish jaggi
2014-11-06 16:02 ` Julien Grall
2014-11-06 16:07 ` Stefano Stabellini
2014-11-06 16:20 ` manish jaggi
2014-11-07 10:29 ` Julien Grall
2014-11-06 19:41 ` Konrad Rzeszutek Wilk
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=1412326870.423.14.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Dave.Martin@arm.com \
--cc=Matt.Evans@arm.com \
--cc=anup.patel@linaro.org \
--cc=julien.grall@linaro.org \
--cc=manish.jaggi@caviumnetworks.com \
--cc=manishjaggi.oss@gmail.com \
--cc=prasun.Kapoor@caviumnetworks.com \
--cc=psawargaonkar@linaro.org \
--cc=stefano.stabellini@eu.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.