All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] upgraded mmap patches
Date: Sun, 09 Jan 2005 21:39:42 +0500	[thread overview]
Message-ID: <crrmls$eeh$1@sea.gmane.org> (raw)
In-Reply-To: aec7e5c3050108154835a8938d@mail.gmail.com

Magnus Damm wrote:

> Hi All,
> 
> I have just finished upgrading the CONFIG_MMU_MAP (aka mmap) patches
> written by Piotrek. I have only tested to build the code with
> --target-list=i386-softmmu and only on x86 hosts running Linux. I am
> able to run Win XP SP2 as guest both with and without mmap
> acceleration with the patch.
> 
> The changes are not many since the last release by Piotrek, I just
> made sure the code applied to CVS of today and yeah, I added some
> basic code to support quad-word memory access. It is totally untested
> and probably broken right now. Someone please look at part4 of the
> patch and verify that I read 32-bit words the right way.
> 
> Sorry PowerPC folks, no ppc host support yet. I will port up the ppc
> host patches after someone has fixed so ppc compiles cleanly...
> 
> The first three parts are simply upgraded versions of the files
> v1-part[1-3].patch.gz that Piotrek posted to the list around a month
> ago. Part4 contains changes by me.
> 
> Enjoy, please report back to the list with problems and benchmarks!

Is a new patched qemu really supposed to be much slower than the original in
the case when /proc/sys/vm/max_map_count doesn't contain a number that's
big enough to enable acceleration?

-- 
Alexander E. Patrakov

  reply	other threads:[~2005-01-09 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 23:48 [Qemu-devel] [PATCH] upgraded mmap patches Magnus Damm
2005-01-09 16:39 ` Alexander E. Patrakov [this message]
2005-01-09 17:31   ` [Qemu-devel] " Magnus Damm
2005-01-11 16:15     ` [Qemu-devel] Benchmark (was: Re: [PATCH] upgraded mmap patches) Alexander E. Patrakov

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='crrmls$eeh$1@sea.gmane.org' \
    --to=patrakov@ums.usu.ru \
    --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 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.