All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Simon Horman <horms@verge.net.au>
Cc: Tom Rotenberg <tom.rotenberg@gmail.com>,
	Xen Developers <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] [IOEMU] Fix wrong INTx for pass-through device
Date: Thu, 31 Dec 2009 15:40:53 +0800	[thread overview]
Message-ID: <4B3C5585.9040600@intel.com> (raw)
In-Reply-To: <20091231064531.GB12237@verge.net.au>

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.

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:)

BTW, could you pls. tell me how to assign the multiple function device 
to guest as it is? Setting the same virtual PCI slot?
Thanks,


Simon Horman wrote:
> Yes, the ability to make assignments like that is the crux
> of the multi-function work that I did earlier in the year.
> And the idea of not always using INTA was to avoid the
> performance penalty of reusing the virtual GSI.
>
>   
>> If we can't do this now, I think option A is also good. Is any
>> specific reason that we change to C? Does some specific multiple
>> function driver assumes specific pin other than INTA?
>>     
>
> ... so A isn't such a good option (it was before and thats what was used).
> I think that I chose C when I added multi-function because it
> avoided introducing any incompatibility for single-function pass-through.
> But at this point I think C just introduces complexity, so I now prefer B.
>
>   
>> BTW, pls. send your patch in attachment as I couldn't get it from
>> your mail:(
>>     
>
> Sure.
>
>   

-- 
best rgds,
edwin

  reply	other threads:[~2009-12-31  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  7:04 [PATCH] [IOEMU] Fix wrong INTx for pass-through device Zhai, Edwin
2009-12-28  7:54 ` Simon Horman
2009-12-28 14:33 ` Tom Rotenberg
2009-12-29  0:22   ` Zhai, Edwin
2009-12-29  2:01     ` Simon Horman
2009-12-29  8:51       ` Tom Rotenberg
2009-12-29  8:59         ` Zhai, Edwin
2009-12-30  8:20           ` Tom Rotenberg
2009-12-31  4:32             ` Simon Horman
2009-12-31  6:08               ` Zhai, Edwin
2009-12-31  6:45                 ` Simon Horman
2009-12-31  7:40                   ` Zhai, Edwin [this message]
2009-12-31  7:56                     ` Simon Horman

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=4B3C5585.9040600@intel.com \
    --to=edwin.zhai@intel.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=horms@verge.net.au \
    --cc=tom.rotenberg@gmail.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.