All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Steven <wangwangkang@gmail.com>
Cc: Wei Wang <wei.wang2@amd.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] acpi: do not flush cache if cx->type != ACPI_STATE_C3
Date: Fri, 13 Apr 2012 08:23:58 +0100	[thread overview]
Message-ID: <4F87F0AE020000780007DB14@nat28.tlf.novell.com> (raw)
In-Reply-To: <CAMTrTqUfiBPZ9bPYpCnuD=DSTEvG4oACMfAPBHGvja-JD_MnFw@mail.gmail.com>

>>> On 12.04.12 at 19:05, Steven <wangwangkang@gmail.com> wrote:
> Hi, Wei,
> I have read you slides in xen summit 2007 about NPT in AMD, "AMD
> Barcelona and Nested Paging Support in Xen".
> However, I have some question regarding the nested page walk in your slide 
> 8.

Please do not hijack threads for unrelated topics; create new ones
instead.

Jan

> In your slide 8, the first step is to get gPA from get_PML4(gCR3,gVA).
> I assume that it use the [47:39] bit of gVA.
> However, in another AMD white paper, "AMD-VTM Nested Paging".
> http://developer.amd.com/assets/NPT-WP-1%201-final-TM.pdf 
> In its figure 4, I saw that the first step is to translate gCR3 using
> nested page walk and then combine with the gVA[47:39] to read the
> table entry.
> 
> These two documents look having different order of reading the guest
> page table. In the slides, it first get_PML4. But in the white paper,
> it first does nested page walk.
> I am wondering which one is true. Thanks.
> 
> - ha
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org 
> http://lists.xen.org/xen-devel 

  reply	other threads:[~2012-04-13  7:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 13:11 [PATCH] acpi: do not flush cache if cx->type != ACPI_STATE_C3 Wei Wang
2012-04-12 17:05 ` Steven
2012-04-13  7:23   ` Jan Beulich [this message]
2012-04-13  2:14 ` Zhang, Yang Z
2012-04-13  8:30   ` Jan Beulich
2012-04-13  9:06     ` Wei Wang
2012-04-13 13:20       ` Zhang, Yang Z

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=4F87F0AE020000780007DB14@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=wangwangkang@gmail.com \
    --cc=wei.wang2@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.