From: 0bo0 <0.bugs.only.0@gmail.com>
To: Weidong Han <weidong.han@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem"
Date: Mon, 25 Jan 2010 08:17:35 -0800 [thread overview]
Message-ID: <c67eed301001250817o66c39940o2d234bcb040fd593@mail.gmail.com> (raw)
In-Reply-To: <4B5CF79A.6020002@intel.com>
hi,
On Sun, Jan 24, 2010 at 5:44 PM, Weidong Han <weidong.han@intel.com> wrote:
> I think this is not a bug. pls note ...
(snip)
Ack'd, even if the limitations are not fully understood:-/
> or you
> can set "pci-passthrough-strict-check no" in /etc/xen/xend-config.sxp and
> restart xend to loose the check in xend, but in this way you should be aware
> of potential issues (e.g. assigned device doesn't work).
sure. would it not be reasonable to have a similar config-file option
in xen 3.x -- with similar warnings etc -- as is done in 4.x? if all
that's required for a workaround is a patch similar to that above ...
thanks
next prev parent reply other threads:[~2010-01-25 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 1:32 follow up to a pciback "pv pci-passthrough co-assigned problem" mail ignored
2010-01-23 4:09 ` mail ignored
2010-01-23 12:30 ` Pasi Kärkkäinen
2010-01-23 16:40 ` mail ignored
2010-01-23 16:48 ` Pasi Kärkkäinen
2010-01-23 17:36 ` mail ignored
2010-01-23 17:43 ` Pasi Kärkkäinen
2010-01-23 17:45 ` mail ignored
2010-01-23 17:54 ` mail ignored
2010-01-23 17:57 ` Pasi Kärkkäinen
2010-01-23 17:58 ` mail ignored
2010-01-23 18:15 ` mail ignored
2010-01-25 1:44 ` Weidong Han
2010-01-25 16:17 ` 0bo0 [this message]
2010-01-26 1:42 ` Weidong Han
2010-01-26 7:02 ` Pasi Kärkkäinen
2010-01-23 18:19 ` Keir Fraser
2010-01-26 6:50 ` 0bo0
2010-01-26 7:34 ` 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=c67eed301001250817o66c39940o2d234bcb040fd593@mail.gmail.com \
--to=0.bugs.only.0@gmail.com \
--cc=weidong.han@intel.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 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).