xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: StefanoStabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Wilk <konrad.wilk@oracle.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 10/17] SUPPORT.md: Add Debugging, analysis, crash post-portem
Date: Thu, 23 Nov 2017 17:08:46 +0000	[thread overview]
Message-ID: <c064cbfd-c17c-493e-66ff-6874620ffee1@citrix.com> (raw)
In-Reply-To: <5A16BBDA0200007800191538@prv-mh.provo.novell.com>

On 11/23/2017 11:15 AM, Jan Beulich wrote:
>>>> On 22.11.17 at 20:20, <george.dunlap@citrix.com> wrote:
>> +## Debugging, analysis, and crash post-mortem
>> +
>> +### Host serial console
>> +
>> +    Status, NS16550: Supported
>> +	Status, EHCI: Supported
> 
> Inconsistent indentation.

And I was so sure I'd checked all those. :-/

> 
>> +	Status, Cadence UART (ARM): Supported
>> +	Status, PL011 UART (ARM): Supported
>> +	Status, Exynos 4210 UART (ARM): Supported
>> +	Status, OMAP UART (ARM): Supported
>> +	Status, SCI(F) UART: Supported
>> +
>> +XXX Should NS16550 and EHCI be limited to x86?  Unlike the ARM
>> +entries, they don't depend on x86 being configured
> 
> ns16550 ought to be usable everywhere. EHCI is x86-only
> anyway (presumably first of all because it takes PCI as a prereq)

But that's just an accident at the moment; I thought there were plans at
some point for ARM servers to have PCI, weren't there?

I'll probably just leave this as it is, unless someone thinks differently.

> With this XXX dropped (and with or without adding (x86) to
> EHCI)
> Acked-by: Jan Beulich <jbeulich@suse.com>

Thanks,
 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2017-11-23 17:08 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 19:20 [PATCH v3 01/17] Introduce skeleton SUPPORT.md George Dunlap
2017-11-22 19:20 ` [PATCH v3 02/17] SUPPORT.md: Add core functionality George Dunlap
2017-11-23 10:46   ` Jan Beulich
2017-11-22 19:20 ` [PATCH v3 03/17] SUPPORT.md: Add some x86 features George Dunlap
2017-11-23 10:47   ` Jan Beulich
2017-11-22 19:20 ` [PATCH v3 04/17] SUPPORT.md: Add core ARM features George Dunlap
2017-11-23 11:11   ` Julien Grall
2017-11-23 11:13     ` George Dunlap
2017-11-23 11:15       ` Julien Grall
2017-11-22 19:20 ` [PATCH v3 05/17] SUPPORT.md: Toolstack core George Dunlap
2017-11-24 16:26   ` Ian Jackson
2017-11-27 10:27     ` George Dunlap
2017-11-27 11:43   ` Roger Pau Monné
2017-11-27 14:12     ` George Dunlap
2017-11-27 14:39       ` Roger Pau Monné
2017-11-27 14:40         ` George Dunlap
2017-11-27 14:58         ` George Dunlap
2017-11-27 15:02           ` Roger Pau Monné
2017-11-27 14:15     ` George Dunlap
2017-11-27 14:36       ` Roger Pau Monné
2017-11-22 19:20 ` [PATCH v3 06/17] SUPPORT.md: Add scalability features George Dunlap
2017-11-23 10:50   ` Jan Beulich
2017-11-23 16:52     ` George Dunlap
2017-11-23 11:12   ` Julien Grall
2017-11-22 19:20 ` [PATCH v3 07/17] SUPPORT.md: Add virtual devices common to ARM and x86 George Dunlap
2017-11-23  8:50   ` Paul Durrant
2017-11-23 10:59   ` Jan Beulich
2017-11-23 17:02     ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 08/17] SUPPORT.md: Add x86-specific virtual hardware George Dunlap
2017-11-23 11:07   ` Jan Beulich
2017-11-27 15:12   ` Anthony PERARD
2017-11-27 16:30     ` George Dunlap
2017-11-27 16:43       ` Anthony PERARD
2017-11-22 19:20 ` [PATCH v3 09/17] SUPPORT.md: Add ARM-specific " George Dunlap
2017-11-23 11:14   ` Julien Grall
2017-11-22 19:20 ` [PATCH v3 10/17] SUPPORT.md: Add Debugging, analysis, crash post-portem George Dunlap
2017-11-23 11:15   ` Jan Beulich
2017-11-23 17:08     ` George Dunlap [this message]
2017-11-24  8:04       ` Jan Beulich
2017-11-27 14:18         ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 11/17] SUPPORT.md: Add 'easy' HA / FT features George Dunlap
2017-11-22 19:20 ` [PATCH v3 12/17] SUPPORT.md: Add Security-releated features George Dunlap
2017-11-23 11:16   ` Jan Beulich
2017-11-23 17:14     ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 13/17] SUPPORT.md: Add secondary memory management features George Dunlap
2017-11-22 19:20 ` [PATCH v3 14/17] SUPPORT.md: Add statement on PCI passthrough George Dunlap
2017-11-23 11:17   ` Jan Beulich
2017-11-27 14:48     ` George Dunlap
2017-11-27 15:04       ` Jan Beulich
2017-11-27 15:05         ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 15/17] SUPPORT.md: Add statement on migration RFC George Dunlap
2017-11-23 11:19   ` Jan Beulich
2017-11-22 19:20 ` [PATCH v3 16/17] SUPPORT.md: Add limits RFC George Dunlap
2017-11-23 11:21   ` Jan Beulich
2017-11-23 17:21     ` George Dunlap
2017-11-24  8:14       ` Jan Beulich
2017-11-27 14:35         ` George Dunlap
2017-11-22 19:20 ` [PATCH v3 17/17] SUPPORT.md: Miscellaneous additions George Dunlap

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=c064cbfd-c17c-493e-66ff-6874620ffee1@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).