From: Gleb Natapov <gleb@kernel.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Tang Chen <tangchen@cn.fujitsu.com>,
pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, mgorman@suse.de, yinghai@kernel.org,
isimatu.yasuaki@jp.fujitsu.com, guz.fnst@cn.fujitsu.com,
laijs@cn.fujitsu.com, kvm@vger.kernel.org, linux-mm@kvack.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
Avi Kivity <avi.kivity@gmail.com>
Subject: Re: [RFC PATCH 1/1] Move two pinned pages to non-movable node in kvm.
Date: Sun, 22 Jun 2014 12:19:27 +0300 [thread overview]
Message-ID: <20140622091927.GA18167@minantech.com> (raw)
In-Reply-To: <20140620203146.GA6580@amt.cnet>
On Fri, Jun 20, 2014 at 05:31:46PM -0300, Marcelo Tosatti wrote:
> > > Same with the APIC access page.
> > APIC page is always mapped into guest's APIC base address 0xfee00000.
> > The way it works is that when vCPU accesses page at 0xfee00000 the access
> > is translated to APIC access page physical address. CPU sees that access
> > is for APIC page and generates APIC access exit instead of memory access.
> > If address 0xfee00000 is not mapped by EPT then EPT violation exit will
> > be generated instead, EPT mapping will be instantiated, access retired
> > by a guest and this time will generate APIC access exit.
>
> Right, confused with the other APIC page which the CPU writes (the vAPIC page)
> to.
>
That one is allocated with kmalloc.
--
Gleb.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-06-22 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 5:50 [RFC PATCH 1/1] Move two pinned pages to non-movable node in kvm Tang Chen
2014-06-18 6:12 ` Gleb Natapov
2014-06-18 6:50 ` Tang Chen
2014-06-19 9:20 ` Gleb Natapov
2014-06-19 19:00 ` Marcelo Tosatti
2014-06-20 3:20 ` Tang Chen
2014-06-20 11:15 ` Gleb Natapov
2014-06-20 12:53 ` Marcelo Tosatti
2014-06-20 14:26 ` Gleb Natapov
2014-06-20 20:31 ` Marcelo Tosatti
2014-06-20 20:39 ` Marcelo Tosatti
2014-06-23 1:48 ` Tang Chen
2014-06-30 1:45 ` Tang Chen
2014-06-30 6:00 ` Gleb Natapov
2014-06-30 8:58 ` Tang Chen
2014-06-22 9:19 ` Gleb Natapov [this message]
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=20140622091927.GA18167@minantech.com \
--to=gleb@kernel.org \
--cc=avi.kivity@gmail.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tangchen@cn.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).