From: Mian Yousaf Kaukab <yousaf.kaukab@suse.com>
To: Auger Eric <eric.auger@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
marc.zyngier@arm.com, alex.williamson@redhat.com
Cc: will.deacon@arm.com
Subject: Re: [PATCH 1/2] irqdomain: add empty irq_domain_check_msi_remap
Date: Thu, 2 Mar 2017 14:31:37 +0100 [thread overview]
Message-ID: <6545e332-ecf4-d273-5b2c-84205cfdb266@suse.com> (raw)
In-Reply-To: <bb4aaa0e-f38a-9f6a-85a9-34be0a855741@redhat.com>
On 03/02/2017 02:12 PM, Auger Eric wrote:
> Hi Yousaf,
>
> On 02/03/2017 13:23, Mian Yousaf Kaukab wrote:
>> On 03/02/2017 11:24 AM, Auger Eric wrote:
>>> Hi Mian Yousaf,
>>>
>>> On 02/03/2017 11:01, Mian Yousaf Kaukab wrote:
>>>> Fix following build error for s390:
>>>> drivers/vfio/vfio_iommu_type1.c: In function
>>>> 'vfio_iommu_type1_attach_group':
>>>> drivers/vfio/vfio_iommu_type1.c:1290:25: error: implicit declaration
>>>> of function 'irq_domain_check_msi_remap'
>>>>
>>>> Signed-off-by: Mian Yousaf Kaukab <yousaf.kaukab@suse.com>
>>>> ---
>>>> include/linux/irqdomain.h | 4 ++++
>>>> 1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/include/linux/irqdomain.h b/include/linux/irqdomain.h
>>>> index 188eced6813e..137817b08cdc 100644
>>>> --- a/include/linux/irqdomain.h
>>>> +++ b/include/linux/irqdomain.h
>>>> @@ -524,6 +524,10 @@ static inline struct irq_domain
>>>> *irq_find_matching_fwnode(
>>>> {
>>>> return NULL;
>>>> }
>>>> +static inline bool irq_domain_check_msi_remap(void)
>>>> +{
>>>> + return true;
>>> By default you should rather return false, reporting there is no MSI
>>> remapping capability on irq domain side. Besides thank you for the fix.
>> I choose to return true based on the function header comments of
>> irq_domain_check_msi_remap. It says
>>
>> "Return: false if any MSI irq domain does not support IRQ remapping,
>> true otherwise (including if there is no MSI irq domain)"
>>
>> So function should return true in case of no MSI irq domain. Have I miss
>> understood this?
> This behavior is indeed mandated on ARM - where MSI are translated by
> the smmu - to allow safe device assignment if there is no MSI domain,
> ie. in this situation there is no risk an assigned device writes into an
> MSI doorbell.
>
> As the function is not implemented at all in your case, personally I
> would rather be defensive though and return false. You were not able to
> check the capability.
OK Agree. I will send an update as soon as a decision is made on 2/2.
BR,
Yousaf
prev parent reply other threads:[~2017-03-02 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 10:01 [PATCH 1/2] irqdomain: add empty irq_domain_check_msi_remap Mian Yousaf Kaukab
2017-03-02 10:01 ` [PATCH 2/2] vfio: type1: conditionally check MSI remapping at irq domain level Mian Yousaf Kaukab
2017-03-02 10:19 ` Marc Zyngier
2017-03-02 10:24 ` Auger Eric
2017-03-02 12:38 ` Mian Yousaf Kaukab
2017-03-02 13:46 ` Auger Eric
2017-03-02 15:01 ` Mian Yousaf Kaukab
2017-03-02 10:16 ` [PATCH 1/2] irqdomain: add empty irq_domain_check_msi_remap Marc Zyngier
2017-03-02 10:29 ` Auger Eric
2017-03-02 10:24 ` Auger Eric
2017-03-02 12:23 ` Mian Yousaf Kaukab
2017-03-02 13:12 ` Auger Eric
2017-03-02 13:31 ` Mian Yousaf Kaukab [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=6545e332-ecf4-d273-5b2c-84205cfdb266@suse.com \
--to=yousaf.kaukab@suse.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox