qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Drop obsolete nographic timer
Date: Fri, 16 Mar 2012 01:52:55 +0100	[thread overview]
Message-ID: <201203160152.55783.marek.vasut@gmail.com> (raw)
In-Reply-To: <4F6264EF.90709@web.de>

Dear Jan Kiszka,

> On 2012-03-15 19:12, Marek Vasut wrote:
> > Dear Marek Vasut,
> > 
> >> Dear Jan Kiszka,
> >> 
> >>> On 2012-03-10 07:19, Marek Vasut wrote:
> >>>> Dear Jan Kiszka,
> >>>> 
> >>>>> We flush coalesced MMIO in the device models now, and VNC - for which
> >>>>> this was once introduced - is also fine without it as it has its own
> >>>>> refresh timer.
> >>>>> 
> >>>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> >>>>> ---
> >>>>> 
> >>>>>  vl.c |   13 -------------
> >>>>>  1 files changed, 0 insertions(+), 13 deletions(-)
> >>>> 
> >>>> This patch seems to break QEMU/PXA emulation for me on the ZipitZ2
> >>>> platform. The serial console became very slow, but only when I type
> >>>> something in. The output from the device to the console is ok. After
> >>>> reverting this particular one, the console behaves normally.
> >>> 
> >>> Removing that timer removal likely just revealed some formerly hidden
> >>> bug. Can you share the command line used for starting and some test
> >>> image?
> >>> 
> >>> Jan
> >> 
> >> qemu-system-arm -M z2 -pflash flash.img -serial null -serial null
> >> -serial stdio -display none
> >> 
> >> flash.img attached (XZ-ed)
> > 
> > Bump?
> 
> I had a brief look: The guest is apparently polling the uart, IRQ
> delivery is disabled.

Yes, it is.

> But it also receives no timer ticks. I haven't
> checked how it progresses, maybe there is some loop counter used.

What do you mean? How does the timer implementation in pxa-uboot work? udelay() 
calls on the guest (pxa-uboot) simply poll the timer until it reaches certain 
value. There's no paralelism going on at all.

> 
> What's the origin of this test image? Have you checked it works properly
> on real silicon?

Yep.

> I do not know how this platform looks like in reality,
> how it should behave and should be programmed (by the guest), so I
> really can't compare and analyze, sorry.

I'm the maintainer, nice to meet you ;-) Real silicon is a small clamshell pc-
like device. But this breaks all xscale stuff in qemu.

> 
> Jan

Best regards,
Marek Vasut

  reply	other threads:[~2012-03-16  0:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 10:31 [Qemu-devel] [PATCH 2/2] Drop obsolete nographic timer Jan Kiszka
2011-10-14  0:05 ` David Gibson
2011-11-01 20:10   ` Anthony Liguori
2011-11-01 20:15     ` Blue Swirl
2011-11-01 20:20       ` Anthony Liguori
2012-03-10  6:19 ` Marek Vasut
2012-03-10 10:44   ` Jan Kiszka
2012-03-11 23:39     ` Marek Vasut
2012-03-15 18:12       ` Marek Vasut
2012-03-15 21:53         ` Jan Kiszka
2012-03-16  0:52           ` Marek Vasut [this message]
2012-03-16  8:17             ` Jan Kiszka
2012-03-16  8:55               ` Paolo Bonzini

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=201203160152.55783.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=jan.kiszka@web.de \
    --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).