All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Manish <mjaggi@caviumnetworks.com>,
	"Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "stefano.stabellini@citrix.com" <stefano.stabellini@citrix.com>,
	"tim@xen.org" <tim@xen.org>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>
Subject: Re: [PATCH for 4.6 13/13] xen/iommu: smmu: Add Xen specific code to be able to use the driver
Date: Thu, 19 Feb 2015 06:01:42 +0000	[thread overview]
Message-ID: <54E57C46.2030008@linaro.org> (raw)
In-Reply-To: <54E550B2.1090605@caviumnetworks.com>



On 19/02/2015 02:55, Manish wrote:
>
> On 18/02/15 11:52 pm, Julien Grall wrote:
>>
>>
>> On 18/02/2015 17:30, Jaggi, Manish wrote:
>>> [manish] There are general comments on the data structures
>>> (a) I don't see a use case where for same domain (VM) there would be
>>> different context banks , so linked list may not be required.
>>
>> I guess you mean the list in arm_smmu_xen_domain? All the devices
>> pass-through to a domain may not be protected by the same SMMU.
>> Therefore the context banks are different.
> you are right. For each smmu the context bank instance for a xen domain
> is duplicated with just a change in context bank id. I was thinking can
> it be minimized.
>>
>> Also, for now a context is allocated per-device. It should be rework
>> to share the context between multiple device protected by the same
>> SMMU and pass-through to the same domain.
> Yes, this is exactly I an doing at my end.
>>
>>> (b) Also iommu group may not be relevant for the same reason.
>>> I am curious to find the use cases.
>>
>> The iommu_group is used to store the configuration of the device
>> protected by an SMMU (i.e the stream ids associated to this domain).
>>
>> I'm a bit surprised that you think they are not useful...
> How do we create an iommu_group in xen ? AFAIK an iommu group is a vfio
> group in linux which is assigned to a a VM.
> lkvm run -m 512 -k home/Image ...  --vfio-groups=48, 51

  > For Xen There are 2 ways of attaching devices using xl pci-attach or in
> domU cfg file. Should they create different iommu_groups ?

Why are you talking about VFIO? The iommu_group is created by the SMMU 
when a new device is added (see arm_smmu_device). At the time we are 
speaking, Linux and Xen use one iommu group per-device. No matters what 
VFIO does.

Even though we have two ways to attach PCI on the toolstack, both are 
using the same hypercall at the end.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-02-19  6:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 20:08 [PATCH for 4.6 00/13] xen/arm: Resync the SMMU driver with the Linux one Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 01/13] xen/arm: gic-v2: Change the device name in DT_DEVICE_START Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 02/13] xen/arm: vgic: Drop unecessary include asm/device.h Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 03/13] xen: Introduce ACCESS_ONCE macro Julien Grall
2014-12-17 10:05   ` Jan Beulich
2014-12-17 12:54     ` Julien Grall
2014-12-17 17:10       ` Jan Beulich
2014-12-17 17:52         ` Andrew Cooper
2014-12-18 15:58           ` Julien Grall
2014-12-18 15:58           ` Julien Grall
2015-01-15 13:39           ` Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 04/13] xen/dt: Extend dt_device_match to possibly store data Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 05/13] xen/arm: device: Rename device_type into device_match Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 06/13] xen/iommu: arm: Remove temporary the SMMU driver Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 07/13] xen: Introduce a generic way to describe device Julien Grall
2014-12-17 10:16   ` Jan Beulich
2014-12-17 10:30     ` Julien Grall
2014-12-17 10:46       ` Jan Beulich
2014-12-17 13:03         ` Julien Grall
2014-12-17 17:17           ` Jan Beulich
2014-12-18 15:56             ` Julien Grall
2014-12-18 16:02               ` Jan Beulich
2014-12-18 16:07                 ` Julien Grall
2014-12-18  1:12   ` Zhang, Yang Z
2014-12-18  8:52     ` Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 08/13] xen/iommu: Consolidate device assignment ops into a single set Julien Grall
2014-12-17 10:20   ` Jan Beulich
2014-12-16 20:08 ` [PATCH for 4.6 09/13] xen/arm: Describe device supported by a driver with dt_match_node Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 10/13] xen/iommu: arm: Import the SMMU driver from Linux Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 11/13] xen/iommu: smmu: Check for duplicate stream IDs when registering master devices Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 12/13] xen/iommu: smmu: Introduce automatic stream-id-masking Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 13/13] xen/iommu: smmu: Add Xen specific code to be able to use the driver Julien Grall
2015-02-18  1:02   ` Manish
2015-02-18 11:47     ` Julien Grall
2015-02-18 11:54       ` Julien Grall
2015-02-18 17:30         ` Jaggi, Manish
2015-02-18 18:22           ` Julien Grall
2015-02-19  2:55             ` Manish
2015-02-19  6:01               ` Julien Grall [this message]
2015-02-19  7:16                 ` Manish
2015-02-19 10:34               ` Andrew Cooper

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=54E57C46.2030008@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Manish.Jaggi@caviumnetworks.com \
    --cc=ian.campbell@citrix.com \
    --cc=mjaggi@caviumnetworks.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --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.