All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: mark.burton@greensocs.com, qemu-devel@nongnu.org, cota@braap.org,
	guillaume.delbergue@greensocs.com, edgar.iglesias@gmail.com,
	fred.konrad@greensocs.com
Subject: Re: [Qemu-devel] MTTCG next version?
Date: Tue, 01 Sep 2015 17:07:34 +0100	[thread overview]
Message-ID: <87lhcqi0mx.fsf@linaro.org> (raw)
In-Reply-To: <1267437413.19435982.1440601647923.JavaMail.zimbra@zmail13.collab.prod.int.phx2.redhat.com>


Paolo Bonzini <pbonzini@redhat.com> writes:

> I am on vacation so no calls for me, but I *might* be able to send a pull request with the linux-user patches (and signal-free kick if reviewed). My queue is already long, and Emilio had useful fixups so he obviously tested/reviewed them. It will not be signed though as I tend not to have the key with me when travelling.
>
> Just one thing: do not squash too much into existing patches if possible. Leaving things protected by the BQL and only moving it to tb_lock in a subsequent patch is perfectly fine.
>
> Alex, please post the to-do list when you have time. More
> parallelization of the work or possible, especially as the focus
> slowly moves from "getting it working" to covering more architectures.

I too am on holiday but I'll get the notes tidied up and posted later in
the week when the kids are back to school ;-)

>
> Paolo
>
>
> -----Original Message-----
> From: Mark Burton [mark.burton@greensocs.com]
> Received: mercoledì, 26 ago 2015, 14:21
> To: KONRAD Frédéric [fred.konrad@greensocs.com]
> CC: qemu-devel [qemu-devel@nongnu.org]; Alex Bennée [alex.bennee@linaro.org]; mttcg@greensocs.com, Paolo Bonzini [pbonzini@redhat.com]; Guillaume Delbergue [guillaume.delbergue@greensocs.com]; Edgar E. Iglesias [edgar.iglesias@gmail.com]; Emilio G. Cota [cota@braap.org]
> Subject: Re: MTTCG next version?
>
> Just to remind everybody as well - we’ll have a call next Monday to co-ordinate.
> It would be good to make sure everybody knows which bit of this everybody else is committing to do, so we avoid replication and treading on each others patch sets.
>
> Cheers
>
> Mark.
>
>> On 26 Aug 2015, at 14:18, Frederic Konrad <fred.konrad@greensocs.com> wrote:
>> 
>> Hi everybody,
>> 
>> I'm trying to do the next version of the MTTCG work:
>> 
>> I would like to rebase on Alvise atomic instruction branch:
>>  - Alvise can you rebase it on the 2.4.0 version without MTTCG support and then
>>    point me to the MTTCG specific changes so I can include them in my tree?
>> I will add Paolo's linux-user and signal free qemu_cpu_kick series as well.
>> 
>> About tb_flush we think to do that without exiting:
>>  - Use two buffers for tbs.
>>  - Use a per tb invalidated flag.
>>  - when tb_flush just invalidate all tb from the buffer and swap to the second buffer:
>>    VCPU which are executing code will discard their tb_jmp_cache when they exit
>>    (eg: run_on_cpu).
>> 
>> We need also to fix emulated data barrier so tlb_flush are finished before the
>> instruction is executed. (That might be only data barrier breaks the TB).
>> 
>> Protecting page->code_bitmap and cpu_breakpoint_insert changes will be squashed in the tb_lock patch.
>> 
>> More tests must be done especially with gdbstub and icount.
>> 
>> Do that make sense?
>> Fred
>
>
> 	 +44 (0)20 7100 3485 x 210
>  +33 (0)5 33 52 01 77x 210
>
> 	+33 (0)603762104
> 	mark.burton

-- 
Alex Bennée

  reply	other threads:[~2015-09-01 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 12:18 [Qemu-devel] MTTCG next version? Frederic Konrad
2015-08-26 12:21 ` Mark Burton
2015-08-26 15:07   ` Paolo Bonzini
2015-09-01 16:07     ` Alex Bennée [this message]
2015-08-26 18:34 ` Emilio G. Cota
2015-08-31  7:30 ` alvise rigo

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=87lhcqi0mx.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=cota@braap.org \
    --cc=edgar.iglesias@gmail.com \
    --cc=fred.konrad@greensocs.com \
    --cc=guillaume.delbergue@greensocs.com \
    --cc=mark.burton@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 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.