From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] stop cpus before forking.
Date: Tue, 22 Jun 2010 15:18:06 +0300 [thread overview]
Message-ID: <4C20A9FE.1060308@redhat.com> (raw)
In-Reply-To: <20100616165810.GR19104@mothafucka.localdomain>
On 06/16/2010 07:58 PM, Glauber Costa wrote:
>
>> It is, and the fix would be to create the APIC memory slot as
>> sharable across forks (should be easy to fix in the kernel).
>>
> Kernel pages are already shared across fork, no?
>
What are kernel pages in this context?
The APIC access page is an ordinary user page.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-06-22 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 19:27 [Qemu-devel] [PATCH] stop cpus before forking Glauber Costa
2010-06-14 19:33 ` Anthony Liguori
2010-06-14 19:42 ` Glauber Costa
2010-06-14 19:58 ` Anthony Liguori
2010-06-14 20:05 ` Glauber Costa
2010-06-16 16:57 ` Glauber Costa
2010-06-15 6:14 ` Daniel P. Berrange
2010-06-15 7:36 ` Avi Kivity
2010-06-15 7:35 ` Avi Kivity
2010-06-15 7:33 ` Avi Kivity
2010-06-16 16:58 ` Glauber Costa
2010-06-22 12:18 ` Avi Kivity [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=4C20A9FE.1060308@redhat.com \
--to=avi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).