All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Espen Skoglund <espen.skoglund@netronome.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Make new PCI device probe work with older hypervisors
Date: Mon, 07 Jul 2008 15:37:23 +0100	[thread overview]
Message-ID: <C497E8B3.23A34%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <18546.8229.793718.252754@gargle.gargle.HOWL>

As long as setups with older dom0 kernels do not suffer feature regression
when only the hypervisor is upgraded, I think it's fine.

 -- Keir

On 7/7/08 14:54, "Espen Skoglund" <espen.skoglund@netronome.com> wrote:

> For older dom0 kernels Xen will not know which PCI devices exists in
> the system.  This has the implication that
> 
>   a) IOMMU device assignment will not work, and
>   b) assigning MSI interrupts will not work.
> 
> The only way to avoid these "limitations" is to either perform PCI bus
> enumaration at startup or to create new pci_devs on deamand (e.g.,
> when guest wants to assign an MSI to a new unknown device).
> 
> Given that MSIs (and to a lesser extent IOMMUs) have only recently
> found their way into Xen, I'm not sure whether it calls for having to
> support a-few-weeks-old dom0s in Xen.
> 
> eSk
> 
> 
> [Keir Fraser]
>> Thanks. One thing also -- do old dom0 kernels work with new Xen
>> (i.e., do we have compatibility both ways)?
> 
>>  -- Keir
> 
>> On 7/7/08 13:40, "Espen Skoglund" <espen.skoglund@netronome.com> wrote:
> 
>>> Be a bit more forgiving if hyervisor does not implement the
>>> manage_pci_add hypercall.
>>> 
>>> Signed-off-by: Espen Skoglund <espen.skoglund@netronome.com>
>>> 
>>> --
>>> diff -r bb937c2f7382 drivers/xen/core/pci.c
>>> --- a/drivers/xen/core/pci.c Fri Jul 04 17:55:07 2008 +0100
>>> +++ b/drivers/xen/core/pci.c Mon Jul 07 13:34:32 2008 +0100
>>> @@ -19,7 +19,7 @@
>>> manage_pci.devfn = pci_dev->devfn;
>>> 
>>> r = HYPERVISOR_physdev_op(PHYSDEVOP_manage_pci_add, &manage_pci);
>>> - if (r)
>>> + if (r && r != -ENOSYS)
>>> return r;
>>> 
>>> r = pci_bus_probe(dev);
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
> 
> 
> 

  reply	other threads:[~2008-07-07 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 12:40 [PATCH] Make new PCI device probe work with older hypervisors Espen Skoglund
2008-07-07 12:55 ` Keir Fraser
2008-07-07 13:54   ` Espen Skoglund
2008-07-07 14:37     ` Keir Fraser [this message]
2008-07-07 14:54       ` Espen Skoglund
2008-07-07 14:57         ` Keir Fraser
2008-07-07 15:04           ` Espen Skoglund
2008-07-07 15:07             ` Keir Fraser
2008-07-07 15:11               ` Espen Skoglund

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=C497E8B3.23A34%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=espen.skoglund@netronome.com \
    --cc=xen-devel@lists.xensource.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 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.