From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5)
Date: Tue, 31 Mar 2009 19:07:39 +0300 [thread overview]
Message-ID: <f43fc5580903310907k79a7b572y9c127afab8fc7711@mail.gmail.com> (raw)
In-Reply-To: <20090331112354.GA18048@amd.home.annexia.org>
On 3/31/09, Richard W.M. Jones <rjones@redhat.com> wrote:
> On Thu, Mar 26, 2009 at 08:03:47AM -0500, Anthony Liguori wrote:
> > Richard W.M. Jones wrote:
> >> -CPPFLAGS += -DHAS_AUDIO -DHAS_AUDIO_CHOICE
> >> +OBJS+= wdt_ib700.o wdt_i6300esb.o
> >> +CPPFLAGS += -DHAS_AUDIO -DHAS_AUDIO_CHOICE -DHAS_WATCHDOGS
> >
> > I don't think this is the right way to address this problem as it isn't
> > likely to scale as we add additional devices. I'd suggest either
> > registering the watch dogs in the pc init function or better yet, as
> > part of PCI/ISA initialization. Hopefully this will all get a lot
> > cleaner as Markus' device config patches get included but for now, let's
> > try to at least avoid using CFLAGS to solve this.
>
> I wasn't sure how to do this 'correctly'. If I initialize the
> watchdog in the pc_init1 code, then the initialization happens too
> late, after command line processing. So no watchdogs are registered
> in time for parsing the -watchdog flag.
>
> The patch below contains a different solution, just using '#ifdef
> TARGET_I386' as a test instead of the custom -DHAS_WATCHDOGS flag.
> This matches the conditional that adds the watchdog devices in
> Makefile.target, so everything is good.
>
> Everything else that you mentioned should be fixed in this patch.
>
> It's also been rebased to the latest SVN, in particular the big
> changes to command-line flags and documentation.
+ if (i > 0) exit (i == 1 ? 1 : 0);
+ if (!d->enabled) return;
Please split these into two lines.
next prev parent reply other threads:[~2009-03-31 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 18:49 [Qemu-devel] [PATCH] Hardware watchdog patch, version 5 Richard W.M. Jones
2009-03-25 8:43 ` Richard W.M. Jones
2009-03-26 13:03 ` Anthony Liguori
2009-03-31 11:23 ` [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5) Richard W.M. Jones
2009-03-31 11:24 ` Richard W.M. Jones
2009-03-31 16:07 ` Blue Swirl [this message]
2009-04-01 8:46 ` Richard W.M. Jones
2009-04-01 13:18 ` [Qemu-devel] Re: [PATCH] Hardware watchdog patch, version 6 Anthony Liguori
2009-04-25 12:56 ` [Qemu-devel] [PATCH] Hardware watchdog patch, version 7 Richard W.M. Jones
2009-04-07 21:19 ` [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5) Hollis Blanchard
2009-04-08 8:39 ` Richard W.M. Jones
2009-04-08 9:22 ` [libvirt] " Daniel P. Berrange
2009-04-08 14:18 ` [Qemu-devel] Re: [libvirt] Re: [PATCH] Hardware watchdog patch, version 6 Anthony Liguori
2009-04-08 14:35 ` Daniel P. Berrange
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=f43fc5580903310907k79a7b572y9c127afab8fc7711@mail.gmail.com \
--to=blauwirbel@gmail.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 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).