qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Kauer <kauer@os.inf.tu-dresden.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Re: RTC polling mode broken
Date: Thu, 27 Aug 2009 15:08:19 +0200	[thread overview]
Message-ID: <20090827130819.GB9586@chrom.inf.tu-dresden.de> (raw)
In-Reply-To: <20090827123330.GO30093@redhat.com>

On Thu, Aug 27, 2009 at 03:33:30PM +0300, Gleb Natapov wrote:
> On Thu, Aug 27, 2009 at 01:18:03PM +0200, Bernhard Kauer wrote:
> > Suppose I have some software that does not run with Qemu 
> > and I have done the following steps:
> > 
> > 	1. found that it is bug in Qemu and not in my software
> > 	2. produced a patch that fixed the problem for my test-case
> > 	3. send the patch with an explanation to the mailinglist
> > 	4. waited 6 weeks for comments or inclusion in Qemu
> > 
> > Now what should I do, to get the bug fixed?
> > 
> Resend the patch? (no need to what for 6 week to do that BTW)

How often?


	Bernhard



> > On Wed, Jul 15, 2009 at 12:50:43PM +0200, Bernhard Kauer wrote:
> > > The RTC emulation does not set the IRQ flags independent of the IRQ enable bits.
> > > 
> > > The original MC146818A datasheet from 1984 notes:
> > > 	"flag bits in Register C [...] are set independent of the
> > > 	state of the corresponding enable bits in Register B"
> > > Similar sections can be found in newer documentation e.g. in rtc82885.
> > > 
> > > Qemu and Bochs set the IRQ flags only if they are enabled,
> > > which breaks drivers polling on them.
> > > 
> > > The following patch corrects this for the update-ended-flag in Qemu only.
> > > It currently does not fix the handling of the other flags.
> > > 
> > > 
> > > Signed-off-by: Bernhard Kauer <kauer@tudos.org>
> > > 
> > > 
> > > diff --git a/hw/mc146818rtc.c b/hw/mc146818rtc.c
> > > index 2022548..2b040a7 100644
> > > --- a/hw/mc146818rtc.c
> > > +++ b/hw/mc146818rtc.c
> > > @@ -421,9 +421,10 @@ static void rtc_update_second2(void *opaque)
> > >      }
> > >  
> > >      /* update ended interrupt */
> > > +    s->cmos_data[RTC_REG_C] |= REG_C_UF;
> > >      if (s->cmos_data[RTC_REG_B] & REG_B_UIE) {
> > > -        s->cmos_data[RTC_REG_C] |= 0x90;
> > > -        rtc_irq_raise(s->irq);
> > > +      s->cmos_data[RTC_REG_C] |= REG_C_IRQF;
> > > +      rtc_irq_raise(s->irq);
> > >      }
> > >  
> > >      /* clear update in progress bit */
> > 

  reply	other threads:[~2009-08-27 13:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 10:50 [Qemu-devel] RTC polling mode broken Bernhard Kauer
2009-08-27 11:18 ` Bernhard Kauer
2009-08-27 12:33   ` Gleb Natapov
2009-08-27 13:08     ` Bernhard Kauer [this message]
2009-08-27 13:17       ` [Qemu-devel] [PATCH] " Gleb Natapov

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=20090827130819.GB9586@chrom.inf.tu-dresden.de \
    --to=kauer@os.inf.tu-dresden.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).