From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bhupinder Thakur <bhupinder.thakur@linaro.org>
Cc: xen-devel@lists.xenproject.org,
Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 1/1] xen/arm: Add pl011 uart support in Xen for guest domains
Date: Mon, 6 Feb 2017 13:35:40 -0500 [thread overview]
Message-ID: <20170206183540.GH21148@char.us.oracle.com> (raw)
In-Reply-To: <1486404548-15062-2-git-send-email-bhupinder.thakur@linaro.org>
On Mon, Feb 06, 2017 at 11:39:08PM +0530, Bhupinder Thakur wrote:
> As per "VM System Specification for ARM Processors", there is a requirement for Xen to support guest console
> over pl011 UART, which is SBSA compliant. The changes in this patch implement the pl011 emulation in Xen
> and a new pl011 console support in xenconsoled.
Heya!
Got a couple of pointers for this RFC patch.
This patch should be broken up. That is the first patch
should be the one that brings in the HVM_PARAM changes along
with documentation on how this would work on non-ARM systems.
The second patch would implement this in the generic
code (in xen/common/event_channel.c) - perhaps via an
secondary function that is NOP on x86 but not so on ARM?
Then another patch that fleshes out the emulation code in
the hypervisor, then the one in console code, and lastly
in libxl to turn this on/off.
From a short glance I would recommend you also:
- Include a doc which explains how pl011 UART works,
or at least a link.
- Remove the #if 0
- Rip out the debug printk code.
- Fix the tab/spaces alignment to match the code
- Don't hardcode paths. They should be gathered from
envionment variables (like the rest of xenconsoled does)
- If you remove the VM_PARAM_MEMORY_EVENT_ you also need to
rev up the version field.
- Include a knob in libxl to define whether the guest has
this emulation enabled or not. And if it is disabled
then the code in hypervisor should not emulate it.
- Return code for MMIO shouldn't be 1, but rather the proper
#defines.
- The vpl011_cons_intf_s looks very weird. It looks like it
is missing an design document as well? That is should there
be a header in include/xen/public/ file?
Should vpl011.h be in include/xen/public/ ? If so you need
a different license for that file.
Thanks!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-06 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 18:09 [PATCH 0/1] xen/arm: Add pl011 uart support in Xen for guest domains Bhupinder Thakur
2017-02-06 18:09 ` [PATCH 1/1] " Bhupinder Thakur
2017-02-06 18:30 ` Julien Grall
2017-02-06 18:35 ` Konrad Rzeszutek Wilk [this message]
2017-02-15 7:23 ` Bhupinder Thakur
2017-02-15 15:38 ` Konrad Rzeszutek Wilk
2017-02-16 14:34 ` Julien Grall
2017-02-17 12:35 ` Bhupinder Thakur
2017-02-17 15:29 ` Konrad Rzeszutek Wilk
2017-02-20 15:23 ` Bhupinder Thakur
2017-02-28 21:21 ` Konrad Rzeszutek Wilk
2017-02-17 15:27 ` Konrad Rzeszutek Wilk
2017-02-26 20:50 ` Julien Grall
2017-02-28 21:22 ` Konrad Rzeszutek Wilk
2017-03-01 10:51 ` Bhupinder Thakur
2017-03-01 16:44 ` Julien Grall
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=20170206183540.GH21148@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=bhupinder.thakur@linaro.org \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--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).