From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH RFC 1/2] xen/pvh: take the p2m lock when doing logdirty ops from HVM domains
Date: Wed, 15 Oct 2014 12:55:30 +0100 [thread overview]
Message-ID: <543E60B2.3060904@citrix.com> (raw)
In-Reply-To: <543E600F.5@citrix.com>
On 15/10/14 12:52, Roger Pau Monné wrote:
> El 15/10/14 a les 13.31, Andrew Cooper ha escrit:
>> On 15/10/14 11:53, Roger Pau Monne wrote:
>>> ---
>>> xen/arch/x86/mm/paging.c | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/xen/arch/x86/mm/paging.c b/xen/arch/x86/mm/paging.c
>>> index 6b788f7..5af6309 100644
>>> --- a/xen/arch/x86/mm/paging.c
>>> +++ b/xen/arch/x86/mm/paging.c
>>> @@ -412,6 +412,8 @@ static int paging_log_dirty_op(struct domain *d,
>>>
>>> if ( !resuming )
>>> domain_pause(d);
>>> + if (has_hvm_container_vcpu(current))
>>> + p2m_lock(p2m_get_hostp2m(current->domain));
>> It appears as if there is some indentation issue here.
> Yes, an extra space.
>
>> Also, can you pull current into a struct vcpu *curr on the stack?
> We only use ->domain from current, would you prefer me to pull
> current->domain instead?
>
> Roger.
You use current, and current->domain.
current degrades eventually into a macro which bitmasks the stack
pointer. Looking at the generated asm, GCC is not fantastic at eliding
recalculations of it. Therefore, it is better to manually optimise it.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-15 11:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 10:53 [PATCH RFC 0/2] xen/pvh: enable migration on PVH Dom0 Roger Pau Monne
2014-10-15 10:53 ` [PATCH RFC 1/2] xen/pvh: take the p2m lock when doing logdirty ops from HVM domains Roger Pau Monne
2014-10-15 11:31 ` Andrew Cooper
2014-10-15 11:52 ` Roger Pau Monné
2014-10-15 11:55 ` Andrew Cooper [this message]
2014-10-15 11:58 ` Roger Pau Monné
2014-10-16 8:21 ` Jan Beulich
2014-10-16 9:20 ` Tim Deegan
2014-10-16 10:03 ` Roger Pau Monné
2014-11-13 15:46 ` Tim Deegan
2014-11-13 16:17 ` Jan Beulich
2014-10-16 14:15 ` Jan Beulich
2014-10-16 15:05 ` Tim Deegan
2014-10-15 10:53 ` [PATCH RFC 2/2] xen/pvh: enable mmu_update hypercall Roger Pau Monne
2014-10-16 7:53 ` Tim Deegan
2014-10-16 8:45 ` Jan Beulich
2014-10-16 11:30 ` Roger Pau Monné
2014-10-16 13:28 ` Jan Beulich
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=543E60B2.3060904@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=tim@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 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.