On Tue, Sep 18, 2012 at 04:06:49PM +0100, Greg KH wrote:
> On Tue, Sep 18, 2012 at 10:42:30AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, Sep 18, 2012 at 12:23:02PM +0100, Jan Beulich wrote:
> > > Just like for the in-tree early console debug port driver, the
> > > hypervisor - when using a deb
On Tue, Sep 18, 2012 at 10:42:30AM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 18, 2012 at 12:23:02PM +0100, Jan Beulich wrote:
> > Just like for the in-tree early console debug port driver, the
> > hypervisor - when using a debug port based console - also needs to be
> > told about controlle
On Tue, Sep 18, 2012 at 12:23:02PM +0100, Jan Beulich wrote:
> Just like for the in-tree early console debug port driver, the
> hypervisor - when using a debug port based console - also needs to be
> told about controller resets, so it can suppress using and then
> re-initialize the debug port acco
On Tue, 18 Sep 2012, Jan Beulich wrote:
> Just like for the in-tree early console debug port driver, the
> hypervisor - when using a debug port based console - also needs to be
> told about controller resets, so it can suppress using and then
> re-initialize the debug port accordingly.
>
> Other
Just like for the in-tree early console debug port driver, the
hypervisor - when using a debug port based console - also needs to be
told about controller resets, so it can suppress using and then
re-initialize the debug port accordingly.
Other than the in-tree driver, the hypervisor driver actual
