From: Julien Grall <julien.grall@linaro.org>
To: manish jaggi <manishjaggi.oss@gmail.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: manish.jaggi@caviumnetworks.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Vijaya.Kumar@caviumnetworks.com,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen regressions for ARM SMMU (non pci-passthrough)
Date: Mon, 27 Oct 2014 13:26:45 +0000 [thread overview]
Message-ID: <544E4815.8080806@linaro.org> (raw)
In-Reply-To: <CAAiw7J=OzhY=sqH6cUJy5K-KNswrF0VGXgzxORQJECnk7WeOCQ@mail.gmail.com>
Hello Manish,
On 10/27/2014 09:54 AM, manish jaggi wrote:
> On 27 October 2014 14:57, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> On Mon, 2014-10-27 at 13:56 +0530, manish jaggi wrote:
>>> I am trying to find out about the tests which are part of the Xen
>>> regression suite for Arm which tests the SMMU and non pic-passthrough
>>> feature.
>>
>> There are currently no such tests in the osstest suite.
Device passthrough is not supported in Xen upstream. So adding test for
it is not yet relevant.
For SMMU, there is no need to have specific test. Any platform with SMMU
describe in the device tree will use the SMMU drivers in Xen.
We have only one platform with SMMU platform in OSS-test which is
midway. But the device tree provided upstream doesn't have the SMMU nodes.
>>
> Is Julien Planning to add the tests ?
I don't plan to add any test or make midway uses SMMU for testing. You
are welcome to send a patch for it.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-10-27 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 8:26 Xen regressions for ARM SMMU (non pci-passthrough) manish jaggi
2014-10-27 9:27 ` Ian Campbell
2014-10-27 9:54 ` manish jaggi
2014-10-27 13:26 ` Julien Grall [this message]
2014-10-28 9:19 ` manish jaggi
2014-10-28 13:57 ` Konrad Rzeszutek Wilk
2014-10-28 14:23 ` manish jaggi
2014-10-28 14:38 ` 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=544E4815.8080806@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=manish.jaggi@caviumnetworks.com \
--cc=manishjaggi.oss@gmail.com \
--cc=stefano.stabellini@eu.citrix.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.