From: Alex Williamson <alex.williamson@redhat.com>
To: Bhushan Bharat <Bharat.Bhushan@freescale.com>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
"eric.auger@linaro.org" <eric.auger@linaro.org>,
"pranavkumar@linaro.org" <pranavkumar@linaro.org>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>
Subject: Re: [RFC PATCH 3/6] vfio: Extend iommu-info to return MSIs automap state
Date: Tue, 06 Oct 2015 09:11:18 -0600 [thread overview]
Message-ID: <1444144278.4059.35.camel@redhat.com> (raw)
In-Reply-To: <CY1PR0301MB12762322B3669142A04F9DB890370@CY1PR0301MB1276.namprd03.prod.outlook.com>
On Tue, 2015-10-06 at 08:53 +0000, Bhushan Bharat wrote:
>
>
> > -----Original Message-----
> > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > Sent: Tuesday, October 06, 2015 4:15 AM
> > To: Bhushan Bharat-R65777 <Bharat.Bhushan@freescale.com>
> > Cc: kvmarm@lists.cs.columbia.edu; kvm@vger.kernel.org;
> > christoffer.dall@linaro.org; eric.auger@linaro.org; pranavkumar@linaro.org;
> > marc.zyngier@arm.com; will.deacon@arm.com
> > Subject: Re: [RFC PATCH 3/6] vfio: Extend iommu-info to return MSIs
> > automap state
> >
> > On Mon, 2015-10-05 at 06:00 +0000, Bhushan Bharat wrote:
> > > > -1138,6 +1156,8 @@
> > > > > static long vfio_iommu_type1_ioctl(void *iommu_data,
> > > > > }
> > > > > } else if (cmd == VFIO_IOMMU_GET_INFO) {
> > > > > struct vfio_iommu_type1_info info;
> > > > > + struct iommu_domain_msi_maps msi_maps;
> > > > > + int ret;
> > > > >
> > > > > minsz = offsetofend(struct vfio_iommu_type1_info,
> > > > iova_pgsizes);
> > > > >
> > > > > @@ -1149,6 +1169,18 @@ static long vfio_iommu_type1_ioctl(void
> > > > > *iommu_data,
> > > > >
> > > > > info.flags = 0;
> > > > >
> > > > > + ret = vfio_domains_get_msi_maps(iommu, &msi_maps);
> > > > > + if (ret)
> > > > > + return ret;
> > > >
> > > > And now ioctl(VFIO_IOMMU_GET_INFO) no longer works for any
> > IOMMU
> > > > implementing domain_get_attr but not supporting
> > > > DOMAIN_ATTR_MSI_MAPPING.
> > >
> > > With this current patch version this will get the default assumed behavior
> > as you commented on previous patch.
> >
> > How so?
>
> You are right, the ioctl will return failure. But that should be ok, right?
Not remotely. ioctl(VFIO_IOMMU_GET_INFO) can't suddenly stop working on
some platforms.
> >
> > + msi_maps->automap = true;
> > + msi_maps->override_automap = false;
> > +
> > + if (domain->ops->domain_get_attr)
> > + ret = domain->ops->domain_get_attr(domain, attr,
> > + data);
> >
> > If domain_get_attr is implemented, but DOMAIN_ATTR_MSI_MAPPING is
> > not, ret should be an error code.
>
> Currently it returns same error code returned by domain->ops->domain_get_attr().
> I do not think we want to complicate that we return an error to user-space that msi's probably cannot be used but user-space can continue with Legacy interrupt, or you want that?
I can't really parse your statement, but ioctl(VFIO_IOMMU_GET_INFO)
works today and it must work with your changes. Your change should only
affect whether some flags are visible, MSI has worked just fine up to
this point on other platforms.
next prev parent reply other threads:[~2015-10-06 15:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1443624989-24346-1-git-send-email-Bharat.Bhushan@freescale.com>
2015-09-30 14:56 ` [RFC PATCH 2/6] iommu: Add interface to get msi-pages mapping attributes Bharat Bhushan
2015-10-02 22:45 ` Alex Williamson
2015-10-05 5:17 ` Bhushan Bharat
2015-10-05 5:56 ` Bhushan Bharat
2015-09-30 14:56 ` [RFC PATCH 3/6] vfio: Extend iommu-info to return MSIs automap state Bharat Bhushan
2015-10-02 22:46 ` Alex Williamson
2015-10-05 6:00 ` Bhushan Bharat
2015-10-05 22:45 ` Alex Williamson
2015-10-06 8:53 ` Bhushan Bharat
2015-10-06 15:11 ` Alex Williamson [this message]
2015-09-30 14:56 ` [RFC PATCH 4/6] vfio: Add interface to iommu-map/unmap MSI pages Bharat Bhushan
2015-10-02 22:46 ` Alex Williamson
2015-10-05 6:27 ` Bhushan Bharat
2015-10-05 22:45 ` Alex Williamson
2015-10-06 9:05 ` Bhushan Bharat
2015-10-06 15:12 ` Alex Williamson
2015-09-30 14:56 ` [RFC PATCH 5/6] vfio-pci: Create iommu mapping for msi interrupt Bharat Bhushan
2015-09-30 11:02 ` kbuild test robot
2015-09-30 11:32 ` Bhushan Bharat
2015-09-30 11:34 ` kbuild test robot
2015-10-02 22:46 ` Alex Williamson
2015-10-05 7:20 ` Bhushan Bharat
2015-10-05 22:44 ` Alex Williamson
2015-10-06 8:32 ` Bhushan Bharat
2015-10-06 15:06 ` Alex Williamson
2015-09-30 14:56 ` [RFC PATCH 6/6] arm-smmu: Allow to set iommu mapping for MSI Bharat Bhushan
2015-10-02 22:46 ` Alex Williamson
2015-10-05 8:33 ` Bhushan Bharat
2015-10-05 22:54 ` Alex Williamson
2015-10-06 10:26 ` Bhushan Bharat
2015-10-26 15:40 ` Christoffer Dall
2015-11-02 2:53 ` Pranavkumar Sawargaonkar
2015-10-02 22:45 ` [RFC PATCH 1/6] vfio: Add interface for add/del reserved iova region Alex Williamson
2015-10-05 4:55 ` Bhushan Bharat
2015-10-05 22:45 ` Alex Williamson
2015-10-06 9:39 ` Bhushan Bharat
2015-10-06 15:21 ` Alex Williamson
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=1444144278.4059.35.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=Bharat.Bhushan@freescale.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pranavkumar@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).