kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Nadav Har'El <nyh@math.technion.ac.il>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Bug 53611] New: nVMX: Add nested EPT
Date: Wed, 24 Apr 2013 09:25:38 +0200	[thread overview]
Message-ID: <517788F2.1080308@web.de> (raw)
In-Reply-To: <514C8AB9.6040602@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

On 2013-03-22 17:45, Jan Kiszka wrote:
> On 2013-03-22 07:23, Nakajima, Jun wrote:
>> On Mon, Mar 4, 2013 at 8:45 PM, Nakajima, Jun <jun.nakajima@intel.com> wrote:
>>> I have some updates on this. We rebased the patched to the latest KVM
>>> (L0). It turned out that the version of L1 KVM/Linux matters. At that
>>> time, actually I used v3.7 kernel for L1, and the L2 didn't work as I
>>> described above. If I use v3.5 or older for L1, L2 works with the EPT
>>> patches. So, I guess some changes made to v3.6 might have exposed a
>>> bug with the nested EPT patches or somewhere. We are looking at the
>>> changes to root-cause it.
>>>
>>
>> Finally I've had more time to work on this, and I think I've fixed
>> this. The problem was that the exit qualification for EPT violation
>> (to L1) was not accurate (enough). And I needed to save the exit
>> qualification upon EPT violation somewhere. Today, that information is
>> converted to error_code (see below), and we lose the information.  We
>> need to use  at least the lower 3 bits when injecting EPT violation to
>> the L1 VMM. I tried to use the upper bytes of error_code to pass  part
>> of the exit qualification, but it didn't work well. Any suggestion for
>> the place to store the value? kvm_vcpu?
>>
>>        ...
>>         /* It is a write fault? */
>>         error_code = exit_qualification & (1U << 1);
>>         /* ept page table is present? */
>>         error_code |= (exit_qualification >> 3) & 0x1;
>>
>>         return kvm_mmu_page_fault(vcpu, gpa, error_code, NULL, 0);
> 
> I don't have a full picture (already asked you to post / git-push your
> intermediate state), but nested related states typically go to
> nested_vmx, thus vcpu_vmx.

Ping regarding publication. I'm about to redo your porting work as we
are making no progress.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-04-24  7:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 12:49 [Bug 53611] New: nVMX: Add nested EPT bugzilla-daemon
2013-02-11 12:50 ` [Bug 53611] " bugzilla-daemon
2013-02-11 13:16 ` [Bug 53611] New: " Jan Kiszka
2013-02-11 13:27   ` Nadav Har'El
2013-02-11 14:53     ` Jan Kiszka
2013-02-12 19:13     ` Nakajima, Jun
2013-02-13  7:43       ` Jan Kiszka
2013-02-15  2:07         ` Nakajima, Jun
2013-02-26 14:11           ` Nadav Har'El
2013-02-26 19:43             ` Jan Kiszka
2013-02-26 20:14               ` Gleb Natapov
2013-03-05  4:45               ` Nakajima, Jun
2013-03-05  8:28                 ` Jan Kiszka
2013-03-22  6:23                 ` Nakajima, Jun
2013-03-22 16:45                   ` Jan Kiszka
2013-04-24  7:25                     ` Jan Kiszka [this message]
2013-04-24 15:55                       ` Nakajima, Jun
2013-04-24 15:57                         ` Jan Kiszka
2013-04-25  8:00                         ` Nakajima, Jun
2013-04-25  9:19                           ` Gleb Natapov
2013-04-26  6:26                           ` Jan Kiszka
2013-04-26 16:07                             ` Nakajima, Jun
2013-04-28 10:03                               ` Jan Kiszka
2013-02-27  8:14 ` [Bug 53611] " bugzilla-daemon
2015-03-17  3:53 ` bugzilla-daemon
2015-04-08  9:02 ` bugzilla-daemon

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=517788F2.1080308@web.de \
    --to=jan.kiszka@web.de \
    --cc=jun.nakajima@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=nyh@math.technion.ac.il \
    /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).