qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: mttcg@listserver.greensocs.com,
	Alvise Rigo <a.rigo@virtualopensystems.com>,
	pbonzini@redhat.com, Frederic Konrad <fred.konrad@greensocs.com>,
	Jan Kiszka <jan.kiszka@siemens.com>
Cc: Mark Burton <mark.burton@greensocs.com>,
	claudio.fontana@huawei.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Summary of MTTCG Call 3/8/2015
Date: Wed, 05 Aug 2015 13:25:00 +0100	[thread overview]
Message-ID: <874mkdly77.fsf@linaro.org> (raw)

Hi,

Seeing as the last summary was useful I thought I'd send out some fresh
notes:

Alex discussed his barrier tests which where posted to the list last
week. There is some behaviour that needs explaining w.r.t to barrier
only approaches which should fail in real hardware but don't. Alvise
prompted he notices the Load Acquire/Store Release semantics were new
for ARMv8 and Alex replied we'd need to look at the barrier stuff later
but they likely need testing on non-x86 backends where we'll need to be
careful to express full barrier semantics.

Fred talked about progress on the main patch set which is re-based on
the recent -rc0 release. He hopes to post the latest set of patches this
week.

Alvise also expects to post updated patch series for the
atomic/exclusive code this week. He's maintaining two trees at the
moment, one based direct off mainline QEMU and then a MTTCG aware
version. There was some discussion about how to proceed with the other
backends. The general consensus was as long as the patches didn't break
the other builds we could submit to the mainline list and ask for help
from other TCG experts. The changes are expected to be fairly
mechanical.

There was some general discussion about the current status of MTTCG
and the consensus was we are generally happy with the functionality.
There where a number of comments about making the MTTCG build friendly
to being disabled on different platforms (v4 was broken on
non-x86/non-arm). We shall see what the community thinks once the next
set of patches goes out.

Mark asked for advanced copies of the presentation Alex is giving at
KVMForum and he replied he'd hope to get wider circulation this week
after an internal review. He would also contact Fred offline to discuss
the demo options for the talk.

Finally it was agreed with KVM Forum only 2 weeks away to have the next
conference on Monday.


-- 
Alex Bennée

             reply	other threads:[~2015-08-05 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 12:25 Alex Bennée [this message]
2015-08-05 15:03 ` [Qemu-devel] Summary of MTTCG Call 3/8/2015 Claudio Fontana

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=874mkdly77.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=a.rigo@virtualopensystems.com \
    --cc=claudio.fontana@huawei.com \
    --cc=fred.konrad@greensocs.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mark.burton@greensocs.com \
    --cc=mttcg@listserver.greensocs.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).