From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Kevin Tian <kevin.tian@intel.com>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 2/2] x86/hvm: Don't intercept #UD exceptions in general
Date: Wed, 27 Jan 2016 19:18:17 +0000 [thread overview]
Message-ID: <56A917F9.4030003@citrix.com> (raw)
In-Reply-To: <56A91710.7010701@oracle.com>
On 27/01/16 19:14, Boris Ostrovsky wrote:
> On 01/27/2016 01:59 PM, Andrew Cooper wrote:
>> On 27/01/16 18:49, Boris Ostrovsky wrote:
>>> On 01/27/2016 01:11 PM, Andrew Cooper wrote:
>>>> diff --git a/xen/arch/x86/domctl.c b/xen/arch/x86/domctl.c
>>>> index 1d71216..1084e82 100644
>>>> --- a/xen/arch/x86/domctl.c
>>>> +++ b/xen/arch/x86/domctl.c
>>>> @@ -65,8 +65,20 @@ static void update_domain_cpuid_info(struct domain
>>>> *d,
>>>> .ecx = ctl->ecx
>>>> }
>>>> };
>>>> + int old_vendor = d->arch.x86_vendor;
>>>> d->arch.x86_vendor = get_cpu_vendor(vendor_id.str,
>>>> gcv_guest);
>>>> +
>>>> + if ( is_hvm_domain(d) && (d->arch.x86_vendor != old_vendor) )
>>>> + {
>>>> + struct vcpu *v;
>>>> +
>>>> + domain_pause(d);
>>>> + for_each_vcpu( d, v )
>>>> + hvm_update_guest_vendor(v);
>>>> + domain_unpause(d);
>>>> + }
>>>> +
>>>> break;
>>>> }
>>> Not specific to this patch, but shouldn't we pause/unpause domain for
>>> the whole routine?
>> Not specifically, although that might be better lonterm.
>>
>> In practice, this hypercall is only made as part of domain construction,
>> and never at domain runtime.
>
> Is it safe to unpause a domain here if it is not running?
Yes - all pausing/unpausing is reference counted, including the initial
systemcontroller pause reference taken (on behalf of the toolstack
domain) during the createdomain hypercall.
~Andrew
next prev parent reply other threads:[~2016-01-27 19:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:11 [PATCH 1/2] x86/vmx: Don't clobber exception_bitmap when entering/leaving emulated real mode Andrew Cooper
2016-01-27 18:11 ` [PATCH 2/2] x86/hvm: Don't intercept #UD exceptions in general Andrew Cooper
2016-01-27 18:49 ` Boris Ostrovsky
2016-01-27 18:59 ` Andrew Cooper
2016-01-27 19:14 ` Boris Ostrovsky
2016-01-27 19:18 ` Andrew Cooper [this message]
2016-01-27 19:13 ` [PATCH v2 " Andrew Cooper
2016-01-27 19:26 ` Boris Ostrovsky
2016-01-27 19:52 ` Konrad Rzeszutek Wilk
2016-01-27 19:57 ` Andrew Cooper
2016-01-27 20:21 ` Konrad Rzeszutek Wilk
2016-01-28 9:42 ` Jan Beulich
2016-01-28 10:55 ` Andrew Cooper
2016-01-28 11:30 ` Jan Beulich
2016-01-29 19:17 ` [PATCH v3 " Andrew Cooper
2016-02-01 12:23 ` Jan Beulich
2016-02-02 7:56 ` Tian, Kevin
2016-01-28 9:22 ` [PATCH 1/2] x86/vmx: Don't clobber exception_bitmap when entering/leaving emulated real mode Jan Beulich
2016-02-02 7:54 ` Tian, Kevin
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=56A917F9.4030003@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.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 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).