From: Jambunathan K <jambunathan@netxen.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: PCI Passthru: fn0 exported but not fn1
Date: Mon, 27 Aug 2007 20:57:49 +0530 [thread overview]
Message-ID: <46D2ED75.1000906@netxen.com> (raw)
In-Reply-To: <C2F8AAE2.CE94%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 27/8/07 15:08, "Jambunathan K" <jambunathan@netxen.com> wrote:
>
>> I confirming that this is a regression from xen304 to xen310. (I
>> verified just the 'BACKEND_PASS' config)
>>
>> I had cursorily looked at pciback and pcifront code changes between
>> xen304 to xen310. My not so discerning eye couldn't catch any
>> differences that do matter.
>>
>> For now I have reverted my working tree to Xen-304. I would appreciate
>> if you could provide a patch that addresses this issue in Xen310.
>
> What is the regression? That pcifront does not scan fn!=0 if fn==0 is empty?
>
> -- Keir
>
Behaviorally speaking, I can export *just* fn1 on Xen304. But I can't
export *just* fn1 on Xen310.
I am calling this difference in behaviour a regression.
Jambunathan K.
next prev parent reply other threads:[~2007-08-27 15:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 19:04 PCI Passthru: fn0 exported but not fn1 Jambunathan K
2007-08-24 14:42 ` Keir Fraser
2007-08-24 14:58 ` Jambunathan K
2007-08-24 15:01 ` Keir Fraser
2007-08-26 16:19 ` Jambunathan K
2007-08-27 14:08 ` Jambunathan K
2007-08-27 15:22 ` Keir Fraser
2007-08-27 15:27 ` Jambunathan K [this message]
2007-08-27 15:40 ` Keir Fraser
2007-08-27 15:58 ` Jambunathan K
2007-08-27 16:14 ` Keir Fraser
2007-08-27 16:34 ` Jambunathan K
2007-08-27 16:42 ` Keir Fraser
[not found] <C2FA6F3A.D05F%keir@xensource.com>
2007-08-29 14:18 ` Jambunathan K
2007-08-29 14:26 ` Keir Fraser
2007-08-30 10:11 ` Jambunathan K
2007-08-30 10:19 ` Keir Fraser
2007-08-30 14:45 ` Jambunathan K
2007-08-29 18:27 ` Stefan Neuwirth
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=46D2ED75.1000906@netxen.com \
--to=jambunathan@netxen.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=sanjeev@netxen.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.