From: Simon Horman Subject: Re: [PATCH] [IOEMU] Fix wrong INTx for pass-through device Date: Thu, 31 Dec 2009 18:56:17 +1100 Message-ID: <20091231075616.GA29386@verge.net.au> References: <8686c3cd0912280633u27839f56k74abcd73fb041e4@mail.gmail.com> <4B394BCB.30607@intel.com> <20091229020128.GG10172@verge.net.au> <8686c3cd0912290051t76c771fdq15314f25287d3973@mail.gmail.com> <4B39C4DE.8050103@intel.com> <8686c3cd0912300020n1284bf0ele160985f5118aad4@mail.gmail.com> <20091231043241.GA30174@verge.net.au> <4B3C3FC3.40301@intel.com> <20091231064531.GB12237@verge.net.au> <4B3C5585.9040600@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4B3C5585.9040600@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Zhai, Edwin" Cc: Tom Rotenberg , Xen Developers , Ian Jackson List-Id: xen-devel@lists.xenproject.org On Thu, Dec 31, 2009 at 03:40:53PM +0800, Zhai, Edwin wrote: > Regarding this patch, I think we need move the pci_read_intx up, or > I would get compilation error with the reference in > pt_irqpin_reg_init. Ok, I'll fix that. > I have tested this path, both linux and windows can work, so Let's > use physical PIN policy. Could you pls. send a new patch to Ian > Jakson in a new thread, so that he can check in it after holiday > without tracking this long discussion:) Sure. > BTW, could you pls. tell me how to assign the multiple function > device to guest as it is? Setting the same virtual PCI slot? Single-function assignment works like this: pci=00:1d.0 Multi-function extends that syntax by allowing multiple functions to be specified. For example: pci=0:1d.0,1 Details of other incantations are detailed at: http://wiki.xensource.com/xenwiki/BDFNotation