From: Julien Grall <julien.grall@linaro.org>
To: manish jaggi <manishjaggi.oss@gmail.com>
Cc: Julien Grall <julien.grall@citrix.com>,
xen-devel@lists.xenproject.org, manish.jaggi@caviumnetworks.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Non PCI passthrough on xen-unstable tree
Date: Thu, 14 Aug 2014 09:48:14 +0100 [thread overview]
Message-ID: <53EC77CE.7070206@linaro.org> (raw)
In-Reply-To: <CAAiw7JnK++4ZWMxqsWzef3baVQ18zyk19MoMfk00Aft4_6diew@mail.gmail.com>
On 08/13/2014 06:29 PM, manish jaggi wrote:
>>> On 10 August 2014 07:53, manish jaggi <manishjaggi.oss@gmail.com> wrote:
>>>> I am trying to evaluate your changes
>>>> (http://www.gossamer-threads.com/lists/xen/devel/342003) while I am adding
>>>> support for PCI passthrough for xen on cavium thunder. Can you please
>>>> provide steps how you tested non-pci passthrough with your git.
>>
>> Everything should be written in the cover letter. I won't copy again the
>> steps here.
>>
> Can you please help us with the following so that we can test your
> patch and use it in our development
> Which linux version was used, defconfig and domU.cfg used ?
Why are you talking about linux version/defconfig? As said on my cover
letter nothing as been modified in Linux. The only requirements is the
kernel must have a driver for your device.
> Was it only on midway or can work on foundation model
Even though I did my development on midway, it should work on every
platform with devices under an SMMU.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-08-14 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 2:23 Non PCI passthrough on xen-unstable tree manish jaggi
2014-08-12 4:40 ` manish jaggi
2014-08-13 14:30 ` Julien Grall
2014-08-13 17:29 ` manish jaggi
2014-08-14 8:48 ` Julien Grall [this message]
2014-08-14 9:20 ` manish jaggi
2014-08-14 22:13 ` Julien Grall
2014-09-02 7:28 ` manish jaggi
2014-09-02 22:14 ` Stefano Stabellini
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=53EC77CE.7070206@linaro.org \
--to=julien.grall@linaro.org \
--cc=julien.grall@citrix.com \
--cc=manish.jaggi@caviumnetworks.com \
--cc=manishjaggi.oss@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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.