From: gleb@redhat.com (Gleb Natapov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] KVM: ARM: Get rid of KVM_HPAGE_ defines
Date: Sun, 25 Aug 2013 17:48:47 +0300 [thread overview]
Message-ID: <20130825144847.GV8218@redhat.com> (raw)
In-Reply-To: <CAFEAcA9-hcGHYAKTP4xty1pB-bs=EgATrxKQhCOQ3YZOOpM4wg@mail.gmail.com>
On Sun, Aug 25, 2013 at 03:29:17PM +0100, Peter Maydell wrote:
> On 25 August 2013 15:05, Gleb Natapov <gleb@redhat.com> wrote:
> > (you will probably need them when you will implement
> > nested HYP mode :)).
>
> Smiley noted, but this is pretty unlikely since it's not possible
> to lie to the guest about which mode it's in, so you can't make
> a guest think it's in Hyp mode.
>
I suspected this, but forgot most that I read about Hyp mode by now.
Need to refresh my memory ASAP. Is it impossible even with a lot of
emulation? Can guest detect that it is not in a Hyp mode without
trapping into hypervisor?
--
Gleb.
next prev parent reply other threads:[~2013-08-25 14:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 4:07 [PATCH 0/3] KVM/ARM Huge pages support Christoffer Dall
2013-08-09 4:07 ` [PATCH 1/3] KVM: Move gfn_to_index to x86 specific code Christoffer Dall
2013-08-09 4:07 ` [PATCH 2/3] KVM: ARM: Get rid of KVM_HPAGE_XXX defines Christoffer Dall
2013-08-09 4:07 ` [PATCH 3/3] KVM: ARM: Transparent huge pages and hugetlbfs support Christoffer Dall
2013-09-23 10:11 ` Marc Zyngier
2013-09-23 14:46 ` Marc Zyngier
2013-09-24 15:41 ` Steve Capper
2013-10-02 22:36 ` Christoffer Dall
2013-10-03 20:33 ` Christoffer Dall
2013-10-04 9:23 ` Marc Zyngier
2013-08-09 14:30 ` [PATCH 2/3] KVM: ARM: Get rid of KVM_HPAGE_ defines Christoffer Dall
2013-08-25 14:05 ` Gleb Natapov
2013-08-25 14:29 ` Peter Maydell
2013-08-25 14:48 ` Gleb Natapov [this message]
2013-08-25 15:18 ` Peter Maydell
2013-08-25 15:27 ` Alexander Graf
2013-08-26 10:55 ` Gleb Natapov
2013-08-26 0:46 ` Christoffer Dall
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=20130825144847.GV8218@redhat.com \
--to=gleb@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).