All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: chenbaodong <chenbaodong@mxnavi.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	nd <nd@arm.com>
Subject: Re: [Xen-devel] [PATCH] xen/arm: io: add function swap_mmio_handler()
Date: Tue, 25 Jun 2019 09:46:00 +0100	[thread overview]
Message-ID: <7975c4d5-310f-3041-a32c-128d9237616d@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1906241435510.2468@sstabellini-ThinkPad-T480s>

HiStefano,

On 25/06/2019 00:59, Stefano Stabellini wrote:
> On Mon, 24 Jun 2019, Julien Grall wrote:
>> Hi,
>>
>> On 6/24/19 9:17 PM, Stefano Stabellini wrote:
>>> On Mon, 24 Jun 2019, Julien Grall wrote:
>>>> Hi Stefano,
>>>>
>>>> On 24/06/2019 19:27, Stefano Stabellini wrote:
>>>>> On Mon, 24 Jun 2019, Stefano Stabellini wrote:
>>>>>> On Thu, 13 Jun 2019, chenbaodong wrote:
>>>>> Let me add that if you prefer to document one of the other interfaces
>>>>> listed above in my email, you are welcome to pick another one. For
>>>>> example, we are also missing a doc about the DomU memory map, listing
>>>>> all memory regions with addresses and sizes, both MMIO and normal
>>>>> memory. For that, most of the information is:
>>>>>
>>>>> xen/include/public/arch-arm.h
>>>>>
>>>>> A well written in-code comment in arch-arm.h would be OK, or also a
>>>>> document under docs/misc/arm.
>>>>
>>>> Please no duplication, it is already quite hard to maintain one place.
>>>> Instead, we should document all the headers in a documented format that
>>>> can be extracted automatically.
>>>
>>> As we have no such thing today (as far as I am aware), please make a
>>> proposal with a bit more details, otherwise I don't think Baodong will
>>> be able to take the next step.
>>
>> I don't have a concrete proposal so far. Except that documentation outside of
>> the headers is a no-go from my side. The goal of documenting within the
>> headers rather than outside is you also help the developer of guest OS.
>>
>> A few weeks ago Ian Jackson pointed to docs/xen-headers for a potential
>> syntax. Sadly, there are no documentation of the script so far. I haven't had
>> time to look it so far.
> 
> In that case, I'd suggest for Baodong to either pick the device tree
> documentation item (assuming you are OK with that one being under
> docs/misc/arm) or just write a normal in-code comment in arch-arm.h for
> the domU memory map not worrying about the format of the in-code comment
> for now.

I don't think we have specific place for documenting device-tree so 
docs/misc/arm would be suitable.

Regarding in-code comment in arch-arm.h This will always be an improvement to 
what we have. However, it would be good if someone take an action to formalize 
the documentation format.

Cheers,

-- 
Julien Grall

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

  reply	other threads:[~2019-06-25  8:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  5:42 [Xen-devel] [PATCH] xen/arm: io: add function swap_mmio_handler() Baodong Chen
2019-06-12  9:08 ` Julien Grall
2019-06-12 10:08   ` chenbaodong
2019-06-12 12:21     ` Julien Grall
2019-06-13  0:31       ` chenbaodong
2019-06-24 18:18         ` Stefano Stabellini
2019-06-24 18:27           ` Stefano Stabellini
2019-06-24 19:27             ` Julien Grall
2019-06-24 20:17               ` Stefano Stabellini
2019-06-24 21:18                 ` Julien Grall
2019-06-24 23:59                   ` Stefano Stabellini
2019-06-25  8:46                     ` Julien Grall [this message]
2019-06-27 23:30                       ` chenbaodong

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=7975c4d5-310f-3041-a32c-128d9237616d@arm.com \
    --to=julien.grall@arm.com \
    --cc=chenbaodong@mxnavi.com \
    --cc=nd@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 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.