All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Egger, Christoph" <chegger@amazon.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: suravee.suthikulpanit@amd.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/1 V2] x86/AMD: Fix nested svm crash due to assertion in __virt_to_maddr
Date: Mon, 8 Jul 2013 11:18:35 +0200	[thread overview]
Message-ID: <51DA83EB.7040605@amazon.de> (raw)
In-Reply-To: <51DA9EDD02000078000E32F5@nat28.tlf.novell.com>

On 08.07.13 11:13, Jan Beulich wrote:
>>>> On 06.07.13 at 00:10, <suravee.suthikulpanit@amd.com> wrote:
>> @@ -1816,7 +1816,7 @@ svm_vmexit_do_vmload(struct vmcb_struct *vmcb,
>>          goto inject;
>>      }
>>  
>> -    svm_vmload(nv->nv_vvmcx);
>> +    svm_vmload_by_paddr(nv->nv_vvmcxaddr);
>>      /* State in L1 VMCB is stale now */
>>      v->arch.hvm_svm.vmcb_in_sync = 0;
>>  
>> @@ -1852,7 +1852,7 @@ svm_vmexit_do_vmsave(struct vmcb_struct *vmcb,
>>          goto inject;
>>      }
>>  
>> -    svm_vmsave(nv->nv_vvmcx);
>> +    svm_vmsave_by_paddr(nv->nv_vvmcxaddr);
>>  
>>      __update_guest_eip(regs, inst_len);
>>      return;
> 
> As said on the previous version already - from all I can tell these
> are GPAs, not PAs, and hence can't be passed untranslated to
> VMLOAD/VMSAVE. If I'm right with this, I also can't see how this
> would have worked for you...

You can translate GPA->PA with the hostp2m.

> Apart from that I also dislike the _by_paddr suffix. I'd suggest
> either just _pa, or (slightly preferable) prefixing the names with
> a double underscore instead.

I prefer _pa suffix over the latter.

Christoph

  reply	other threads:[~2013-07-08  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 22:10 [PATCH 1/1 V2] x86/AMD: Fix nested svm crash due to assertion in __virt_to_maddr suravee.suthikulpanit
2013-07-08  9:13 ` Jan Beulich
2013-07-08  9:18   ` Egger, Christoph [this message]
2013-07-08  9:37     ` Jan Beulich
2013-07-08  9:59       ` Egger, Christoph
2013-07-08 16:21   ` Tim Deegan

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=51DA83EB.7040605@amazon.de \
    --to=chegger@amazon.de \
    --cc=JBeulich@suse.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xen.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 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.