From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: penberg@kernel.org, mingo@elte.hu, gorcunov@gmail.com,
asias.hejun@gmail.com, kvm@vger.kernel.org, ajsween@sandia.gov
Subject: Re: [PATCH] kvm tools: mmap guest kernel instead of reading it into memory
Date: Tue, 13 Dec 2011 08:46:10 +0200 [thread overview]
Message-ID: <1323758770.3269.14.camel@lappy> (raw)
In-Reply-To: <4EE64395.7020109@redhat.com>
On Mon, 2011-12-12 at 20:10 +0200, Avi Kivity wrote:
> On 12/12/2011 04:47 PM, Sasha Levin wrote:
> > This patch mmaps guest kernel into it's own memory slot instead of reading
> > it into the memory.
> >
> > - } else {
> > - /* First RAM range from zero to the PCI gap: */
> >
> > + /* Mapped kernel */
> > + phys_start = BZ_KERNEL_START;
> > + phys_size = bzl;
> > + host_mem = kvm->bz_start;
> > +
> > + kvm__register_mem(kvm, phys_start, phys_size, host_mem);
> > +
> > + /* Rest of the memory */
> > + phys_start = BZ_KERNEL_START + bzl;
> > + phys_size = kvm->ram_size - (BZ_KERNEL_START + bzl);
> > + host_mem = kvm->ram_start + (BZ_KERNEL_START + bzl);
> > +
> > + kvm__register_mem(kvm, phys_start, phys_size, host_mem);
> >
>
>
> You don't actually need separate slots for this (there is no requirement
> that a slot == one vma).
How exactly would I put it into one slot?
--
Sasha.
prev parent reply other threads:[~2011-12-13 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 14:47 [PATCH] kvm tools: mmap guest kernel instead of reading it into memory Sasha Levin
2011-12-12 14:54 ` Pekka Enberg
2011-12-12 17:47 ` Sasha Levin
2011-12-12 16:40 ` Andrew Walrond
2011-12-12 15:59 ` Pekka Enberg
2011-12-12 18:14 ` Sasha Levin
2011-12-12 18:03 ` Avi Kivity
2011-12-12 17:18 ` Ingo Molnar
2011-12-12 18:08 ` Avi Kivity
2011-12-12 18:10 ` Avi Kivity
2011-12-13 6:46 ` Sasha Levin [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=1323758770.3269.14.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=ajsween@sandia.gov \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.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.