From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Cc: Linuxarm <linuxarm@huawei.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
wanghuiqiang <wanghuiqiang@huawei.com>,
"Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>,
"steven.price@arm.com" <steven.price@arm.com>,
"Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
"jon@solid-run.com" <jon@solid-run.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
yangyicong <yangyicong@huawei.com>
Subject: RE: [PATCH v8 02/11] iommu: Introduce a union to struct iommu_resv_region
Date: Wed, 23 Mar 2022 15:55:40 +0000 [thread overview]
Message-ID: <07bb59d690e84edfa62d7c844612b526@huawei.com> (raw)
In-Reply-To: <5cf2c21b-6974-b2f9-140d-382985cf3095@arm.com>
> -----Original Message-----
> From: Robin Murphy [mailto:robin.murphy@arm.com]
> Sent: 22 March 2022 18:27
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>;
> linux-arm-kernel@lists.infradead.org; linux-acpi@vger.kernel.org;
> iommu@lists.linux-foundation.org
> Cc: Linuxarm <linuxarm@huawei.com>; lorenzo.pieralisi@arm.com;
> joro@8bytes.org; will@kernel.org; wanghuiqiang
> <wanghuiqiang@huawei.com>; Guohanjun (Hanjun Guo)
> <guohanjun@huawei.com>; steven.price@arm.com; Sami.Mujawar@arm.com;
> jon@solid-run.com; eric.auger@redhat.com; yangyicong
> <yangyicong@huawei.com>
> Subject: Re: [PATCH v8 02/11] iommu: Introduce a union to struct
> iommu_resv_region
>
> On 2022-02-21 15:43, Shameer Kolothum wrote:
> > A union is introduced to struct iommu_resv_region to hold
> > any firmware specific data. This is in preparation to add
> > support for IORT RMR reserve regions and the union now holds
> > the RMR specific information.
> >
> > Signed-off-by: Shameer Kolothum
> <shameerali.kolothum.thodi@huawei.com>
> > ---
> > include/linux/iommu.h | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> > index de0c57a567c8..b06952a75f95 100644
> > --- a/include/linux/iommu.h
> > +++ b/include/linux/iommu.h
> > @@ -126,6 +126,11 @@ enum iommu_resv_type {
> > IOMMU_RESV_SW_MSI,
> > };
> >
> > +struct iommu_iort_rmr_data {
> > + u32 *sids; /* Stream Ids associated with IORT RMR entry */
>
> Please make this const.
>
> Further nit: capitalisation of "IDs" in the comment, otherwise I might
> worry about the possibility of Stream Egos too :P
True :). Will do that.
Thanks,
Shameer
>
> > + u32 num_sids;
> > +};
> > +
> > /**
> > * struct iommu_resv_region - descriptor for a reserved memory region
> > * @list: Linked list pointers
> > @@ -133,6 +138,7 @@ enum iommu_resv_type {
> > * @length: Length of the region in bytes
> > * @prot: IOMMU Protection flags (READ/WRITE/...)
> > * @type: Type of the reserved region
> > + * @fw_data: FW specific reserved region data
>
> Nit: we've got plenty of room to spell out "Firmware-specific", and it
> never hurts to make documentation as easy to read as possible.
>
> Thanks,
> Robin.
>
> > */
> > struct iommu_resv_region {
> > struct list_head list;
> > @@ -140,6 +146,9 @@ struct iommu_resv_region {
> > size_t length;
> > int prot;
> > enum iommu_resv_type type;
> > + union {
> > + struct iommu_iort_rmr_data rmr;
> > + } fw_data;
> > };
> >
> > /**
WARNING: multiple messages have this Message-ID (diff)
From: Shameerali Kolothum Thodi via iommu <iommu@lists.linux-foundation.org>
To: Robin Murphy <robin.murphy@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Cc: "jon@solid-run.com" <jon@solid-run.com>,
Linuxarm <linuxarm@huawei.com>,
"steven.price@arm.com" <steven.price@arm.com>,
"Guohanjun \(Hanjun Guo\)" <guohanjun@huawei.com>,
yangyicong <yangyicong@huawei.com>,
"Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
"will@kernel.org" <will@kernel.org>,
wanghuiqiang <wanghuiqiang@huawei.com>
Subject: RE: [PATCH v8 02/11] iommu: Introduce a union to struct iommu_resv_region
Date: Wed, 23 Mar 2022 15:55:40 +0000 [thread overview]
Message-ID: <07bb59d690e84edfa62d7c844612b526@huawei.com> (raw)
In-Reply-To: <5cf2c21b-6974-b2f9-140d-382985cf3095@arm.com>
> -----Original Message-----
> From: Robin Murphy [mailto:robin.murphy@arm.com]
> Sent: 22 March 2022 18:27
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>;
> linux-arm-kernel@lists.infradead.org; linux-acpi@vger.kernel.org;
> iommu@lists.linux-foundation.org
> Cc: Linuxarm <linuxarm@huawei.com>; lorenzo.pieralisi@arm.com;
> joro@8bytes.org; will@kernel.org; wanghuiqiang
> <wanghuiqiang@huawei.com>; Guohanjun (Hanjun Guo)
> <guohanjun@huawei.com>; steven.price@arm.com; Sami.Mujawar@arm.com;
> jon@solid-run.com; eric.auger@redhat.com; yangyicong
> <yangyicong@huawei.com>
> Subject: Re: [PATCH v8 02/11] iommu: Introduce a union to struct
> iommu_resv_region
>
> On 2022-02-21 15:43, Shameer Kolothum wrote:
> > A union is introduced to struct iommu_resv_region to hold
> > any firmware specific data. This is in preparation to add
> > support for IORT RMR reserve regions and the union now holds
> > the RMR specific information.
> >
> > Signed-off-by: Shameer Kolothum
> <shameerali.kolothum.thodi@huawei.com>
> > ---
> > include/linux/iommu.h | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> > index de0c57a567c8..b06952a75f95 100644
> > --- a/include/linux/iommu.h
> > +++ b/include/linux/iommu.h
> > @@ -126,6 +126,11 @@ enum iommu_resv_type {
> > IOMMU_RESV_SW_MSI,
> > };
> >
> > +struct iommu_iort_rmr_data {
> > + u32 *sids; /* Stream Ids associated with IORT RMR entry */
>
> Please make this const.
>
> Further nit: capitalisation of "IDs" in the comment, otherwise I might
> worry about the possibility of Stream Egos too :P
True :). Will do that.
Thanks,
Shameer
>
> > + u32 num_sids;
> > +};
> > +
> > /**
> > * struct iommu_resv_region - descriptor for a reserved memory region
> > * @list: Linked list pointers
> > @@ -133,6 +138,7 @@ enum iommu_resv_type {
> > * @length: Length of the region in bytes
> > * @prot: IOMMU Protection flags (READ/WRITE/...)
> > * @type: Type of the reserved region
> > + * @fw_data: FW specific reserved region data
>
> Nit: we've got plenty of room to spell out "Firmware-specific", and it
> never hurts to make documentation as easy to read as possible.
>
> Thanks,
> Robin.
>
> > */
> > struct iommu_resv_region {
> > struct list_head list;
> > @@ -140,6 +146,9 @@ struct iommu_resv_region {
> > size_t length;
> > int prot;
> > enum iommu_resv_type type;
> > + union {
> > + struct iommu_iort_rmr_data rmr;
> > + } fw_data;
> > };
> >
> > /**
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Cc: Linuxarm <linuxarm@huawei.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
wanghuiqiang <wanghuiqiang@huawei.com>,
"Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>,
"steven.price@arm.com" <steven.price@arm.com>,
"Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
"jon@solid-run.com" <jon@solid-run.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
yangyicong <yangyicong@huawei.com>
Subject: RE: [PATCH v8 02/11] iommu: Introduce a union to struct iommu_resv_region
Date: Wed, 23 Mar 2022 15:55:40 +0000 [thread overview]
Message-ID: <07bb59d690e84edfa62d7c844612b526@huawei.com> (raw)
In-Reply-To: <5cf2c21b-6974-b2f9-140d-382985cf3095@arm.com>
> -----Original Message-----
> From: Robin Murphy [mailto:robin.murphy@arm.com]
> Sent: 22 March 2022 18:27
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>;
> linux-arm-kernel@lists.infradead.org; linux-acpi@vger.kernel.org;
> iommu@lists.linux-foundation.org
> Cc: Linuxarm <linuxarm@huawei.com>; lorenzo.pieralisi@arm.com;
> joro@8bytes.org; will@kernel.org; wanghuiqiang
> <wanghuiqiang@huawei.com>; Guohanjun (Hanjun Guo)
> <guohanjun@huawei.com>; steven.price@arm.com; Sami.Mujawar@arm.com;
> jon@solid-run.com; eric.auger@redhat.com; yangyicong
> <yangyicong@huawei.com>
> Subject: Re: [PATCH v8 02/11] iommu: Introduce a union to struct
> iommu_resv_region
>
> On 2022-02-21 15:43, Shameer Kolothum wrote:
> > A union is introduced to struct iommu_resv_region to hold
> > any firmware specific data. This is in preparation to add
> > support for IORT RMR reserve regions and the union now holds
> > the RMR specific information.
> >
> > Signed-off-by: Shameer Kolothum
> <shameerali.kolothum.thodi@huawei.com>
> > ---
> > include/linux/iommu.h | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> > index de0c57a567c8..b06952a75f95 100644
> > --- a/include/linux/iommu.h
> > +++ b/include/linux/iommu.h
> > @@ -126,6 +126,11 @@ enum iommu_resv_type {
> > IOMMU_RESV_SW_MSI,
> > };
> >
> > +struct iommu_iort_rmr_data {
> > + u32 *sids; /* Stream Ids associated with IORT RMR entry */
>
> Please make this const.
>
> Further nit: capitalisation of "IDs" in the comment, otherwise I might
> worry about the possibility of Stream Egos too :P
True :). Will do that.
Thanks,
Shameer
>
> > + u32 num_sids;
> > +};
> > +
> > /**
> > * struct iommu_resv_region - descriptor for a reserved memory region
> > * @list: Linked list pointers
> > @@ -133,6 +138,7 @@ enum iommu_resv_type {
> > * @length: Length of the region in bytes
> > * @prot: IOMMU Protection flags (READ/WRITE/...)
> > * @type: Type of the reserved region
> > + * @fw_data: FW specific reserved region data
>
> Nit: we've got plenty of room to spell out "Firmware-specific", and it
> never hurts to make documentation as easy to read as possible.
>
> Thanks,
> Robin.
>
> > */
> > struct iommu_resv_region {
> > struct list_head list;
> > @@ -140,6 +146,9 @@ struct iommu_resv_region {
> > size_t length;
> > int prot;
> > enum iommu_resv_type type;
> > + union {
> > + struct iommu_iort_rmr_data rmr;
> > + } fw_data;
> > };
> >
> > /**
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-23 15:55 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 15:43 [PATCH v8 00/11] ACPI/IORT: Support for IORT RMR node Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-21 15:43 ` [PATCH v8 01/11] ACPI/IORT: Add temporary RMR node flag definitions Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-03-22 19:31 ` Robin Murphy
2022-03-22 19:31 ` Robin Murphy
2022-03-22 19:31 ` Robin Murphy
2022-02-21 15:43 ` [PATCH v8 02/11] iommu: Introduce a union to struct iommu_resv_region Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-03-22 18:27 ` Robin Murphy
2022-03-22 18:27 ` Robin Murphy
2022-03-22 18:27 ` Robin Murphy
2022-03-23 15:55 ` Shameerali Kolothum Thodi [this message]
2022-03-23 15:55 ` Shameerali Kolothum Thodi
2022-03-23 15:55 ` Shameerali Kolothum Thodi via iommu
2022-02-21 15:43 ` [PATCH v8 03/11] ACPI/IORT: Add helper functions to parse RMR nodes Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-24 10:13 ` Lorenzo Pieralisi
2022-02-24 10:13 ` Lorenzo Pieralisi
2022-02-24 10:13 ` Lorenzo Pieralisi
2022-02-25 17:31 ` Shameerali Kolothum Thodi
2022-02-25 17:31 ` Shameerali Kolothum Thodi
2022-02-25 17:31 ` Shameerali Kolothum Thodi via iommu
2022-03-10 10:32 ` Eric Auger
2022-03-10 10:32 ` Eric Auger
2022-03-10 10:32 ` Eric Auger
2022-03-10 10:45 ` Shameerali Kolothum Thodi
2022-03-10 10:45 ` Shameerali Kolothum Thodi
2022-03-10 10:45 ` Shameerali Kolothum Thodi via iommu
2022-02-21 15:43 ` [PATCH v8 04/11] iommu/dma: Introduce generic helper to retrieve RMR info Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-21 15:43 ` [PATCH v8 05/11] ACPI/IORT: Add a helper to retrieve RMR memory regions Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-23 18:05 ` Lorenzo Pieralisi
2022-02-23 18:05 ` Lorenzo Pieralisi
2022-02-23 18:05 ` Lorenzo Pieralisi
2022-03-22 19:08 ` Robin Murphy
2022-03-22 19:08 ` Robin Murphy
2022-03-22 19:08 ` Robin Murphy
2022-03-23 16:06 ` Shameerali Kolothum Thodi
2022-03-23 16:06 ` Shameerali Kolothum Thodi
2022-03-23 16:06 ` Shameerali Kolothum Thodi via iommu
2022-03-25 17:49 ` Robin Murphy
2022-03-25 17:49 ` Robin Murphy
2022-03-25 17:49 ` Robin Murphy
2022-02-21 15:43 ` [PATCH v8 06/11] iommu/arm-smmu-v3: Introduce strtab init helper Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-21 15:43 ` [PATCH v8 07/11] iommu/arm-smmu-v3: Refactor arm_smmu_init_bypass_stes() to force bypass Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-21 15:43 ` [PATCH v8 08/11] iommu/arm-smmu-v3: Get associated RMR info and install bypass STE Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-21 15:43 ` [PATCH v8 09/11] iommu/arm-smmu: Get associated RMR info and install bypass SMR Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-02-21 15:43 ` [PATCH v8 10/11] iommu/arm-smmu-v3: Reserve any RMR regions associated with a dev Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-03-22 19:12 ` Robin Murphy
2022-03-22 19:12 ` Robin Murphy
2022-03-22 19:12 ` Robin Murphy
2022-02-21 15:43 ` [PATCH v8 11/11] iommu/arm-smmu: " Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum
2022-02-21 15:43 ` Shameer Kolothum via iommu
2022-03-03 10:37 ` [PATCH v8 00/11] ACPI/IORT: Support for IORT RMR node Steven Price
2022-03-03 10:37 ` Steven Price
2022-03-03 10:37 ` Steven Price
2022-03-03 13:02 ` Shameerali Kolothum Thodi
2022-03-03 13:02 ` Shameerali Kolothum Thodi
2022-03-03 13:02 ` Shameerali Kolothum Thodi via iommu
2022-03-11 8:06 ` Eric Auger
2022-03-11 8:06 ` Eric Auger
2022-03-11 8:06 ` Eric Auger
2022-03-11 13:23 ` Shameerali Kolothum Thodi
2022-03-11 13:23 ` Shameerali Kolothum Thodi
2022-03-11 13:23 ` Shameerali Kolothum Thodi via iommu
2022-03-11 8:19 ` Eric Auger
2022-03-11 8:19 ` Eric Auger
2022-03-11 8:19 ` Eric Auger
2022-03-11 10:34 ` Robin Murphy
2022-03-11 10:34 ` Robin Murphy
2022-03-11 10:34 ` Robin Murphy
2022-03-14 10:37 ` Eric Auger
2022-03-14 10:37 ` Eric Auger
2022-03-14 10:37 ` Eric Auger
2022-03-14 10:43 ` Ard Biesheuvel
2022-03-14 10:43 ` Ard Biesheuvel
2022-03-14 10:43 ` Ard Biesheuvel
2022-03-14 11:30 ` Lorenzo Pieralisi
2022-03-14 11:30 ` Lorenzo Pieralisi
2022-03-14 11:30 ` Lorenzo Pieralisi
2022-03-15 17:53 ` Eric Auger
2022-03-15 17:53 ` Eric Auger
2022-03-15 17:53 ` Eric Auger
2022-03-17 15:30 ` Shameerali Kolothum Thodi
2022-03-17 15:30 ` Shameerali Kolothum Thodi
2022-03-17 15:30 ` Shameerali Kolothum Thodi via iommu
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=07bb59d690e84edfa62d7c844612b526@huawei.com \
--to=shameerali.kolothum.thodi@huawei.com \
--cc=Sami.Mujawar@arm.com \
--cc=eric.auger@redhat.com \
--cc=guohanjun@huawei.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jon@solid-run.com \
--cc=joro@8bytes.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=wanghuiqiang@huawei.com \
--cc=will@kernel.org \
--cc=yangyicong@huawei.com \
/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.