From: "Xu, Quan" <quan.xu@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "dario.faggioli@citrix.com" <dario.faggioli@citrix.com>,
"Wu, Feng" <feng.wu@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v9 3/3] VT-d: Fix vt-d Device-TLB flush timeout issue
Date: Sun, 10 Apr 2016 14:28:31 +0000 [thread overview]
Message-ID: <945CA011AD5F084CBEA3E851C0AB28894B887E26@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <5703A5EA02000078000E318B@prv-mh.provo.novell.com>
On April 05, 2016 5:48pm, Jan Beulich <JBeulich@suse.com> wrote:
> >>> On 01.04.16 at 16:47, <quan.xu@intel.com> wrote:
> > +static void dev_invalidate_iotlb_timeout(struct iommu *iommu, u16 did,
> > + u16 seg, u8 bus, u8 devfn)
> {
> > + struct domain *d = NULL;
> > + struct pci_dev *pdev;
> > +
> > + if ( test_bit(did, iommu->domid_bitmap) )
> > + d = rcu_lock_domain_by_id(iommu->domid_map[did]);
> > +
> > + if ( d == NULL )
> > + return;
>
> This should be accompanied by a comment explaining why returning here
> without indicating any error is okay.
>
I'd say:
"The domain has been freed, and the device no longer belongs to this domain."
> > + {
> > + ASSERT(pdev->domain);
> > + list_del(&pdev->domain_list);
> > + pdev->domain = NULL;
> > + pci_hide_existing_device(pdev);
> > + break;
> > + }
> > + }
> > +
> > + pcidevs_unlock();
> > +
> > + if ( !is_hardware_domain(d) )
> > + domain_crash(d);
>
> else printk();
>
As I mentioned in commit log "If impacted domain is hardware domain, just throw out a warning (done in queue_invalidate_wait).",
I am not sure whether we really need a printk() at this point or not.
> > @@ -251,11 +303,13 @@ int qinval_device_iotlb(struct iommu *iommu, }
> >
> > int qinval_device_iotlb_sync(struct iommu *iommu,
> > - u32 max_invs_pend, u16 sid, u16 size, u64 addr)
> > + u32 max_invs_pend, u16 did, u16 seg, u8 bus, u8 devfn, u16 size,
> > + u64 addr)
> > {
> > + u16 sid = PCI_BDF2(bus, devfn);
>
> Pointless local variable (but being a matter of taste, the VT-d maintainers will
> have the final say).
>
I will drop this local variable.
> > --- a/xen/include/xen/pci.h
> > +++ b/xen/include/xen/pci.h
> > @@ -116,6 +116,7 @@ const unsigned long *pci_get_ro_map(u16 seg); int
> > pci_add_device(u16 seg, u8 bus, u8 devfn,
> > const struct pci_dev_info *, nodeid_t node); int
> > pci_remove_device(u16 seg, u8 bus, u8 devfn);
> > +void pci_hide_existing_device(struct pci_dev *pdev);
> > int pci_ro_device(int seg, int bus, int devfn); int
> > pci_hide_device(int bus, int devfn);
>
> Please move the addition here.
>
Agreed.
Quan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-10 14:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 14:47 [PATCH v9 0/3] VT-d Device-TLB flush issue Quan Xu
2016-04-01 14:47 ` [PATCH v9 1/3] VT-d: add a command line parameter for Queued Invalidation Quan Xu
2016-04-05 9:09 ` Jan Beulich
2016-04-07 1:49 ` Xu, Quan
2016-04-07 1:51 ` Tian, Kevin
2016-04-01 14:47 ` [PATCH v9 2/3] VT-d: wrap a _sync version for all VT-d flush interfaces Quan Xu
2016-04-05 9:35 ` Jan Beulich
2016-04-07 7:44 ` Xu, Quan
2016-04-07 15:28 ` Jan Beulich
2016-04-08 2:20 ` Xu, Quan
2016-04-11 7:25 ` Tian, Kevin
2016-04-11 9:07 ` Xu, Quan
2016-04-11 6:52 ` Tian, Kevin
2016-04-11 8:01 ` Xu, Quan
2016-04-01 14:47 ` [PATCH v9 3/3] VT-d: Fix vt-d Device-TLB flush timeout issue Quan Xu
2016-04-05 9:47 ` Jan Beulich
2016-04-10 14:28 ` Xu, Quan [this message]
2016-04-11 16:17 ` Jan Beulich
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=945CA011AD5F084CBEA3E851C0AB28894B887E26@SHSMSX101.ccr.corp.intel.com \
--to=quan.xu@intel.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=feng.wu@intel.com \
--cc=kevin.tian@intel.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 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).