From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>,
"yu.zhao@intel.com" <yu.zhao@intel.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [DOM0 KERNELS] pciback: Fix SR-IOV VF passthrough
Date: Mon, 01 Mar 2010 09:45:26 +0000 [thread overview]
Message-ID: <C7B13D36.B8B3%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B8B91AF0200007800031C75@vpn.id2.novell.com>
On 01/03/2010 09:06, "Jan Beulich" <JBeulich@novell.com> wrote:
>> 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
> I would appreciate clarification on the differences in the bar_read()/
> bar_write()/rom_write() vs. read_dev_bar() modifications.
>
> In any case I would think that the command_write() change would
> be generally applicable.
I never saw the Intel patch before. It looks fine to me.
-- Keir
next prev parent reply other threads:[~2010-03-01 9:45 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 [this message]
2010-03-01 16:20 ` Konrad Rzeszutek Wilk
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=C7B13D36.B8B3%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=jeremy@goop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).