From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/hvm: Drop more remains of the PVHv1 implementation
Date: Wed, 19 Jul 2017 15:13:58 +0100 [thread overview]
Message-ID: <a3157fa7-fb8c-a187-e147-aafb0afc02eb@citrix.com> (raw)
In-Reply-To: <20170719141204.eslsqc72rvrapzgw@dhcp-3-128.uk.xensource.com>
On 19/07/17 15:12, Roger Pau Monné wrote:
> On Wed, Jul 19, 2017 at 02:27:31PM +0100, Andrew Cooper wrote:
>> These functions don't need is_hvm_{vcpu,domain}() predicates.
>>
>> hvmop_set_evtchn_upcall_vector() does need the predicate to prevent a PV
>> caller accessing the hvm union, but swap the copy_from_guest() and
>> is_hvm_domain() predicate to avoid reading the hypercall parameter if we not
>> going to use it.
> IC, certain HVMOPs are available to PV guests (ie: the control domain).
At the very least, the control domain needs to use HVMOP_getparam for
construction and migration purposes. As a result, PV guests have always
had blanket reign on HVMOPs.
>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
>
> Thanks. Just one style nit.
>
>> CC: George Dunlap <George.Dunlap@eu.citrix.com>
>> CC: Jan Beulich <JBeulich@suse.com>
>> CC: Wei Liu <wei.liu2@citrix.com>
>> CC: Paul Durrant <paul.durrant@citrix.com>
>> CC: Roger Pau Monné <roger.pau@citrix.com>
>> ---
>> xen/arch/x86/hvm/hvm.c | 15 ++++++---------
>> 1 file changed, 6 insertions(+), 9 deletions(-)
>>
>> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
>> index 8145385..4fef616 100644
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++ b/xen/arch/x86/hvm/hvm.c
>> @@ -506,8 +506,7 @@ void hvm_do_resume(struct vcpu *v)
>> {
>> check_wakeup_from_wait();
>>
>> - if ( is_hvm_domain(v->domain) )
>> - pt_restore_timer(v);
>> + pt_restore_timer(v);
>>
>> if ( !handle_hvm_io_completion(v) )
>> return;
>> @@ -1544,8 +1543,7 @@ void hvm_vcpu_destroy(struct vcpu *v)
>> tasklet_kill(&v->arch.hvm_vcpu.assert_evtchn_irq_tasklet);
>> hvm_funcs.vcpu_destroy(v);
>>
>> - if ( is_hvm_vcpu(v) )
>> - vlapic_destroy(v);
>> + vlapic_destroy(v);
>>
>> hvm_vcpu_cacheattr_destroy(v);
>> }
>> @@ -1711,7 +1709,6 @@ int hvm_hap_nested_page_fault(paddr_t gpa, unsigned long gla,
>> * - newer Windows (like Server 2012) for HPET accesses.
>> */
>> if ( !nestedhvm_vcpu_in_guestmode(curr)
>> - && is_hvm_domain(currd)
>> && hvm_mmio_internal(gpa) )
> Can this be moved to the previous line?
Will fix on commit.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-07-19 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 13:27 [PATCH] x86/hvm: Drop more remains of the PVHv1 implementation Andrew Cooper
2017-07-19 13:33 ` Paul Durrant
2017-07-19 13:35 ` Wei Liu
2017-07-19 14:12 ` Roger Pau Monné
2017-07-19 14:13 ` Andrew Cooper [this message]
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=a3157fa7-fb8c-a187-e147-aafb0afc02eb@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=paul.durrant@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.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).