[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <51137B4A02000078000BCB9F@nat28.tlf.novell.com>
Date: Thu, 07 Feb 2013 09:00:42 +0000
From: "Jan Beulich" <JBeulich@...e.com>
To: "Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>
Cc: "xen-devel" <xen-devel@...ts.xen.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] xen-pciback: notify hypervisor about devices
intended to be assigned to guests
>>> On 06.02.13 at 18:12, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
>> + if (pci_find_capability(dev, PCI_CAP_ID_MSIX)) {
>> + struct physdev_pci_device ppdev = {
>> + .seg = pci_domain_nr(dev->bus),
>> + .bus = dev->bus->number,
>> + .devfn = dev->devfn
>> + };
>> + int err = HYPERVISOR_physdev_op(PHYSDEVOP_release_msix,
>> + &ppdev);
>> +
>> + if (err)
>> + dev_warn(&dev->dev, "MSI-X release failed (%d)\n",
>> + err);
>> + }
>
> Perhaps it should be more off:
>
> if (err) {
> if (err == -ENOSYS)
> dev_info(&dev->dev,"MSI-X release
> hypercall not supported.");
> else
> dev_warn(&dev->dev, "MSI-X release failed (%d)\n",
> err);
>
Why would you want to special case this? The more that _really_
old hypervisors returned -EINVAL instead of -ENOSYS here?
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists