From: Igor Druzhinin <igor.druzhinin@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: andrew.cooper3@citrix.com, wl@xen.org, jbeulich@suse.com,
roger.pau@citrix.com
Subject: Re: [PATCH] x86/svm: retry after unhandled NPT fault if gfn was marked for recalculation
Date: Fri, 22 May 2020 01:26:10 +0100 [thread overview]
Message-ID: <5727f0fd-38ed-91af-ee2c-0f1f6fb830f1@citrix.com> (raw)
In-Reply-To: <1590097438-28829-1-git-send-email-igor.druzhinin@citrix.com>
On 21/05/2020 22:43, Igor Druzhinin wrote:
> If a recalculation NPT fault hasn't been handled explicitly in
> hvm_hap_nested_page_fault() then it's potentially safe to retry -
> US bit has been re-instated in PTE and any real fault would be correctly
> re-raised next time.
>
> This covers a specific case of migration with vGPU assigned on AMD:
> global log-dirty is enabled and causes immediate recalculation NPT
> fault in MMIO area upon access. This type of fault isn't described
> explicitly in hvm_hap_nested_page_fault (this isn't called on
> EPT misconfig exit on Intel) which results in domain crash.
>
> Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
> ---
Alternatively, I can re-raise the fault immediately after recalculation is
done which is less efficient (will take one more VMEXIT) but safer IMO -
hvm_hap_nested_page_fault might potentially leave VM in inconsistent state
in case of a real failure and cause second page fault to conceal it.
Another alternative is to inject fall_through bool into hvm_hap_nested_page_fault
to give it the idea of expected behavior in that case and avoid guessing in SVM
code. I think that's an improvement over suggestion in v1 and a candidate for v2.
Igor
next prev parent reply other threads:[~2020-05-22 0:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 21:43 [PATCH] x86/svm: retry after unhandled NPT fault if gfn was marked for recalculation Igor Druzhinin
2020-05-22 0:26 ` Igor Druzhinin [this message]
2020-05-22 9:45 ` Andrew Cooper
2020-05-22 10:05 ` Igor Druzhinin
2020-05-22 10:19 ` Andrew Cooper
2020-05-22 10:25 ` Igor Druzhinin
2020-05-22 13:34 ` Jan Beulich
2020-05-22 10:08 ` Roger Pau Monné
2020-05-22 10:14 ` Igor Druzhinin
2020-05-22 10:23 ` Roger Pau Monné
2020-05-22 10:27 ` Igor Druzhinin
2020-05-22 11:11 ` Roger Pau Monné
2020-05-22 13:04 ` Jan Beulich
2020-05-22 13:11 ` Andrew Cooper
2020-05-22 13:32 ` Roger Pau Monné
2020-05-22 15:53 ` Andrew Cooper
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=5727f0fd-38ed-91af-ee2c-0f1f6fb830f1@citrix.com \
--to=igor.druzhinin@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).