All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Manuel Bouyer <bouyer@antioche.eu.org>
Subject: Re: Ping: Re: [PATCH] x86: correct vCPU dirty CPU handling
Date: Tue, 22 May 2018 13:29:41 +0100	[thread overview]
Message-ID: <7d0aa7e7-71f7-5e84-55f8-7fe5b9b37fe8@citrix.com> (raw)
In-Reply-To: <5AFA997602000078001C2C29@prv1-mh.provo.novell.com>

On 15/05/18 09:25, Jan Beulich wrote:
>>>> On 26.04.18 at 12:52, <JBeulich@suse.com> wrote:
>>>>> On 26.04.18 at 11:51, <andrew.cooper3@citrix.com> wrote:
>>> On 26/04/18 10:41, Jan Beulich wrote:
>>>> --- a/xen/arch/x86/mm.c
>>>> +++ b/xen/arch/x86/mm.c
>>>> @@ -1202,11 +1202,23 @@ void put_page_from_l1e(l1_pgentry_t l1e,
>>>>               unlikely(((page->u.inuse.type_info & PGT_count_mask) != 0)) &&
>>>>               (l1e_owner == pg_owner) )
>>>>          {
>>>> +            cpumask_t *mask = this_cpu(scratch_cpumask);
>>>> +
>>>> +            cpumask_clear(mask);
>>>> +
>>>>              for_each_vcpu ( pg_owner, v )
>>>>              {
>>>> -                if ( pv_destroy_ldt(v) )
>>>> -                    flush_tlb_mask(cpumask_of(v->dirty_cpu));
>>>> +                unsigned int cpu;
>>>> +
>>>> +                if ( !pv_destroy_ldt(v) )
>>>> +                    continue;
>>>> +                cpu = read_atomic(&v->dirty_cpu);
>>>> +                if ( is_vcpu_dirty_cpu(cpu) )
>>>> +                    __cpumask_set_cpu(cpu, mask);
>>>>              }
>>>> +
>>>> +            if ( !cpumask_empty(mask) )
>>>> +                flush_tlb_mask(mask);
>>> Thinking about this, what is wrong with:
>>>
>>> bool flush;
>>>
>>> for_each_vcpu ( pg_owner, v )
>>>     if ( pv_destroy_ldt(v) )
>>>         flush = true;
>>>
>>> if ( flush )
>>>    flush_tlb_mask(pg_owner->dirty_cpumask);
>>>
>>> This is far less complicated cpumask handling.  As the loop may be long,
>>> it avoids flushing pcpus which have subsequently switched away from
>>> pg_owner context.  It also avoids all playing with v->dirty_cpu.
>> That would look to be correct, but I'm not sure it would be an improvement:
>> While it may avoid flushing some CPUs, it may then do extra flushes on
>> others (which another vCPU of the domain has been switched to). Plus it
>> would flush even those CPUs where pv_destroy_ldt() has returned false,
>> as long as the function returned true at least once.
> Ping?

I'm not sure it is worth trying to optimise this code.  I've got a patch
for 4.12 to leave it compiled out by default.

Therefore, Acked-by: Andrew Cooper <andrew.cooper3@citrix.com> on the
original patch.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-22 12:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26  9:41 [PATCH] x86: correct vCPU dirty CPU handling Jan Beulich
2018-04-26  9:51 ` Andrew Cooper
2018-04-26 10:52   ` Jan Beulich
2018-05-15  8:25     ` Ping: " Jan Beulich
2018-05-22 12:29       ` Andrew Cooper [this message]
2018-05-22 12:38         ` Juergen Gross
2018-04-26 12:39 ` Manuel Bouyer
2018-05-22 11:02 ` Manuel Bouyer
2018-05-22 11:08   ` 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=7d0aa7e7-71f7-5e84-55f8-7fe5b9b37fe8@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=bouyer@antioche.eu.org \
    --cc=jgross@suse.com \
    --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.