From: Ian Campbell <Ian.Campbell@citrix.com>
To: manish jaggi <manishjaggi.oss@gmail.com>
Cc: manish.jaggi@caviumnetworks.com,
Julien Grall <julien.grall@linaro.org>,
xen-devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Few Comments on the Xen SMMU ARM code
Date: Fri, 12 Dec 2014 11:14:27 +0000 [thread overview]
Message-ID: <1418382867.23309.54.camel@citrix.com> (raw)
In-Reply-To: <CAAiw7J=VLb5tJn18uYZh-SHO9Kb6PsUTiM694BdzRfjKxpv_-Q@mail.gmail.com>
On Thu, 2014-12-11 at 10:02 -0800, manish jaggi wrote:
> This is the complete smmu.c file which you can refer for PCI
> passthrough (http://pastebin.com/QDX8fpDu)
I'm afraid that as Julien says this is basically no help.
> Just FYI this is not a patch, we are still testing on our board and
> can post a patch only after our testing is complete.
Please post whatever patch(es) you have now with a WIP (Work In
Progress) tag in the subject. It does not need to be complete, working,
tested or clean. You can put a big fat warning on the commit log if you
like. See for example
http://article.gmane.org/gmane.comp.emulators.xen.devel/220265 where I
did exactly this with some very dirty patches I was halfway through
writing[0] (I used "incomplete" rather than "WIP", the exact words don't
really matter).
If you have any design documentation then please include that as well,
e.g. in the 0/N mail.
IMHO seeing what you have actually done which is leading to the
questions you are asking is a prerequisite to having any sort of
constructive discussion about the design decisions going forward. I'd
certainly want to see the code before any call takes place.
Cheers,
Ian.
[0] in this case because I wasn't going to be able to finish them soon
and it was better to get them onto the list than rotting in my dev tree.
prev parent reply other threads:[~2014-12-12 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 2:39 Few Comments on the Xen SMMU ARM code manish jaggi
2014-12-11 10:20 ` Julien Grall
2014-12-11 10:30 ` Stefano Stabellini
2014-12-11 18:02 ` manish jaggi
2014-12-11 19:10 ` Julien Grall
2014-12-12 11:14 ` Ian Campbell [this message]
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=1418382867.23309.54.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--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.