All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] KEXEC: disconnect all PCI devices from the PCI bus on crash
Date: Thu, 7 Jul 2011 09:03:30 -0400	[thread overview]
Message-ID: <20110707130330.GB6214@dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1107071235320.12963@kaball-desktop>

> quirks). Also resetting devices would better cover the case when a
> device is misbehaving.
> Of course we still need a whitelist for serial consoles and maybe other
> devices.

It sounds like I should post some of the patches I've that deal with
various serial console now. They actually save the BDF of the PCI serial
device so that the "whitelist" data can be easily extracted.

      reply	other threads:[~2011-07-07 13:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 12:39 [PATCH] KEXEC: disconnect all PCI devices from the PCI bus on crash Andrew Cooper
2011-07-06 12:43 ` Jan Beulich
2011-07-06 12:46   ` Andrew Cooper
2011-07-06 18:42 ` Konrad Rzeszutek Wilk
2011-07-07  8:41   ` George Dunlap
2011-07-07  8:53   ` Ian Campbell
2011-07-07  9:10     ` Jan Beulich
2011-07-07  9:12       ` Ian Campbell
2011-07-07  9:42         ` Jan Beulich
2011-07-07  9:53           ` Ian Campbell
2011-07-07 10:02             ` Andrew Cooper
2011-07-07 10:06               ` Tim Deegan
2011-07-07 10:07               ` Ian Campbell
2011-07-07 11:25               ` Jan Beulich
2011-07-07 11:21             ` Jan Beulich
2011-07-07 11:40               ` Stefano Stabellini
2011-07-07 13:03                 ` Konrad Rzeszutek Wilk [this message]

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=20110707130330.GB6214@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.