qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: [PATCH 5/5] RFC: distinguish warm reset from cold r


From: Avi Kivity
Subject: Re: [Qemu-devel] Re: [PATCH 5/5] RFC: distinguish warm reset from cold reset.
Date: Tue, 31 Aug 2010 19:04:31 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100806 Fedora/3.1.2-1.fc13 Thunderbird/3.1.2

 On 08/31/2010 06:00 PM, Anthony Liguori wrote:
On 08/31/2010 09:03 AM, Avi Kivity wrote:
There's no such thing as a global reset. There's a trace on the board that's called RESET that's connected to many chip's RESET input (but perhaps not all). A PCI bus controller will likely propagate its RESET input into the PCI reset signal, however it's called. So individual RESET traces are connected by chips, which have different conditions for asserting them.

So yes, we need a custom traversal. Some bus controllers will block off RESET completely, some will pass it through, some can reset the devices on their bus independently of the controller's RESET input, if it has one.

(but I think we're drifting off into pointlessness here)

That's my source of confusion. I know hardware does a custom transversal but from a functional perspective, do we care?

So far, no one has answered this with, "yes, because device XX propagates in a specific ordering of child a, b, c, d..." which I take to mean that the answer is no.


I don't think there's an issue with the order of propagation, just whether propagation takes place or not.

I'd make all bus models explicitly propagate reset if they want to.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]