From: Andrew May <acmay@acmay.homeip.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: 4xx TLB fixes
Date: Tue, 9 Dec 2008 08:19:05 -0800 [thread overview]
Message-ID: <20081209081905.0936fa52@acmay.homeip.net> (raw)
In-Reply-To: <20081208001735.0244e189@acmay.homeip.net>
On Mon, 8 Dec 2008 00:17:35 -0800
Andrew May <acmay@acmay.homeip.net> wrote:
> I don't all the details of the 4xx MMU stuff, but I think these 2
> fixes for the tlb handling are correct.
No the patch isn't up to date. But I just tried to merge it and things
have gone backwards for me.
And I am kicking myself for not saving off logs to compare how things
are going wrong.
It seems that inside linux "setup_arg_pages()" calls
"move_page_tables()".
And when the code tries to return back to setup_arg_pages(), it fails
to find the kernel code that was just there.
The get_phys_addr_code() does a cpu_abort there, but I don't see that
the MMU code is being checked there.
I haven't been able to debug it too much more.
ps: I am not on the list so, please cc me.
prev parent reply other threads:[~2008-12-09 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 8:17 [Qemu-devel] 4xx TLB fixes Andrew May
2008-12-08 16:37 ` Andreas Färber
2008-12-09 16:19 ` Andrew May [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=20081209081905.0936fa52@acmay.homeip.net \
--to=acmay@acmay.homeip.net \
--cc=qemu-devel@nongnu.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 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).