From: Rusty Russell <rusty@rustcorp.com.au>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@osdl.org>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, experimental] i386 Allow the fixmap to be relocated at boot time
Date: Sat, 06 Aug 2005 22:48:49 +1000 [thread overview]
Message-ID: <1123332529.17152.47.camel@localhost.localdomain> (raw)
In-Reply-To: <42F3FFBA.3040009@vmware.com>
On Fri, 2005-08-05 at 17:09 -0700, Zachary Amsden wrote:
> Also, it seems reasonable that people may want to poke holes in high
> linear space for other hypervisor projects, research, or performance
> reasons without having to build a custom sub-architecture just for
> that. So I think there is some benefit to making the hole size a
> general configurable option (with defaults depending on the sub-arch you
> select).
qemu-fast needs a kernel with __FIXADDR_TOP 0xa7fff000, and PAGE_OFFSET
0x90000000. I used to continually patch my kernels, but these days I
just run full qemu and take the speed hit. If this was easier, it would
be really nice to have that speed back.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2005-08-06 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 23:28 [PATCH,experimental] i386 Allow the fixmap to be relocated at boot time Zachary Amsden
2005-08-05 23:46 ` [PATCH, experimental] " Chris Wright
2005-08-06 0:09 ` Zachary Amsden
2005-08-06 0:22 ` Chris Wright
2005-08-06 12:48 ` Rusty Russell [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=1123332529.17152.47.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.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