From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: INVLPG and IPI emulation in KVM
Date: Sun, 13 Nov 2011 14:44:41 +0200
Message-ID: <4EBFBBB9.60106@redhat.com>
References: <CALKntY3qmMQcMhFy9pSqQrRgYyzRo0A1_bkQ+=z4Mx-QQsECew@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
To: Xin Tong <xerox.time.tech@gmail.com>
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
In-Reply-To: <CALKntY3qmMQcMhFy9pSqQrRgYyzRo0A1_bkQ+=z4Mx-QQsECew@mail.gmail.com>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
List-Id: kvm.vger.kernel.org

On 11/13/2011 02:27 PM, Xin Tong wrote:
> I am investigating how INVLPG is emulated in kvm. 

You're on the wrong list.

> It turns out that it calls
>
> kvm_mmu_invlpg
>    kvm_mmu_flush_tlb
>      kvm_make_request(KVM_REQ_TLB_FLUSH, vcpu);
>
> and the kvm_make_request set the vcpu->requests bit to high, when the
> guest os resumes, it handles the bit. I have 2 questions
>
>
> 1. How does the make_request mechanism work ? 

See vcpu_enter_guest().

> how does the guest
> handle the requests ?

The guest never sees them, this is all internal to kvm.

> 2. INVLPG invalidates a tlb entry, it is typically used when the page
> table changes. However, an ipi is typically used to invalidate the tlb
> entries in other processor cores, However, i can not find the
> emulation code for IPI instruction.

There is no IPI instruction, see lapic.c:apic_send_ipi().

-- 
error compiling committee.c: too many arguments to function