From: "Andres Lagar-Cavilla" <andres@lagarcavilla.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xensource.com, tim@xen.org, keir.xen@gmail.com,
jbeulich@suse.com, adin@gridcentric.ca
Subject: Re: RFC: AMD support for paging
Date: Tue, 14 Feb 2012 13:33:27 -0800 [thread overview]
Message-ID: <d9040b615b8e9eb4f7c68dd35709a090.squirrel@webmail.lagarcavilla.org> (raw)
In-Reply-To: <20120214212655.GA23901@aepfle.de>
> On Tue, Feb 14, Andres Lagar-Cavilla wrote:
>
>> > On Tue, Feb 14, Andres Lagar-Cavilla wrote:
>> >
>> >> Finally, the triple fault.
>> >
>> > "Me too!"
>> > Thats how far I got as well in my attempt.
>>
>> Hey, awesome you're trying this out so quickly :)
>
> I meant my attempt a few weeks ago.
>
>> If you have a couple cycles...
>
> Does your pager do anything? I just get this:
>
> xc: detail: xenpaging init
> xc: detail: watching '/local/domain/1/memory/target-tot_pages'
> xc: detail: max_pages = 263168
> xc: detail: starting /usr/lib/xen/bin/xenpaging for domain_id 1 with
> pagefile /dev/shm/pagefile-sles11sp2_full_xenpaging
> xc: detail: confirming startup in /local/domain/1/xenpaging/state
> xc: detail: Got event from xenstore
> xc: detail: path '@releaseDomain' token '1'
> xc: detail: Got event from evtchn
> xc: detail: Got event from xenstore
> xc: detail: path '/local/domain/1/memory/target-tot_pages' token ''
> xc: detail: new target_tot_pages 59904
> xc: detail: Got event from Xen
> xc: detail: Need to evict 202213 pages to reach 59904 target_tot_pages
> xc: error: Error mapping page 20201 (22 = Invalid argument): Internal
> error
Those are the kinds of errors I was getting until I finished my patch.
Basically, the p2m gets confused and returns p2m_mmio_dm as the type for
anything it doesn't understand. If you end up giving my patch a spin, let
me know if it gets you past that hump.
Andres
> xc: debug: hypercall buffer: total allocations:9 total releases:9
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
> xc: debug: hypercall buffer: cache current size:2
> xc: debug: hypercall buffer: cache hits:7 misses:2 toobig:0
>
>
> Olaf
>
next prev parent reply other threads:[~2012-02-14 21:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 19:05 RFC: AMD support for paging Andres Lagar-Cavilla
2012-02-14 19:22 ` Olaf Hering
2012-02-14 19:35 ` Andres Lagar-Cavilla
2012-02-14 21:26 ` Olaf Hering
2012-02-14 21:33 ` Andres Lagar-Cavilla [this message]
2012-02-14 21:43 ` Olaf Hering
2012-02-15 9:18 ` Olaf Hering
2012-02-15 14:59 ` Andres Lagar-Cavilla
2012-02-15 12:09 ` Wei Wang
2012-02-15 15:14 ` Andres Lagar-Cavilla
2012-02-15 15:33 ` Wei Wang
2012-02-15 16:06 ` Andres Lagar-Cavilla
2012-02-15 17:02 ` Tim Deegan
2012-02-15 17:09 ` Andres Lagar-Cavilla
2012-02-15 17:34 ` Tim Deegan
2012-02-16 15:47 ` Wei Wang
2012-02-16 10:17 ` Wei Wang
2012-02-16 14:36 ` Andres Lagar-Cavilla
2012-02-16 2:31 ` Hongkaixing
2012-02-16 5:19 ` Andres Lagar-Cavilla
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=d9040b615b8e9eb4f7c68dd35709a090.squirrel@webmail.lagarcavilla.org \
--to=andres@lagarcavilla.org \
--cc=adin@gridcentric.ca \
--cc=jbeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=olaf@aepfle.de \
--cc=tim@xen.org \
--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).