From: Richard Henderson <rth@twiddle.net>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
freebsd-emulation@freebsd.org,
Andreas Tobler <andreast@fgznet.ch>,
qemu-devel@nongnu.org, Toni <tonygio04@gmail.com>
Subject: Re: [Qemu-devel] qemu git head 20100323 on FreeBSD - qemu-devel port update for testing
Date: Tue, 30 Mar 2010 12:42:03 -0700 [thread overview]
Message-ID: <4BB2540B.90704@twiddle.net> (raw)
In-Reply-To: <20100330191629.GA95521@triton8.kn-bremen.de>
On 03/30/2010 12:16 PM, Juergen Lock wrote:
> I first tried to replace the endaddr in the !h2g_valid(endaddr) case with
> ((abi_ulong)1 << L1_MAP_ADDR_SPACE_BITS) - 1
> if TARGET_ABI_BITS > L1_MAP_ADDR_SPACE_BITS (which comes from the condition
> of the assert in page_set_flags() that was triggered on the ~0ul value),
> but that caused the qemu process to grow into swap and made the box
> usuable when that code was reached and I had to kill qemu. (The box has
> 8 GB RAM.) And so I thought just leaving that page range unprotected
> if only the start address is valid was the lesser evil...
What's are the real arguments to the page_set_flags that causes things
to go into swap? I can't imagine the range really being so large that
it causes massive allocation within that function...
r~
next prev parent reply other threads:[~2010-03-30 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 20:44 [Qemu-devel] qemu git head 20100323 on FreeBSD - qemu-devel port update for testing Juergen Lock
2010-03-25 21:10 ` [Qemu-devel] " Brandon Gooch
2010-03-30 18:04 ` [Qemu-devel] " Blue Swirl
2010-03-30 19:16 ` Juergen Lock
2010-03-30 19:42 ` Richard Henderson [this message]
2010-03-30 20:09 ` Juergen Lock
2010-03-30 20:33 ` Richard Henderson
2010-03-30 20:45 ` Juergen Lock
2010-03-30 21:57 ` Juergen Lock
2010-03-30 20:42 ` Juergen Lock
2010-03-30 20:56 ` Richard Henderson
2010-03-30 19:54 ` Blue Swirl
2010-03-30 20:17 ` Juergen Lock
2010-04-01 11:59 ` Paul Brook
2010-04-01 17:06 ` Juergen Lock
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=4BB2540B.90704@twiddle.net \
--to=rth@twiddle.net \
--cc=andreast@fgznet.ch \
--cc=blauwirbel@gmail.com \
--cc=freebsd-emulation@freebsd.org \
--cc=nox@jelal.kn-bremen.de \
--cc=qemu-devel@nongnu.org \
--cc=tonygio04@gmail.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.