From: Avi Kivity <avi@qumranet.com>
To: schwidefsky@de.ibm.com
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Dave Hansen <haveblue@us.ibm.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Christian Ehrhardt <EHRHARDT@de.ibm.com>,
hollisb@us.ibm.com, arnd@arndb.de,
Linux Memory Management List <linux-mm@kvack.org>,
carsteno@de.ibm.com, heicars2@linux.vnet.ibm.com,
mschwid2@linux.vnet.ibm.com, jeroney@us.ibm.com,
borntrae@linux.vnet.ibm.com,
virtualization@lists.linux-foundation.org,
kvm-devel@lists.sourceforge.net, rvdheij@gmail.com,
Olaf Schnapper <os@de.ibm.com>,
jblunck@suse.de, "Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [kvm-devel] [RFC/PATCH 01/15] preparation: provide hook to enable pgstes in user pagetable
Date: Mon, 24 Mar 2008 08:57:49 +0200 [thread overview]
Message-ID: <47E750ED.7060509@qumranet.com> (raw)
In-Reply-To: <1206296609.10233.5.camel@localhost>
Martin Schwidefsky wrote:
> On Sun, 2008-03-23 at 12:15 +0200, Avi Kivity wrote:
>
>>>> Can you convert the page tables at a later time without doing a
>>>> wholesale replacement of the mm? It should be a bit easier to keep
>>>> people off the pagetables than keep their grubby mitts off the mm
>>>> itself.
>>>>
>>>>
>>> Yes, as far as I can see you're right. And whatever we do in arch code,
>>> after all it's just a work around to avoid a new clone flag.
>>> If something like clone() with CLONE_KVM would be useful for more
>>> architectures than just s390 then maybe we should try to get a flag.
>>>
>>> Oh... there are just two unused clone flag bits left. Looks like the
>>> namespace changes ate up a lot of them lately.
>>>
>>> Well, we could still play dirty tricks like setting a bit in current
>>> via whatever mechanism which indicates child-wants-extended-page-tables
>>> and then just fork and be happy.
>>>
>>>
>> How about taking mmap_sem for write and converting all page tables
>> in-place? I'd rather avoid the need to fork() when creating a VM.
>>
>
> That was my initial approach as well. If all the page table allocations
> can be fullfilled the code is not too complicated. To handle allocation
> failures gets tricky. At this point I realized that dup_mmap already
> does what we want to do. It walks all the page tables, allocates new
> page tables and copies the ptes. In principle I would reinvent the wheel
> if we can not use dup_mmap
Well, dup_mm() can't work (and now that I think about it, for more
reasons -- what if the process has threads?).
I don't think conversion is too bad. You'd need a four-level loop to
allocate and convert, and another loop to deallocate in case of error.
If, as I don't doubt, s390 hardware can modify the ptes, you'd need
cmpxchg to read and clear a pte in one operation.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-03-24 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1206028710.6690.21.camel@cotte.boeblingen.de.ibm.com>
2008-03-20 16:24 ` Carsten Otte, Martin Schwidefsky
2008-03-20 17:28 ` Jeremy Fitzhardinge
2008-03-20 19:13 ` Dave Hansen
2008-03-20 20:35 ` [kvm-devel] " Carsten Otte
2008-03-21 18:29 ` Dave Hansen
2008-03-21 19:03 ` Carsten Otte
2008-03-22 17:57 ` Heiko Carstens
2008-03-23 10:15 ` Avi Kivity
2008-03-23 18:23 ` Martin Schwidefsky
2008-03-24 6:57 ` Avi Kivity [this message]
2008-03-25 6:08 ` Carsten Otte
2008-03-25 6:12 ` Avi Kivity
2008-03-25 15:37 ` Carsten Otte
2008-03-20 16:24 ` [RFC/PATCH 02/15] preparation: host memory management changes for s390 kvm Carsten Otte, Heiko Carstens, Christian Borntraeger
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=47E750ED.7060509@qumranet.com \
--to=avi@qumranet.com \
--cc=EHRHARDT@de.ibm.com \
--cc=arnd@arndb.de \
--cc=borntrae@linux.vnet.ibm.com \
--cc=carsteno@de.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=heicars2@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=jblunck@suse.de \
--cc=jeremy@goop.org \
--cc=jeroney@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=mschwid2@linux.vnet.ibm.com \
--cc=os@de.ibm.com \
--cc=rvdheij@gmail.com \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xiantao.zhang@intel.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