From: Roland Dreier <rdreier@cisco.com>
To: Simon Horman <horms@verge.net.au>
Cc: linux-kernel@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>,
       kexec@lists.infradead.org
Subject: Re: kexec reboot broken with ioatdma?
References: <ada3a3a8v1g.fsf@roland-alpha.cisco.com>
	<20091216224912.GC16219@verge.net.au>
	<aday6l27c7w.fsf@roland-alpha.cisco.com>
	<20091216233613.GA22449@verge.net.au>
Date: Wed, 16 Dec 2009 15:42:20 -0800
In-Reply-To: <20091216233613.GA22449@verge.net.au> (Simon Horman's message of
	"Thu, 17 Dec 2009 10:36:13 +1100")
Message-ID: <adapr6e7ag3.fsf@roland-alpha.cisco.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 648
Lines: 30


 > If its reset in a standard path, then yes that seems sensible to me.
 > I'm mainly concerned about avoiding something along the lines of:
 > 
 > 	if (is_booting_from_kexec)
 > 		reset_hw();

I think we all agree... the idea is to change from

	init_hw()
	{
		/* assume hw is in pristine state */
		do_init();
	}

to

	init_hw()
	{
		/* hw is in unknown state */
		reset_hw();
		do_init();
	}

 - R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/