All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: KONRAD Frederic <fred.konrad@greensocs.com>
Cc: mttcg@greensocs.com, Mark Burton <mark@greensocs.com>,
	Paolo Bonzini <bonzini@gnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	alvise rigo <a.rigo@virtualopensystems.com>
Subject: Re: [Qemu-devel] MTTCG sync-up call today?
Date: Tue, 12 Jan 2016 15:11:43 +0000	[thread overview]
Message-ID: <87vb6yde8g.fsf@linaro.org> (raw)
In-Reply-To: <5695081C.1070101@greensocs.com>


KONRAD Frederic <fred.konrad@greensocs.com> writes:

> Le 04/01/2016 12:43, Alex Bennée a écrit :
>> Hi,
>>
>> Firstly Happy New Year, I hope everyone is refreshed and rested after
>> the holiday season ;-)
>>
>> My calender has reminded me there is a potential call today. Is it worth
>> having or will the status be pretty much as we left it last year thanks
>> to holidays?
>>
>> For my part I started going through Alvise's patch series last year
>> before the holiday started. After I've spun up back to speed today I
>> intend to finish that review.
>>
>> The current blocker on progress is the re-spin/re-base of Fred's patches
>> I think. I had a bit of a look last year and I think we identified at
>> least one major problem with the exit_request stuff which Paolo reminded
>> me had been mentioned before.
>>
>> Fred if you are struggling to find time I can pick up the current WIP
>> branch and see if I can get it into shape for submission?
>>
>> Cheers,
>>
>> --
>> Alex Bennée
>
> Hi,
>
> Sorry for the late answer, I find some time to take a look at it.
>
> Seems you were right I fixed the exit issue and it seems it was one of
> the problem.
> I think we must double check how we use cpu->exit_request as Paolo
> removed SIG_IPI to exit the CPU.
>
> I found one additional issue and it seems booting well right now.

The other thing that needs cleaning up is the tcg_current_cpu and
current_cpu. I suspect the former should go and the restrictions on the
later be loosend so the TLS current_cpu is available to deferred tasks.

The thing I'm currently looking at is what happens when something like a
virtio completes in a non-CPU thread.

>
> Tomorrow I'll test that a little more, try to clean that up and
> hopefully send you a link to the repo.
>
> Thanks,
> Fred


--
Alex Bennée

       reply	other threads:[~2016-01-12 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r3hx6040.fsf@linaro.org>
     [not found] ` <5695081C.1070101@greensocs.com>
2016-01-12 15:11   ` Alex Bennée [this message]
2016-01-12 15:19     ` [Qemu-devel] MTTCG sync-up call today? Paolo Bonzini
2016-01-12 16:13       ` Alex Bennée
2016-01-12 16:19         ` Paolo Bonzini
2016-01-12 16:32           ` Alex Bennée
2016-01-12 16:43             ` Paolo Bonzini
2016-01-12 17:05               ` Alex Bennée
2016-01-12 17:08                 ` Paolo Bonzini
2016-01-12 17:08                 ` Paolo Bonzini
2016-04-25  9:53 [Qemu-devel] MTTCG Sync-up " Alex Bennée
2016-04-25 10:32 ` alvise rigo
2016-04-25 10:33   ` Mark Burton
  -- strict thread matches above, loose matches on Subject: below --
2016-05-09 11:56 Alex Bennée
2016-05-09 12:03 ` KONRAD Frederic
2016-05-09 12:11 ` alvise rigo
2016-05-09 12:41   ` Alex Bennée

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=87vb6yde8g.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=a.rigo@virtualopensystems.com \
    --cc=bonzini@gnu.org \
    --cc=fred.konrad@greensocs.com \
    --cc=mark@greensocs.com \
    --cc=mttcg@greensocs.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.