qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	alex@alex.org.uk, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] PPC: Timer issues with git master
Date: Thu, 17 Oct 2013 16:53:30 +0200	[thread overview]
Message-ID: <525FF9EA.5020903@redhat.com> (raw)
In-Reply-To: <525FF6CE.1010003@ilande.co.uk>

Il 17/10/2013 16:40, Mark Cave-Ayland ha scritto:
> 
> Hi Paolo,
> 
> I've just attempted a bisection testing HelenOS, but I'm struggling to
> get a consistent result. Even with the same binary across multiple runs
> then sometimes I see the issue with frequent timer pauses, and sometimes
> I don't which makes tracking this down very difficult.
> 
> What I do see post-timer-rework is that when it does occur, the screen
> redraws become really really slow; rectangular blocks (maybe 2 per sec
> or so?) are redrawn very slowly working their way down the screen. I
> have a feeling from memory that HelenOS does tend to hit the timer
> interrupts quite hard on PPC so could it be that the new code somehow
> blocks screen updates under high timer interrupt load?
> 
> As for the FreeBSD issue, this seems to be something different from the
> HelenOS issue and I see it even with QEMU 1.6. A quick browse around the
> git logs points me towards this as a possible suspect:
> http://git.qemu.org/?p=qemu.git;a=commit;h=a0f9fdfd98cc0571f9921a7eadd7316532e3e289.

Can you try reverting this on top of git master (and test both guests)?

Paolo

  reply	other threads:[~2013-10-17 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 22:27 [Qemu-devel] PPC: Timer issues with git master Mark Cave-Ayland
2013-10-11  8:44 ` Paolo Bonzini
2013-10-17 14:40   ` Mark Cave-Ayland
2013-10-17 14:53     ` Paolo Bonzini [this message]
2013-10-17 15:16       ` Mark Cave-Ayland
2013-10-17 15:32         ` Alex Bligh
2013-10-11 14:41 ` Alex Bligh

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=525FF9EA.5020903@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=alex@alex.org.uk \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).