From: kraehe <kraehe@copyleft.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: uml 2.4 (32 bit) on skas 2.6 (64 bit) - add on
Date: Sat, 23 Apr 2005 20:40:32 +0200 [thread overview]
Message-ID: <20050423184032.GA17889@copyleft.de> (raw)
In-Reply-To: <20050423180314.GA17743@copyleft.de>
Moin Guru's,
I've just tried that, 2.4.30 with uml-2.4.28-bs2-pre11.patch works
on a 2.6.11.7-amd64 host without any SKAS patches. So TT mode is
fine. The 2.4.22 bug my UML runs when in SKAS reads as :
/*
* This is a long-lived spinlock. That's fine.
* There's no contention, because the page table
* lock only protects against kswapd anyway, and
* even if kswapd happened to be looking at this
* process we _want_ it to get stuck.
*/
if (address >= end)
BUG(); <-- Kernel panic: kernel BUG at memory.c:377!
spin_lock(&mm->page_table_lock);
flush_cache_range(mm, address, end);
tlb = tlb_gather_mmu(mm);
perhaps this old 2.4.22 code helps to point the problem with SKAS host
and newer 2.4.30 UML clients (/me hopes they are same problem ;-)
Bye Michael
--
mailto:kraehe@copyleft.de UNA:+.? 'CED+2+:::Linux:2.4.29'UNZ+1'
http://www.xml-edifact.org/ CETERUM CENSEO WINDOWS ESSE DELENDAM
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-04-23 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 18:03 [uml-devel] uml 2.4 (32 bit) on skas 2.6 (64 bit) kraehe
2005-04-23 18:40 ` kraehe [this message]
2005-04-24 14:09 ` [uml-devel] Re: uml 2.4 (32 bit) on skas 2.6 (64 bit) - add on Blaisorblade
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=20050423184032.GA17889@copyleft.de \
--to=kraehe@copyleft.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.