From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>, xen-devel@lists.xen.org
Cc: tamas@tklengyel.com, keir@xen.org, jbeulich@suse.com
Subject: Re: [PATCH] vm_event: make sure the domain is paused in key domctls
Date: Thu, 28 Jan 2016 14:10:38 +0000 [thread overview]
Message-ID: <56AA215E.5020605@citrix.com> (raw)
In-Reply-To: <1453989160-8002-1-git-send-email-rcojocaru@bitdefender.com>
On 28/01/16 13:52, Razvan Cojocaru wrote:
> This patch pauses the domain for all writes through the 'ad'
> pointer in monitor_domctl(), defers a domain_unpause() call until
> after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG
> case, and makes sure that the domain is paused for both vm_event
> enable and disable cases in vm_event_domctl().
> Thanks go to Andrew Cooper for his review and suggestions.
>
> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Would you mind annotating each of the checks for d != current->domain
with /* no domain_pause(). */, which is our normal practice.
I think it might be better to move the current check for
XEN_DOMCTL_monitor_op into monitor_domctl() itself, to have all checks
together in one place.
> @@ -144,6 +146,8 @@ int monitor_domctl(struct domain *d, struct xen_domctl_monitor_op *mop)
> if ( rc )
> return rc;
>
> + domain_pause(d);
> +
> if ( mop->op == XEN_DOMCTL_MONITOR_OP_ENABLE &&
> mop->u.mov_to_msr.extended_capture )
> {
> @@ -154,7 +158,6 @@ int monitor_domctl(struct domain *d, struct xen_domctl_monitor_op *mop)
You will need to rework the return -EOPNOTSUPP between these two hunks
to avoid missing the domain_unpause()
It would probably be better to pull the check forwards to before the
domain_pause().
> } else
> ad->monitor.mov_to_msr_extended = 0;
>
> - domain_pause(d);
> ad->monitor.mov_to_msr_enabled = !status;
> domain_unpause(d);
> break;
> @@ -196,9 +199,8 @@ int monitor_domctl(struct domain *d, struct xen_domctl_monitor_op *mop)
>
The other codepaths look fine.
~Andrew
next prev parent reply other threads:[~2016-01-28 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 13:52 [PATCH] vm_event: make sure the domain is paused in key domctls Razvan Cojocaru
2016-01-28 14:10 ` Andrew Cooper [this message]
2016-01-28 14:27 ` Razvan Cojocaru
2016-01-28 14:52 ` Razvan Cojocaru
2016-01-28 20:09 ` Tamas K Lengyel
2016-01-28 21:05 ` Razvan Cojocaru
2016-01-28 21:47 ` Tamas K Lengyel
2016-01-29 6:52 ` Razvan Cojocaru
2016-01-29 6:55 ` Razvan Cojocaru
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=56AA215E.5020605@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.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.