All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [patch] kvm: make cr3 loading more robust
Date: Wed, 3 Jan 2007 13:21:14 +0100	[thread overview]
Message-ID: <20070103122114.GD2786@elte.hu> (raw)
In-Reply-To: <459B9C5C.9060008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>


* Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:

> >hm, where do we ensure that? kvm_mmu_get_page() calls 
> >kvm_mmu_alloc_page(), which might return NULL:
> >
> > static struct kvm_mmu_page *kvm_mmu_alloc_page(struct kvm_vcpu *vcpu,
> >                                                u64 *parent_pte)
> > {
> >         struct kvm_mmu_page *page;
> >
> >         if (list_empty(&vcpu->free_pages))
> >                 return NULL;
> >
> >and i dont see where we ensure that ->free_pages is not empty. The 
> >relevant callchain would be kvm_vmx_return() -> handle_cr() -> 
> >set_cr3() -> paging_new_cr3() -> mmu_alloc_roots() -> 
> >kvm_mmu_get_page().
> >
> >is there some accounting that makes a NULL pointer return impossible? 
> >The only one i can see is the direct quering of vcpu->free_pages or 
> >the querying of n_free_mmu_pages, but neither seems to be done in 
> >this codepath. (but i might have missed it)
> >
> >  
> 
> The page fault path does this:
> 
> static inline int kvm_mmu_page_fault(struct kvm_vcpu *vcpu, gva_t gva,
>                     u32 error_code)
> {
>    if (unlikely(vcpu->kvm->n_free_mmu_pages < KVM_MIN_FREE_MMU_PAGES))
>        kvm_mmu_free_some_pages(vcpu);
>    return vcpu->mmu.page_fault(vcpu, gva, error_code);
> }

ah. This hid in an include file. (Please dont put real program logic 
into include files - although i guess this is a justified exception :-)

> The context switch paths need to do the same.

yeah. Although, as this example has shown it, such implicit assumptions 
carried into code tends to be volatile. Couldnt the kvm_mmu_zap_page() 
be done implicitly within kvm_mmu_alloc_page()? As long as the list is 
LRU, and the number of allocations done within a logical operation 
doesnt exceed the size of the LRU list (which it doesnt), this should be 
doable.

	Ingo

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-01-03 12:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03  2:10 [patch] kvm: make cr3 loading more robust Ingo Molnar
     [not found] ` <20070103021057.GA11316-X9Un+BFzKDI@public.gmane.org>
2007-01-03  8:29   ` Avi Kivity
     [not found]     ` <459B695C.5090004-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 11:52       ` Ingo Molnar
     [not found]         ` <20070103115230.GB937-X9Un+BFzKDI@public.gmane.org>
2007-01-03 12:00           ` Avi Kivity
     [not found]             ` <459B9AC7.6020506-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 12:01               ` Avi Kivity
2007-01-03 12:13               ` Ingo Molnar
     [not found]                 ` <20070103121301.GC2786-X9Un+BFzKDI@public.gmane.org>
2007-01-03 12:25                   ` Avi Kivity
     [not found]                     ` <459BA0B4.20804-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 12:28                       ` Ingo Molnar
     [not found]                         ` <20070103122814.GA7350-X9Un+BFzKDI@public.gmane.org>
2007-01-03 12:40                           ` Ingo Molnar
     [not found]                             ` <20070103124020.GA9738-X9Un+BFzKDI@public.gmane.org>
2007-01-03 13:14                               ` Avi Kivity
     [not found]                                 ` <459BAC45.9090202-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 13:20                                   ` Ingo Molnar
     [not found]                                     ` <20070103132033.GA18027-X9Un+BFzKDI@public.gmane.org>
2007-01-03 13:34                                       ` Avi Kivity
2007-01-03 12:59                           ` Avi Kivity
2007-01-03 11:59       ` Ingo Molnar
     [not found]         ` <20070103115911.GA2786-X9Un+BFzKDI@public.gmane.org>
2007-01-03 12:06           ` Avi Kivity
     [not found]             ` <459B9C5C.9060008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 12:21               ` Ingo Molnar [this message]
     [not found]                 ` <20070103122114.GD2786-X9Un+BFzKDI@public.gmane.org>
2007-01-03 12:29                   ` Avi Kivity
     [not found]                     ` <459BA194.8070305-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 12:32                       ` Ingo Molnar
     [not found]                         ` <20070103123253.GA8822-X9Un+BFzKDI@public.gmane.org>
2007-01-03 13:13                           ` Avi Kivity
2007-01-03 13:37                           ` Ingo Molnar
     [not found]                             ` <20070103133714.GA20638-X9Un+BFzKDI@public.gmane.org>
2007-01-03 13:44                               ` Ingo Molnar
     [not found]                                 ` <20070103134417.GA22055-X9Un+BFzKDI@public.gmane.org>
2007-01-04  8:58                                   ` Avi Kivity
     [not found]                                     ` <459CC1BC.3070308-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-04  9:06                                       ` Ingo Molnar
2007-01-04  8:55                               ` 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=20070103122114.GD2786@elte.hu \
    --to=mingo-x9un+bfzkdi@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 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.