xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>, Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Dirk Behme <dirk.behme@de.bosch.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform
Date: Thu, 7 Jul 2016 14:14:53 +0100	[thread overview]
Message-ID: <577E55CD.3030408@arm.com> (raw)
In-Reply-To: <64F9B0C3-D696-4564-915B-8EE8390AC9C4@gmail.com>



On 07/07/16 13:43, Lars Kurth wrote:
>
>> On 7 Jul 2016, at 12:28, Wei Liu <wei.liu2@citrix.com> wrote:
>>
>> Also CC Lars.
>>
>> On Mon, Jul 04, 2016 at 12:12:52PM +0100, Julien Grall wrote:
>>> (CC Wei for the release part)
>>>
>>> Hi Dirk,
>>>
>>> On 04/07/16 07:51, Dirk Behme wrote:
>>>> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
>>>
>>> Thank you for adding support of a new board in Xen.
>>>
>>> During the last hackathon, we discussed about improving pre-release testing
>>> on ARM hardware [1] and helping users to boot Xen on supported board.
>>>
>>> This patch is the first board officially supported since then, so I would
>>> like to start applying what was discussed (I will put on a wiki page later).
>>> Below the list of things that I would like to see when a new board is added:
>>>
>>>    - Create a wiki page to explain the requirements to boot Xen on the board
>>> (e.g new firmware if not supported out of box, linux version,...);
>>>    - Add a link to the new page in [2];
>>>    - Add the contact details in [3] of someone who would could test
>>> pre-release and help out users to boot Xen on the board.
>>>
>>> I do not expect the latter point to be time consuming. It is basically
>>> checking if Xen boots before each release and possibly update the
>>> requirements of the board. For the part helping users, it will mostly be
>>> question related to booting Xen on the hardware. Others may not be able to
>>> answer because they do not have the board on their desk.
>>>
>>
>> FWIW having some wiki pages, and most importantly contact details, would
>> be a good starting point.
>
> I did actually create these pages during the Hackathon and sent it out to the list, but they were not populated by anyone. See
> http://wiki.xenproject.org/wiki/Xen_ARM_Manual_Smoke_Test
> http://wiki.xenproject.org/wiki/Xen_ARM_Manual_Smoke_Test/Results
>
>> Can we also have a section in MAINTAINERS for different boards (or a
>> dedicated file?) so that we can easily gather all contact and send
>> emails in a batch when the release is near?
>
> I am not in principle against this, but a concrete proposal would need to be made. In fact that may be better than using the wiki (given the lack of traction around it)

I think a file in the repository would be more formal than a wiki page.

However, the MAINTAINERS file may not be the right place because some 
board will not have any specific code/file in Xen (e.g the RCAR-3 only 
add earlyprintk). But we would still want to keep track of them for 
testing purpose and advertising the board supported.

I was thinking to add a file board under docs/misc/arm/boards.txt with 
the list of board and a contact associated I would add some words about 
the "responsibility" of the contact such as:
    - Testing
    - Answering questions related to the board

I would also keep the wiki page [1] (+ a link in the file) to log the 
testing result per release.

Finally, we may want to track whether the board is "supported", 
"obsolete", "untested"...

I will try to write a concrete proposal.

Cheers,

[1] http://wiki.xenproject.org/wiki/Xen_ARM_Manual_Smoke_Test/Results

-- 
Julien Grall

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

  reply	other threads:[~2016-07-07 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04  6:51 [PATCH] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform Dirk Behme
2016-07-04 11:12 ` Julien Grall
2016-07-07 11:28   ` Wei Liu
2016-07-07 12:43     ` Lars Kurth
2016-07-07 13:14       ` Julien Grall [this message]
2016-07-07 13:17         ` Lars Kurth
2016-07-07 13:20           ` Andrew Cooper
2016-07-07 13:31             ` Stefano Stabellini
2016-07-07 13:43         ` Wei Liu

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=577E55CD.3030408@arm.com \
    --to=julien.grall@arm.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=sstabellini@kernel.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).