From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Zhao, Yu" <yu.zhao@intel.com>, Wei Huang <wei.huang2@amd.com>
Cc: Simon Horman <horms@verge.net.au>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Status of SR-IOV for Xen?
Date: Wed, 21 Jan 2009 14:38:18 +0000 [thread overview]
Message-ID: <C59CE3DA.1AB7%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4975EBD3.4000100@intel.com>
Hopefully I will have MSI support fixed and check in by tomorrow. The issue
was not with Intel's locking changes to pci/msi, but with Jan Beulich's
changes to ACKTYPE_NONE/ACKTYPE_EOI handling of MSIs. I'm just doing some
testing of my fix now.
-- Keir
On 20/01/2009 15:20, "Zhao, Yu" <yu.zhao@intel.com> wrote:
> I'll respin those patches and resubmit them later. One thing is that
> SR-IOV depends on MSI/MSI-x but they are disabled as Keir said in thread
> 'x86: Disable MSI as it seems to be triggering ASSERT at irq.c:269'.
>
> Wei Huang wrote:
>> It is better not to duplicate the efforts if Yu Zhao is working on it.
>> Otherwise, I would be interested on it too.
>>
>> -Wei
>>
>> Simon Horman wrote:
>>> On Mon, Jan 19, 2009 at 11:13:37AM -0600, Wei Huang wrote:
>>>> Hi,
>>>>
>>>> Any further update on SR-IOV support for Xen? Are we going to include
>>>> this feature soon?
>>>
>>> I am also interested in this and would be willing to do some work
>>> on breaking out the patches to address Jan Beulich's concerns[1]
>>> about accreditation. And to bring the patches up to date with the most
>>> recent Linux patches. The main problem that I see with the latter
>>> that 2.6.18.8's PCI stack is now quite old, so using that as
>>> a target would be more work than for instance using the paravirt ops
>>> work that Jeremy Fitzhardinge has been working on.
>>>
>>> [1] http://lists.xensource.com/archives/html/xen-devel/2008-09/msg00965.html
>>>
>>> --
>>> Simon Horman
>>> VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
>>> H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
>>>
>>>
>>
>
next prev parent reply other threads:[~2009-01-21 14:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EADF0A36011179459010BDF5142A4575046C2B8E@pdsmsx502.ccr.corp.intel.com>
2009-01-15 3:09 ` Move some of the PCI device manage/control into pciback? Cui, Dexuan
2009-01-15 10:17 ` Shohei Fujiwara
2009-01-15 11:04 ` Keir Fraser
2009-01-16 6:18 ` Jiang, Yunhong
2009-01-16 8:07 ` Keir Fraser
2009-01-16 13:54 ` Espen Skoglund
2009-01-20 6:08 ` Jiang, Yunhong
2009-01-16 3:26 ` Jiang, Yunhong
2009-01-16 5:47 ` Shohei Fujiwara
2009-01-16 6:16 ` Jiang, Yunhong
2009-01-16 8:55 ` Shohei Fujiwara
2009-01-16 14:19 ` Espen Skoglund
2009-01-19 7:05 ` Shohei Fujiwara
2009-01-19 8:30 ` Keir Fraser
2009-01-19 17:13 ` Status of SR-IOV for Xen? Wei Huang
2009-01-20 1:15 ` Simon Horman
2009-01-20 14:43 ` Wei Huang
2009-01-20 15:20 ` Zhao, Yu
2009-01-21 14:38 ` Keir Fraser [this message]
2009-01-20 23:10 ` Simon Horman
2009-01-20 9:26 ` Move some of the PCI device manage/control into pciback? Shohei Fujiwara
2009-01-16 14:41 ` 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=C59CE3DA.1AB7%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=horms@verge.net.au \
--cc=wei.huang2@amd.com \
--cc=xen-devel@lists.xensource.com \
--cc=yu.zhao@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.