From: Mario Smarduch <m.smarduch@samsung.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: Virt MM DEBUG_LL support arm32
Date: Wed, 07 Oct 2015 09:40:20 -0700 [thread overview]
Message-ID: <56154AF4.60206@samsung.com> (raw)
In-Reply-To: <CAFEAcA9ShOzMG7kk9hQRgizJ_u2=Y2B5v6SXi678M1RMZQcPVA@mail.gmail.com>
On 10/7/2015 12:07 AM, Peter Maydell wrote:
> On 7 October 2015 at 01:32, Mario Smarduch <m.smarduch@samsung.com> wrote:
>> Hi Peter,
>> I noticed that icedcc, and 8250 don't work
>> with DEBUG_LL early debug print. And the kernel dies if
>> these are selected. Besides PL011 is there any other
>> serial devices that can be used for early debug with Virt MM?
>> Maybe some additional options are needed?
>
> PL011 and semihosting are the obvious choices for early
> debug output. There's no 8250 in the virt board so that
> definitely isn't going to work. We don't currently implement
> the ICE DCC channel, though I think Edgar was considering
> connecting it up to a chardev backend.
>
> Really though, I think the UART and semihosting should
> be enough for whatever the guest wants to do in the way
> of early debug. Why do you need more options?
>
> thanks
> -- PMM
>
No actually I was thinking of limiting choices to the ones that work for
Virt MM during kernel config. But thought that maybe others may be
supported through some options. Form me PL011 alone is enough.
- Mario
next prev parent reply other threads:[~2015-10-07 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 0:32 Virt MM DEBUG_LL support arm32 Mario Smarduch
2015-10-07 7:07 ` Peter Maydell
2015-10-07 16:40 ` Mario Smarduch [this message]
2015-10-07 21:05 ` Peter Maydell
2015-10-08 22:07 ` Mario Smarduch
2015-10-10 10:51 ` Christoffer Dall
2015-10-12 16:16 ` Mario Smarduch
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=56154AF4.60206@samsung.com \
--to=m.smarduch@samsung.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=peter.maydell@linaro.com \
--cc=peter.maydell@linaro.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 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.