From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "Prasun.kapoor@cavium.com" <Prasun.kapoor@cavium.com>,
"Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>,
Julien Grall <julien.grall@linaro.org>,
xen Devel <xen-devel@lists.xen.org>,
"Kumar, Vijaya" <Vijaya.Kumar@caviumnetworks.com>,
Julien Grall <julien.grall.oss@gmail.com>
Subject: Re: [PATCH 0/2] Re-factoring passthrough/pci.c and adding place-holder code for ARM/PCI
Date: Thu, 16 Apr 2015 16:28:31 +0100 [thread overview]
Message-ID: <1429198111.25195.163.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1504141030000.7690@kaball.uk.xensource.com>
On Tue, 2015-04-14 at 10:34 +0100, Stefano Stabellini wrote:
> On Tue, 14 Apr 2015, Jaggi, Manish wrote:
> > Hi Julien,
> >
> > From: Julien Grall <julien.grall.oss@gmail.com>
> > Sent: Monday, April 13, 2015 3:49 PM
> > To: Jaggi, Manish; xen Devel; Stefano Stabellini; Julien Grall; Ian Campbell; Kumar, Vijaya; Prasun.kapoor@cavium.com
> > Subject: Re: [Xen-devel] [PATCH 0/2] Re-factoring passthrough/pci.c and adding place-holder code for ARM/PCI
> >
> > Hi Manish,
> >
> > On 13/04/15 08:37, Manish Jaggi wrote:
> > > Xen currently does not have PCI support for ARM builds. This patch set
> > > makes the code compilable for ARM PCI and adds places-holder code
> > > which would be replaced with PCI pass-through support patch series.
> >
> > May I ask why you did send directly all the code to support PCI on ARM?
> >
> > Without the rest it's hard to tell whether these patches make sense or not.
> >
> > [Manish] As I have mentioned these two patches are only for refactoring msi specific functions to x86 files and providing the constructs that make PCI ARM code compilable.
> >
> > The code for PCI ARM is very basic in the patch and PCI passthrough code patches will follow in next series. Please let me know which code does not makes sense and I will modify it.
>
> On the face if it, it makes sense, and I understand that you are doing
> this to just build Xen on ARM with HAS_PCI.
>
> However it is hard to understand the full picture, how all the pieces
> fit together, without the rest. I think it would make sense to place
> these two patches at the beginning of your longer series.
I agree.
next prev parent reply other threads:[~2015-04-16 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 7:37 [PATCH 0/2] Re-factoring passthrough/pci.c and adding place-holder code for ARM/PCI Manish Jaggi
2015-04-13 10:19 ` Julien Grall
2015-04-13 10:21 ` Julien Grall
2015-04-14 1:12 ` Jaggi, Manish
2015-04-14 9:34 ` Stefano Stabellini
2015-04-16 15:28 ` Ian Campbell [this message]
2015-04-14 9:07 ` Jan Beulich
2015-04-16 15:27 ` 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=1429198111.25195.163.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Manish.Jaggi@caviumnetworks.com \
--cc=Prasun.kapoor@cavium.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=julien.grall.oss@gmail.com \
--cc=julien.grall@linaro.org \
--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.