From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, "He,
Qing" <qing.he-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 2/2] Add MSR Bitmap support in VMX
Date: Fri, 03 Aug 2007 07:55:36 +1000 [thread overview]
Message-ID: <1186091736.6131.149.camel@localhost.localdomain> (raw)
In-Reply-To: <46B1D092.7070609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Thu, 2007-08-02 at 15:39 +0300, Avi Kivity wrote:
> He, Qing wrote:
> >>
> >> hmm. While there's nothing wrong with the patch, there is a simpler way
> >> to do this:
> >>
> >> static unsigned long vmx_msr_bitmap[PAGE_SIZE / sizeof(unsigned
> >> long)] __aligned(PAGE_SIZE);
> >>
> >> now there's no need to allocate, error-check, free, or kmap the memory.
> >> The io bitmaps can receive similar treatment.
> >>
> >
> > Well, though not so important, kmapping do have a tiny advantage, it uses less virtual space if HIGHMEM is used. This makes sense when 1G limited kernel space is used, although it's highly unlikely to be a real problem.
> >
> >
>
> Starting a virtual machine consumes about 4MB of low memory for the
> shadow mmu (more for the memory map and for various slabs), so 4K is not
> an issue.
>
> However, I do see an issue with my proposal. To get the physical address
> of the page, we need to use vmalloc_to_page(). But that won't work if
> kvm is built into the kernel (and thus uses large pages for data).
>
> Rusty, what say you to a 'struct page *module_to_page(void *kaddr)'
> which does the right thing? Attached an implementation.
Hi Avi,
Arch-specific, unfortunately: modules do not need to be allocated with
vmalloc (and for small modules probably shouldn't anyway). Luckily
vmalloc always page-aligns AFAICT, so you get that.
So I think dynamic alloc is easier.
Rusty.
>
>
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2007-08-02 21:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 9:10 [PATCH 2/2] Add MSR Bitmap support in VMX Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F62F4C6-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-02 10:59 ` Avi Kivity
[not found] ` <46B1B925.1080808-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-02 12:03 ` He, Qing
[not found] ` <37E52D09333DE2469A03574C88DBF40F048ED2-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-02 12:39 ` Avi Kivity
[not found] ` <46B1D092.7070609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-02 14:23 ` Avi Kivity
[not found] ` <46B1E8D6.6010106-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-02 14:41 ` Li, Xin B
[not found] ` <B30DA1341B0CFA4893EF8A36B40B5C5D0178DAEF-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-02 14:50 ` Avi Kivity
[not found] ` <46B1EF29.9000200-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-02 15:07 ` Li, Xin B
2007-08-02 15:30 ` ron minnich
[not found] ` <13426df10708020830r5e716fb3p179f6937fb1f9412-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-02 15:50 ` Avi Kivity
[not found] ` <46B1FD30.9040708-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-02 17:54 ` Nakajima, Jun
[not found] ` <97D612E30E1F88419025B06CB4CF1BE10318605D-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-02 18:23 ` Ulrich Drepper
[not found] ` <46B22134.7080807-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-08-03 1:26 ` Li, Xin B
[not found] ` <B30DA1341B0CFA4893EF8A36B40B5C5D0178DC43-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-03 16:10 ` Avi Kivity
2007-08-02 21:55 ` Rusty Russell [this message]
[not found] ` <1186091736.6131.149.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-08-03 14:54 ` 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=1186091736.6131.149.camel@localhost.localdomain \
--to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=qing.he-ral2JQCrhuEAvxtiuMwx3w@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