From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: Single memory slot
Date: Fri, 16 Oct 2009 08:43:31 +0900 [thread overview]
Message-ID: <4AD7B3A3.7010202@redhat.com> (raw)
In-Reply-To: <4AD76F1B.3040607@codemonkey.ws>
On 10/16/2009 03:51 AM, Anthony Liguori wrote:
> Avi Kivity wrote:
>> One way to improve the gfn_to_pfn() memslot search is to register
>> just one slot. This can only work on 64-bit, since even the smallest
>> guests need 4GB of physical address space. Apart from speeding up
>> gfn_to_page(), it would also speed up mmio which must iterate over
>> all slots, so a lookup cache cannot help.
>>
>> This would require quite a bunch of changes:
>> - modify gfn_to_pfn() to fail gracefully if the page is in the slot
>> but unmapped (hole handling)
>> - modify qemu to reserve the guest physical address space
>
> It could potentially speed up qemu quite a lot too as we would return
> to a model where host va == fixed address + guest pa. That makes
> things like stl_phys/ldl_phys trivial.
This doesn't work on 32-bit, and you still need to perform a lookup for
mmio. It just shortens the loop.
Note qemu can't depend on mmio holes being unmapped (you could trap the
SEGV, but that would be unbearably slow).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-10-15 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 7:33 Single memory slot Avi Kivity
2009-10-15 12:46 ` Alexander Graf
2009-10-15 19:49 ` Marcelo Tosatti
2009-10-15 18:51 ` Anthony Liguori
2009-10-15 23:43 ` Avi Kivity [this message]
2009-10-15 19:46 ` Marcelo Tosatti
2009-10-15 23:48 ` 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=4AD7B3A3.7010202@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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;
as well as URLs for NNTP newsgroup(s).