From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
yu.zhao@intel.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: [DOM0 KERNELS] pciback: Fix SR-IOV VF passthrough
Date: Mon, 1 Mar 2010 11:20:26 -0500 [thread overview]
Message-ID: <20100301162026.GD7881@phenom.dumpdata.com> (raw)
In-Reply-To: <4B8B91AF0200007800031C75@vpn.id2.novell.com>
On Mon, Mar 01, 2010 at 09:06:39AM +0000, Jan Beulich wrote:
> >>> Keir Fraser <keir.fraser@eu.citrix.com> 26.02.10 18:25 >>>
> >Vendor/device and BAR fields in a VF's host-level PCI config space are dummy
> >and must always be virtualised/emulated. Implement this in pciback by always
> >extracting the values installed in dom0 kernel's own PCI structures, rather
> >than interrogating the underlying PCI config space directly.
> >
> >AFAIK, this patch should apply to any kernel that implements pciback: That
> >includes pv_ops, SLES, and the XS/XCP kernels. It should be applied to all
> >of them. It is already applied to linux-2.6.18-xen.hg as 998:693c40564c8d.
> >
> >Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
>
> Some parts of this we had been given by Intel, but some were also
> implemented differently there. I'm reproducing the patch below, and
Could attach it as an attachment? I get:
patching file drivers/xen/pciback/conf_space_header.c
patch: **** malformed patch at line 139: *data)
next prev parent reply other threads:[~2010-03-01 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 17:25 [DOM0 KERNELS] pciback: Fix SR-IOV VF passthrough Keir Fraser
2010-02-26 20:51 ` Konrad Rzeszutek Wilk
2010-03-01 9:06 ` Jan Beulich
2010-03-01 9:45 ` Keir Fraser
2010-03-01 16:20 ` Konrad Rzeszutek Wilk [this message]
2010-03-01 16:49 ` Keir Fraser
2010-03-01 19:12 ` Konrad Rzeszutek Wilk
2010-03-01 22:21 ` Keir Fraser
2010-03-02 9:33 ` Jan Beulich
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=20100301162026.GD7881@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.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.