[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101007175943.GH2397@redhat.com>
Date: Thu, 7 Oct 2010 19:59:43 +0200
From: Gleb Natapov <gleb@...hat.com>
To: Avi Kivity <avi@...hat.com>
Cc: kvm@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, mingo@...e.hu,
a.p.zijlstra@...llo.nl, tglx@...utronix.de, hpa@...or.com,
riel@...hat.com, cl@...ux-foundation.org, mtosatti@...hat.com
Subject: Re: [PATCH v6 06/12] Add PV MSR to enable asynchronous page faults
delivery.
On Thu, Oct 07, 2010 at 02:58:26PM +0200, Avi Kivity wrote:
> On 10/04/2010 05:56 PM, Gleb Natapov wrote:
> >+
> >+ Physical address points to 32 bit memory location that will be written
> >+ to by the hypervisor at the time of asynchronous page fault injection to
> >+ indicate type of asynchronous page fault. Value of 1 means that the page
> >+ referred to by the page fault is not present. Value 2 means that the
> >+ page is now available.
>
> "The must not enable interrupts before the reason is read, or it may
> be overwritten by another apf".
>
> Document the fact that disabling interrupts disables APFs.
>
> How does the guest distinguish betweem APFs and ordinary page faults?
>
> What's the role of cr2?
>
> When disabling APF, all pending APFs are flushed and may or may not
> get a completion.
>
> Is a "page available" notification guaranteed to arrive on the same
> vcpu that took the "page not present" fault?
>
You mean documentation is lacking? :)
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists