From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dario Faggioli <raistlin@linux.it>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Issue with PCI-passthrough and pvops
Date: Wed, 19 Oct 2011 21:42:29 -0400 [thread overview]
Message-ID: <20111020014229.GA6680@phenom.dumpdata.com> (raw)
In-Reply-To: <CAAWQectmCtkgvi7ZpQZYKxCSPZ7sk14UdCYAY2PgQjKSWEDBqw@mail.gmail.com>
> > I would recommend you take a look at the probe function and figure out why
> > it can't reserve that region. And easy way to figure that out is to
> > boot the guest and look in /proc/iomem and see what is in the df30000-e32ffffff
> > region. Perhaps something else is overlapping it?
> >
> I might be wrong, but it doesn't seem quite so to me:
>
> # cat /proc/iomem
> 00000000-0000ffff : reserved
> 00010000-0009ffff : System RAM
> 000a0000-000fffff : reserved
> 000f0000-000fffff : System ROM
> 00100000-1fffffff : System RAM
> 01000000-01b88b4b : Kernel code
> 01b88b4c-02352a7f : Kernel data
> 02652000-02ee6fff : Kernel bss
> 20000000-bf698fff : Unusable memory
> bf6af000-bf6cdfff : ACPI Tables
> d58f8000-d58fbfff : 0000:00:00.0
> d5900000-d597ffff : 0000:00:00.0
> df200000-e71fffff : 0000:00:00.0
> 100000000-1000fffff : System RAM
>
> The probe function is huge... But I'll se if I can find the time to take
> a look at it in the next days...
Hmmm. Instrumenting resources.c (__request_resource) might be the way to
figure out where it chokes on.
next prev parent reply other threads:[~2011-10-20 1:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 15:36 Issue with PCI-passthrough and pvops Dario Faggioli
2011-10-17 16:40 ` Konrad Rzeszutek Wilk
2011-10-18 23:54 ` Dario Faggioli
2011-10-19 1:10 ` Konrad Rzeszutek Wilk
2011-10-19 7:40 ` Ian Campbell
2011-10-19 13:46 ` Dario Faggioli
2011-10-19 14:10 ` Konrad Rzeszutek Wilk
2011-10-19 17:27 ` Dario Faggioli
2011-10-20 1:42 ` Konrad Rzeszutek Wilk [this message]
2011-10-19 7:39 ` Ian Campbell
2011-10-19 16:12 ` Dario Faggioli
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=20111020014229.GA6680@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=raistlin@linux.it \
--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.