From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: Chris <tknchris@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
"xen-devel-bounces@lists.xensource.com"
<xen-devel-bounces@lists.xensource.com>
Subject: Re: pv_ops reassigndev for pci passthrough
Date: Fri, 29 Jan 2010 17:46:59 -0500 [thread overview]
Message-ID: <20100129224659.GA20092@phenom.dumpdata.com> (raw)
In-Reply-To: <OF7926313B.B07CFE8D-ON8525769A.005399D0-8525769A.00546A55@gdeb.com>
On Mon, Dec 28, 2009 at 10:22:02AM -0500, Michael D Labriola wrote:
> > As a hack you can eliminate the check in the Xend python code for this
> > and see how far you can go. Just remember that it is a hack :-)
>
> Might try this if I get a spare moment... just to see what happens ;-)
>
> > I had not ported it over. My thought was to write code in the pciback
> code
> > that would do this automatically (if BARs are found to be not BAR
> aligned).
> >
> > Thought I am unsure of why this was not explored - are there any
> badtechnical
> > reasons to make BARs page-aligned after the device has been enabled (and
> then
> > disabled)?
> >
> > I am taking aside the Linux kernel resources structs (request_resource
> > and its friends), which probabally will throw a fit.
>
> Yeah, I always kinda wondered why this wasn't done automatically by
> pciback. Having pciback do it would mean that even non-BAR aligned
> devices could be exported after booting and w/out specifying PCI IDs as
> kernel args. That would be one fewer issue to fix later in the
> upstreaming effort.
So this is actually implemented in the pvops kernel, but has a different
name: pci=resource_alignment=<BDF>
This is what you need to pass as bootup argument, for example:
xen-pciback.hide=(07:00.0)(08:05.0)(08:07.0)(08:07.2) pci=resource_alignment=08:05.0
prev parent reply other threads:[~2010-01-29 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 17:42 pv_ops reassigndev for pci passthrough Michael D Labriola
2009-12-23 18:28 ` Chris
2009-12-23 19:03 ` [Xen-devel] " Keir Fraser
2009-12-23 20:10 ` Michael D Labriola
2009-12-23 21:37 ` Keir Fraser
2009-12-28 14:27 ` Konrad Rzeszutek Wilk
2009-12-28 15:22 ` Michael D Labriola
2010-01-29 22:46 ` Konrad Rzeszutek Wilk [this message]
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=20100129224659.GA20092@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=mlabriol@gdeb.com \
--cc=tknchris@gmail.com \
--cc=xen-devel-bounces@lists.xensource.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.