All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weidong Han <weidong.han@intel.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: RE: xl fails to work with some command
Date: Tue, 31 Aug 2010 15:07:08 +0800	[thread overview]
Message-ID: <4C7CAA1C.1030902@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1008271151110.2545@kaball-desktop>

Stefano Stabellini wrote:
> On Fri, 27 Aug 2010, Weidong Han wrote:
>   
>>>>> Yes, give a look at libxl_device_pci_reset: first libxl tries to use the
>>>>> pciback sysfn node "do_flr", but if it is not present it will use the
>>>>> standard linux sysfs "reset" node.
>>>>> Please note that on pvops kernels the do_flr node is not present (but it
>>>>> is present on both XCP and XCI kernels) while the reset node points to
>>>>> pci_reset_function.
>>>>>       
>>>>>           
>>>> <hint>I am all up for receiving the patches from XCP/XCI for this</hint>
>>>>
>>>>     
>>>>         
>>> I think that using the standard linux reset mechanism is a better way to
>>> handle this as oppose to have our own do_flr method.
>>>   
>>>       
>> Pls note that there are some specific FLR functions for graphics 
>> pass-through. They should be ported to xl.
>>
>>     
>  
> As stated above, xl doesn't know how to FLR a device, the dom0 kernel
> provides a way to do it.
> XCP kernels have pciback do_flr that has all the HW specific FLR
> functions you are referring to AFAIK, but the pvops kernel, that uses
> the standard reset node, does not.
>
>   
So it should implement specific FLRs in pciback like XCP/XCI.

Regards,
Weidong

  reply	other threads:[~2010-08-31  7:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19  5:51 xl fails to work with some command Zhang, Yang Z
2010-08-23  7:16 ` Zhang, Yang Z
2010-08-23 10:12   ` Stefano Stabellini
2010-08-23 13:32     ` Zhang, Yang Z
2010-08-24 13:21       ` Gianni Tedesco
2010-08-25  1:21         ` Zhang, Yang Z
2010-08-25  2:31           ` Weidong Han
2010-08-25 15:50       ` Stefano Stabellini
2010-08-26  6:10         ` Weidong Han
2010-08-26 12:17           ` Stefano Stabellini
2010-08-26 13:50             ` Konrad Rzeszutek Wilk
2010-08-26 15:47               ` Stefano Stabellini
2010-08-27  0:30                 ` Weidong Han
2010-08-27 10:53                   ` Stefano Stabellini
2010-08-31  7:07                     ` Weidong Han [this message]
2010-08-31  9:40                       ` Stefano Stabellini
2010-08-31 10:07                         ` Ian Campbell
2010-08-31 13:04                           ` Weidong Han

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=4C7CAA1C.1030902@intel.com \
    --to=weidong.han@intel.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yang.z.zhang@intel.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.