From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Andrew Cooper <andrew.cooper3@citrix.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 16:52:50 +0200 [thread overview]
Message-ID: <56AA2B42.5090904@bitdefender.com> (raw)
In-Reply-To: <56AA215E.5020605@citrix.com>
On 01/28/2016 04:10 PM, Andrew Cooper wrote:
> 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.
Nice, doing that allowed me to find and modify this code:
1137 #ifdef CONFIG_HAS_MEM_ACCESS
1138 case XEN_DOMCTL_set_access_required:
1139 if ( unlikely(current->domain == d) ) /* no domain_pause() */
1140 ret = -EPERM;
1141 else
1142 {
1143 domain_pause(d);
1144 p2m_get_hostp2m(d)->access_required =
1145 op->u.access_required.access_required;
1146 domain_unpause(d);
1147 }
1148 break;
1149 #endif
(there was no domain_pause(d) / domain_unpause(d)) before.
Thanks,
Razvan
next prev parent reply other threads:[~2016-01-28 14:52 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
2016-01-28 14:27 ` Razvan Cojocaru
2016-01-28 14:52 ` Razvan Cojocaru [this message]
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=56AA2B42.5090904@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--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.