From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Shaohua Li <shaoh.li-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC 4/8]KVM: move gfn_to_page out of kmap/unmap pars
Date: Wed, 25 Jul 2007 10:19:31 +0300 [thread overview]
Message-ID: <46A6F983.3040005@qumranet.com> (raw)
In-Reply-To: <288dbef70707240618l71bd8678n28a39e663dab3c1c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Shaohua Li wrote:
> 2007/7/24, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>:
>> Shaohua Li wrote:
>> > gfn_to_page might sleep with swap support. Move it out of the kmap
>> calls.
>> >
>> >
>>
>> I'd like to apply this to the kvm.git master branch so we don't have to
>> maintain it. Was this tested on a highmem machine? If not, I can do
>> it.
> My test system has 1G memory, so it should work. I only tested 32bit
> system, better check a x64 build.
>
This is now in, after minor merge fixups.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-07-25 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 6:51 [RFC 4/8]KVM: move gfn_to_page out of kmap/unmap pars Shaohua Li
2007-07-24 9:38 ` Avi Kivity
[not found] ` <46A5C884.8060200-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-24 13:18 ` Shaohua Li
[not found] ` <288dbef70707240618l71bd8678n28a39e663dab3c1c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-25 7:19 ` 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=46A6F983.3040005@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shaoh.li-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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