From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@redhat.com>, aliguori@us.ibm.com
Subject: [Qemu-devel] Re: [PATCH] remove smaller slots if registering a bigger one
Date: Wed, 11 Feb 2009 17:47:44 +0100 [thread overview]
Message-ID: <49930130.5050409@siemens.com> (raw)
In-Reply-To: <4992EF12.3000103@redhat.com>
Avi Kivity wrote:
> Jan Kiszka wrote:
>>> Which is fine. I'd prefer it to be here, so we can analyse it case by
>>> case.
>>> The old memory code for kvm was totally messy, in part because we
>>> tried to
>>> hug the world at once, with some code paths that were almost never hit.
>>>
>>> Slot management can easily get very complicated. and trying to come up
>>> with a solution that accounts for all problems at once may backfire
>>> on us.
>>>
>>>
>>
>> Well, then "fix" all users...
>>
>
> Making memory management in qemu symmetric (any
> cpu_register_physical_memory() must be followed by a
> cpu_unregister_physical_memory() with the same parameters) is a good idea.
>
Then all devices should track their - potentially guest-defined -
mappings and revert them on reset? I think handling this in the lower
layer is more convenient.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-02-11 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 13:47 [Qemu-devel] [PATCH] remove smaller slots if registering a bigger one Glauber Costa
2009-02-11 14:23 ` [Qemu-devel] " Jan Kiszka
2009-02-11 14:36 ` Avi Kivity
2009-02-11 14:37 ` Glauber Costa
2009-02-11 14:45 ` Jan Kiszka
2009-02-11 14:52 ` Jan Kiszka
2009-02-11 14:59 ` Glauber Costa
2009-02-11 15:30 ` Avi Kivity
2009-02-11 16:47 ` Jan Kiszka [this message]
2009-02-11 16:56 ` Avi Kivity
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=49930130.5050409@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@redhat.com \
--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.