From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, ian.campbell@citrix.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
tim@xen.org, xen-devel@lists.xenproject.org,
ian.jackson@eu.citrix.com
Subject: Re: [PATCH v8 for-xen-4.5 2/2] dpci: Replace tasklet with an softirq (v8)
Date: Sun, 2 Nov 2014 16:09:45 -0400 [thread overview]
Message-ID: <20141102200945.GA31191@andromeda.dapyr.net> (raw)
In-Reply-To: <54520D3202000078000435FA@mail.emea.novell.com>
> > -void pci_release_devices(struct domain *d)
> > +int pci_release_devices(struct domain *d)
> > {
> > struct pci_dev *pdev;
> > u8 bus, devfn;
> > + int ret;
> >
> > spin_lock(&pcidevs_lock);
> > - pci_clean_dpci_irqs(d);
> > + ret = pci_clean_dpci_irqs(d);
> > + if ( ret == -ERESTART )
> > + {
> > + spin_unlock(&pcidevs_lock);
> > + return ret;
> > + }
> > while ( (pdev = pci_get_pdev_by_domain(d, -1, -1, -1)) )
> > {
> > bus = pdev->bus;
>
> Even if errors other than -ERESTART aren't possible right now, the
> code now looks like it is ignoring such. I think it would be better if
> you simply dropped the special casing of -ERESTART and propagated
> all errors here.
The will cause a regression. The pci_clean_dpci_irqs will
now return -EINVAL if the iommu is turned off - which will mean
that we won't be able to kill an HVM guest without passthrough.
I can do:
1). if ( ret && !(ret == -EINVAL || ret == -E..))
2). Or remove the various 'return -EINVAL' in the pci_clean_dpci_irqs
for the causes where IOMMU is off or there are no PCI passthrough
devices - and just make them return 0.
3). Leave it as is.
next prev parent reply other threads:[~2014-11-02 20:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 17:19 [PATCH v8 for-xen-4.5] Fix interrupt latency of HVM PCI passthrough devices Konrad Rzeszutek Wilk
2014-10-21 17:19 ` [PATCH v8 for-xen-4.5 1/2] dpci: Move from an hvm_irq_dpci (and struct domain) to an hvm_dirq_dpci model Konrad Rzeszutek Wilk
2014-10-23 8:58 ` Jan Beulich
2014-10-24 1:58 ` Konrad Rzeszutek Wilk
2014-10-24 9:49 ` Jan Beulich
2014-10-24 19:09 ` Konrad Rzeszutek Wilk
2014-10-27 9:25 ` Jan Beulich
2014-10-27 16:36 ` Konrad Rzeszutek Wilk
2014-10-27 16:57 ` Jan Beulich
2014-10-21 17:19 ` [PATCH v8 for-xen-4.5 2/2] dpci: Replace tasklet with an softirq (v8) Konrad Rzeszutek Wilk
2014-10-23 9:36 ` Jan Beulich
2014-10-24 1:58 ` Konrad Rzeszutek Wilk
2014-10-24 10:09 ` Jan Beulich
2014-10-24 20:55 ` Konrad Rzeszutek Wilk
2014-10-25 0:39 ` Konrad Rzeszutek Wilk
2014-10-27 9:36 ` Jan Beulich
2014-10-27 16:36 ` Konrad Rzeszutek Wilk
2014-10-27 9:32 ` Jan Beulich
2014-10-27 10:40 ` Andrew Cooper
2014-10-27 10:59 ` Jan Beulich
2014-10-27 11:09 ` Andrew Cooper
2014-10-27 11:24 ` Jan Beulich
2014-10-27 17:01 ` Konrad Rzeszutek Wilk
2014-10-27 17:36 ` Andrew Cooper
2014-10-27 18:00 ` Konrad Rzeszutek Wilk
2014-10-27 21:13 ` Konrad Rzeszutek Wilk
2014-10-28 10:43 ` Jan Beulich
2014-10-28 20:07 ` Konrad Rzeszutek Wilk
2014-10-29 8:28 ` Jan Beulich
2014-10-29 21:11 ` Konrad Rzeszutek Wilk
2014-10-30 9:04 ` Jan Beulich
2014-11-02 20:09 ` Konrad Rzeszutek Wilk [this message]
2014-11-03 8:46 ` Jan Beulich
2014-10-28 7:58 ` Jan Beulich
2014-10-28 7:53 ` 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=20141102200945.GA31191@andromeda.dapyr.net \
--to=konrad@darnok.org \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--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.