All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Manish Jaggi <mjaggi@caviumnetworks.com>,
	xen Devel <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Julien Grall <julien.grall@linaro.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"Kumar, Vijaya" <Vijaya.Kumar@caviumnetworks.com>,
	"Prasun.kapoor@cavium.com" <Prasun.kapoor@cavium.com>
Subject: Re: [PATCH 0/2] Re-factoring passthrough/pci.c and adding place-holder code for ARM/PCI
Date: Mon, 13 Apr 2015 11:21:48 +0100	[thread overview]
Message-ID: <552B98BC.7020000@citrix.com> (raw)
In-Reply-To: <552B9818.7010702@gmail.com>

BTW, your series is not threaded.

I've already said it on another series. Please look at [1] to see how to
send correctly your series.

[1]
http://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Sending_the_patches_to_the_list

Regards,

On 13/04/15 11:19, Julien Grall wrote:
> 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.
> 
>> Re-factor MSI Handling
>> -------------
>> There is a some x86 specific code which is found in common code:
>> xen/drivers/passthrough/pci.c which needs to be re factored.
>>
>> MSI/X are configured and handled by dom0 or domU code on ARM64 and is not
>> required to be part of common code. However there are functions which are
>> used as part of common code and calls to these functions cannot be easily
>> re factored like pci_cleanup_msi.
> 
> On x86, the hypervisor is taking care of MSI (enabling/disabling in the
> config space) as long as doing sanity check on MSI used by a given domain.
> 
> How do you plan to handle it on ARM? IHMO, the MSI code is very useful
> and would also help GIC MSI implement (ITS + V2M).
> 
> FWIW, I've pointed out the same issue on the ITS series a couple of
> weeks ago.
> 
> Regards,
> 


-- 
Julien Grall

  reply	other threads:[~2015-04-13 10:21 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 [this message]
2015-04-14  1:12   ` Jaggi, Manish
2015-04-14  9:34     ` Stefano Stabellini
2015-04-16 15:28       ` Ian Campbell
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=552B98BC.7020000@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Prasun.kapoor@cavium.com \
    --cc=Vijaya.Kumar@caviumnetworks.com \
    --cc=julien.grall@linaro.org \
    --cc=mjaggi@caviumnetworks.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.