From: Jambunathan K <jambunathan@netxen.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Stefan Neuwirth <neuwirt-xen-devel@trillian.hd.shuttle.de>,
Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: PCI Passthru: fn0 exported but not fn1
Date: Thu, 30 Aug 2007 20:15:52 +0530 [thread overview]
Message-ID: <46D6D820.7000601@netxen.com> (raw)
In-Reply-To: <C2FC583D.15073%keir@xensource.com>
>> Oh, that is pretty gross. I guess we can just comment out asm-generic's
>> definition of that macro, as pretty much every architecture is defining it
>> for itself anyway.
>>
>> Can you try that? Just have it defined to 1 in
>> asm-x86_64/mach-xen/asm/pci.h, and comment out the definition in
>> asm-generic/pci.h.
>>
>> If that works I'll apply the fix to our tree with appropriate comments.
>>
>> This isn't going to fly upstream, or probably even in vendor kernels, so
>> longer term the dummy device in pciback is probably going to be required.
The changes work well.
Please include these changes in the next stable release of Xen31 tree.
Jambunathan K.
next prev parent reply other threads:[~2007-08-30 14:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C2FA6F3A.D05F%keir@xensource.com>
2007-08-29 14:18 ` PCI Passthru: fn0 exported but not fn1 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 [this message]
2007-08-29 18:27 ` Stefan Neuwirth
2007-08-23 19:04 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
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
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=46D6D820.7000601@netxen.com \
--to=jambunathan@netxen.com \
--cc=keir@xensource.com \
--cc=neuwirt-xen-devel@trillian.hd.shuttle.de \
--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.