From: "Alex Bennée" <alex.bennee@linaro.org>
To: alvise rigo <a.rigo@virtualopensystems.com>
Cc: "MTTCG Devel" <mttcg@listserver.greensocs.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Mark Burton" <mark.burton@greensocs.com>,
"KONRAD Frédéric" <fred.konrad@greensocs.com>,
"Sergey Fedorov" <serge.fdrv@gmail.com>,
"Emilio G. Cota" <cota@braap.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Pranith Kumar" <bobby.prani@gmail.com>
Subject: Re: [Qemu-devel] Any topics for today's MTTCG sync-up call?
Date: Mon, 20 Jun 2016 15:12:29 +0100 [thread overview]
Message-ID: <8760t4rlte.fsf@linaro.org> (raw)
In-Reply-To: <CAH47eN3BKcu3tk+YubSMiRFKeEf5BHimSZJF8C_b7KJG4pLZag@mail.gmail.com>
alvise rigo <a.rigo@virtualopensystems.com> writes:
> Hi Alex,
>
> I'm looking into the worries that Sergey issued in his review of the
> last LL/SC series. The target is to reduce the TLB flushes by using an
> exclusive history of dynamic length. I don't have anything ready yet
> though.
Are you also tackling the race condition and ensuring all flushes are
done before the critical work?
Sergey has posted an RFC for his "quiescent work" solution which is
worth looking at.
>
> Best regards,
> alvise
>
> On Mon, Jun 20, 2016 at 1:57 PM, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> Hi,
>>
>> We missed the last call (sorry I was travelling). Have we any topics we
>> would like to cover this week?
>>
>> --
>> Alex Bennée
--
Alex Bennée
next prev parent reply other threads:[~2016-06-20 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 11:57 [Qemu-devel] Any topics for today's MTTCG sync-up call? Alex Bennée
2016-06-20 13:01 ` alvise rigo
2016-06-20 14:12 ` Alex Bennée [this message]
2016-06-20 14:18 ` alvise rigo
-- strict thread matches above, loose matches on Subject: below --
2016-07-04 9:46 Alex Bennée
2016-07-04 13:08 ` Alex Bennée
2016-05-23 10:57 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
2016-05-23 13:16 ` Alex Bennée
2016-05-23 15:22 ` Emilio G. Cota
2016-05-23 15:28 ` Emilio G. Cota
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=8760t4rlte.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=a.rigo@virtualopensystems.com \
--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.