All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claudio Fontana <claudio.fontana@huawei.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"alvise rigo" <a.rigo@virtualopensystems.com>
Cc: "MTTCG Devel" <mttcg@listserver.greensocs.com>,
	"Mark Burton" <mark.burton@greensocs.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Emilio G. Cota" <cota@braap.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Sergey Fedorov" <serge.fdrv@gmail.com>,
	"Pranith Kumar" <bobby.prani@gmail.com>,
	"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] Any topics for today's MTTCG sync-up call?
Date: Mon, 23 May 2016 14:57:12 +0200	[thread overview]
Message-ID: <5742FE28.3020601@huawei.com> (raw)
In-Reply-To: <878tz1djph.fsf@linaro.org>

On 23.05.2016 14:47, Alex Bennée wrote:
> 
> alvise rigo <a.rigo@virtualopensystems.com> writes:
> 
>> Hi Alex,
>>
>> I finally solved the issue I had, the branch is working well as far as I
>> can say.
>> The work I will share, in addition to making the LL/SC work mttcg-aware,
>> extends the various TLB flushes calls with the query-based mechanism: the
>> requesting CPU queries the flushes to the target CPUs and wait them for
>> completion.
>>
>> Sorry for the delay, I have been quite busy. I just need to polish some
>> commits, than (this week) I will share the branch.
> 
> Thanks for the update. It sounds like we don't need to add to that on
> the call.
> 
> Anyone else have something they want to discuss?

Hi, at some point in the past there was a set of performance benchmarks which were showing the improvements using mttcg,
is there some update on that?

Thanks,

Claudio

> 
>>
>> Best regards,
>> alvise
>>
>> On Mon, May 23, 2016 at 12:57 PM, Alex Bennée <alex.bennee@linaro.org>
>> wrote:
>>
>>> Hi,
>>>
>>> It's been a while since the last sync-up call. Have we got any topics to
>>> discuss today?
>>>
>>> Sergey and I (with a little Paolo) have spent some of last week delving
>>> into the locking hierarchy w.r.t to tb_lock vs mmap_lock to see if there
>>> is any simplification to be had. I'm not sure if this is a topic
>>> conducive to a phone call instead of the mailing list but if others want
>>> to discuss it we can add it as an agenda item.
>>>
>>> We also have a new member of the team. Pranith has joined as a GSoC
>>> student. He'll be looking at memory ordering with his first pass at the
>>> problem looking to solve the store-after-load issues which do show up on
>>> ARM-on-x86 (see my testcase).
>>>
>>> Alvise, is there any help you need with the LL/SC stuff? The MTTCG aware
>>> version has been taking some time so would it be worth sharing the
>>> issues you have hit with the group?
>>>
>>> Emilio, is there anything you want to add? I've been following the QHT
>>> stuff which is a really positive addition which my v3 base patches is
>>> based upon (making the hot-path non lock contended). Do you have
>>> anything in the works above that?
>>>
>>> Cheers,
>>>
>>> --
>>> Alex Bennée
>>>
> 
> 
> --
> Alex Bennée
> 

  reply	other threads:[~2016-05-23 12:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 10:57 [Qemu-devel] Any topics for today's MTTCG sync-up call? Alex Bennée
2016-05-23 12:03 ` alvise rigo
2016-05-23 12:47   ` Alex Bennée
2016-05-23 12:57     ` Claudio Fontana [this message]
2016-05-23 13:16       ` Alex Bennée
2016-05-23 15:22       ` Emilio G. Cota
2016-05-23 15:28 ` Emilio G. Cota
  -- strict thread matches above, loose matches on Subject: below --
2016-06-20 11:57 Alex Bennée
2016-06-20 13:01 ` alvise rigo
2016-06-20 14:12   ` Alex Bennée
2016-06-20 14:18     ` alvise rigo
2016-07-04  9:46 Alex Bennée
2016-07-04 13:08 ` Alex Bennée

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=5742FE28.3020601@huawei.com \
    --to=claudio.fontana@huawei.com \
    --cc=a.rigo@virtualopensystems.com \
    --cc=alex.bennee@linaro.org \
    --cc=bobby.prani@gmail.com \
    --cc=cota@braap.org \
    --cc=fred.konrad@greensocs.com \
    --cc=mark.burton@greensocs.com \
    --cc=mttcg@listserver.greensocs.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=serge.fdrv@gmail.com \
    /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.