qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pavel Dovgalyuk <dovgaluk@ispras.ru>
Cc: 'Aleksandr Bezzubikov' <zuban32s@gmail.com>,
	'QEMU Developers' <qemu-devel@nongnu.org>,
	'Pranith Kumar' <bobby.prani+qemu@gmail.com>,
	pavel.dovgaluk@ispras.ru,
	'Aleksandr Bezzubikov' <abezzubikov@ispras.ru>,
	'Paolo Bonzini' <pbonzini@redhat.com>,
	'Igor R' <boost.lists@gmail.com>
Subject: Re: [Qemu-devel] What is the best commit for record-replay?
Date: Tue, 31 Oct 2017 14:27:35 +0000	[thread overview]
Message-ID: <871sljie94.fsf@linaro.org> (raw)
In-Reply-To: <000d01d3523b$2e00f880$8a02e980$@ru>


Pavel Dovgalyuk <dovgaluk@ispras.ru> writes:

>> From: Alex Bennée [mailto:alex.bennee@linaro.org]
>> Aleksandr Bezzubikov <zuban32s@gmail.com> writes:
>>
>> > 2017-09-19 12:30 GMT+03:00 Alex Bennée <alex.bennee@linaro.org>:
>> >>
>> >>> As I know, RR is still broken in the current version.
>> >>> It was caused by the MTTCG implementation.
>> >>> Alex Bennee tried to fix RR back. Alex, have you found any solution?
>> >>>
>> >>> We also trying to find a way to fix RR. It seems, that we will reinvent BQL for RR.
>> >>
>> >> I think the method outlined in my RFC is the way to go, essentially the
>> >> RR mutex taking over for the what the BQL did. The RFC patch hadn't
>> >> hoisted the mutex for the additional devices so I'm just re-basing now
>> >> and I'll see if I can make the changes for Igor's test case.
>> >>
>> >> --
>> >> Alex Bennée
>>
>> Could you try:
>>
>>   https://github.com/stsquad/qemu/tree/bql-and-replay-locks-v2
>>
>> And report back?
>
> Please check the new series of the patches.
> It includes patches from Alex and some fixes that made them working.

For reference that is:

  Subject: [RFC PATCH 00/26] replay additions
  From: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
  Date: Tue, 31 Oct 2017 14:24:57 +0300
  Message-ID: <20171031112457.10516.8971.stgit@pasha-VirtualBox>

--
Alex Bennée

  reply	other threads:[~2017-10-31 14:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  8:05 [Qemu-devel] What is the best commit for record-replay? Igor R
2017-04-09  6:55 ` Pranith Kumar
2017-04-25 19:16   ` Igor R
2017-04-26 13:48     ` Alex Bennée
2017-05-02 12:42       ` Igor R
2017-09-18 12:02         ` Aleksandr Bezzubikov
2017-09-18 12:09           ` Aleksandr Bezzubikov
2017-09-19  9:17             ` Pavel Dovgalyuk
2017-09-19  9:30               ` Alex Bennée
2017-09-19 12:26                 ` Aleksandr Bezzubikov
2017-09-19 14:25                   ` Alex Bennée
2017-09-19 15:46                     ` Alexander Bezzubikov
2017-09-20  6:17                     ` Pavel Dovgalyuk
2017-10-31 11:27                     ` Pavel Dovgalyuk
2017-10-31 14:27                       ` Alex Bennée [this message]
2017-11-01  5:14                         ` Pavel Dovgalyuk

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=871sljie94.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=abezzubikov@ispras.ru \
    --cc=bobby.prani+qemu@gmail.com \
    --cc=boost.lists@gmail.com \
    --cc=dovgaluk@ispras.ru \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zuban32s@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 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).