From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Slutz, Donald Christopher" <dslutz@verizon.com>
Cc: Steve Freitas <sflist@ihonk.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: PCI hole resize support for 4.5? If not, workaround?
Date: Wed, 29 Oct 2014 16:25:43 -0400 [thread overview]
Message-ID: <20141029202543.GM3424@laptop.dumpdata.com> (raw)
In-Reply-To: <A3CD31A5D207064088A18AC2AF7B5DC6C2517001@MIA20725MBX891B.apps.tmrk.corp>
On Wed, Oct 29, 2014 at 01:33:56PM +0000, Slutz, Donald Christopher wrote:
> On 10/21/14 13:33, Steve Freitas wrote:
> > On 10/21/2014 6:14, Don Slutz wrote:
> >> On 10/20/14 13:14, Steve Freitas wrote:
> >>> Sure would be nice to see this problem fixed for good.
> >>
> >> The change to 4.5 is not a complete fix, but a good 1st step.
> >
> > If you don't mind, could you describe the next steps? Might be worth
> > adding them as a suggested roadmap to bug #28.
> >
>
> I am not sure of the next steps. I do know that the code in QEMU
> traditional
> would need to be understood. Also looking through the mailing list
> archives for details on why this was not up-stream can help.
Perhaps making e820_hole work with HVM guests? That way your guests'
E820 looks like the host - which can help quite much with
finicky PCI devices.
>
> -Don Slutz
>
> > Steve
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-10-29 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 6:17 PCI hole resize support for 4.5? If not, workaround? Steve Freitas
2014-10-20 13:06 ` Don Slutz
2014-10-20 17:14 ` Steve Freitas
2014-10-21 13:14 ` Don Slutz
2014-10-21 17:33 ` Steve Freitas
2014-10-29 13:33 ` Slutz, Donald Christopher
2014-10-29 20:25 ` 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=20141029202543.GM3424@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dslutz@verizon.com \
--cc=sflist@ihonk.com \
--cc=xen-devel@lists.xen.org \
/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.