qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: MTTCG Devel <mttcg@listserver.greensocs.com>,
	QEMU Devel <qemu-devel@nongnu.org>
Cc: Mark Burton <mark.burton@greensocs.com>,
	Alexander Spyridakis <a.spyridakis@virtualopensystems.com>,
	Claudio Fontana <claudio.fontana@huawei.com>,
	Alvise Rigo <a.rigo@virtualopensystems.com>,
	"Emilio G. Cota" <cota@braap.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Frederic Konrad <fred.konrad@greensocs.com>
Subject: [Qemu-devel] MTTCG sync-up call summary 28/09/2015
Date: Mon, 28 Sep 2015 14:51:17 +0100	[thread overview]
Message-ID: <87612utzxm.fsf@linaro.org> (raw)


Here follows a slightly abbreviated form of my notes for the sync-up
call. Please reply if anything is missing on unclear ;-)

- Alvise has posted v5 addressing Paolo's comments
  - bitmap addresses TLB size issues
  - consensus we can go with Alvise's and build on them with ideas from Emilo's series
  - Alvise will have a look through during re-basing to see if any potential conflicts
  - Hope to take best of both worlds approach with slow and fast path later
- Fred patch status
  - Waiting for latest re-base from Paolo
  - Signal Free TCG and linux-user fixes now merged upstream so re-base can be done there
- Paolo
  - Tree breakage AJB reported seems to be in merge-base but exacerbated by Paolo's MTTCG branch
    - upstream master seems much more stable, we shall see when Fred re-bases
    - Alex will hammer it when ready to check bug has disappeared
  - Outstanding work from Paolo's review:
    - missing breakpoint support
    - invalidating flag
    - locking on tb_get_next
  - Reverse playback may conflict a little when it arrives in tree
    - but still a week or so of getting into Paolo's tree
- Memory Barriers
  - Paper referenced by Emilo's patch set is good read [[https://www.cs.princeton.edu/research/techreps/TR-981-15][here]]
  - Alex will take Emilo's work for ARM on ARM testing
  - Would be nice to demo ARM on ARM/AArch64 in November
  - Alex plans to tests with all ARM barrier types by end of week
- Any work good for new people to ease in?
  - Look at breakpoints, is GDB stub working?
  - Benchmarking: perhaps get some independent numbers on both atomic implementations?

-- 
Alex Bennée

                 reply	other threads:[~2015-09-28 13:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87612utzxm.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=a.rigo@virtualopensystems.com \
    --cc=a.spyridakis@virtualopensystems.com \
    --cc=claudio.fontana@huawei.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 \
    /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).