All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <dunlapg@umich.edu>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, infra@xenproject.org
Subject: Re: [OSSTEST PATCH] README.hardware-acquisition
Date: Wed, 31 Oct 2018 17:49:50 +0000	[thread overview]
Message-ID: <CAFLBxZabx3rG1t8C+6p-+kojxq1WNOqEXn23GyB+w0OgjDYLiQ@mail.gmail.com> (raw)
In-Reply-To: <20181030161326.17879-1-ian.jackson@eu.citrix.com>

On Tue, Oct 30, 2018 at 4:14 PM Ian Jackson <ian.jackson@eu.citrix.com> wrote:
> +   + Baremetal boot from Debian stable or stable-backports:
> +
> +     A suitable Linux kernel binary which can boot baremetal on the
> +     proposed hardware must be available from Debian (at least
> +     `stable', or, if that is not possible `stable-backports').  It is
> +     not OK to require a patched version of Linux, or a version of
> +     Linux built from a particular git branch, or some such.  If the
> +     required kernel is not available in Debian, the vendor should
> +     first work with the Debian project to ensure and validate that
> +     the Debian stable-backports kernel binaries boot on the proposed
> +     hardware.

So it sounds like (from the rest of this discussion) the real
requirement is "osstest must be able to install a system such that it
can build the target versions of Linux and Xen".  At the moment, that
means that the proposed hardware must be supported by debian +
stable-backports.  Osstest does not have functionality to build custom
versions of Linux for build boxes, nor does it have support for Yocto.

Would it make sense to reword it this way:

---
+ Baremetal boot from Debian stable or stable-backports:

In order to avoid cross-compilation, Osstest must be able to install a
bare-metal system on the host itself in order to build Linux and Xen
test binaries for that host. At the moment osstest uses Debian for
this, and there is no facility in osstest for building custom kernels
for this purpose.  As such, a suitable Linux kernel binary which can
boot baremetal on the proposed hardware must be available from Debian
(at least `stable', or, if that is not possible, `stable-backports').
Osstest cannot install using a patched version of Linux, or one built
from a particular git branch, or some such.  If the required kernel is
not available in Debian, the vendor should ideally work with the
Debian project to ensure and validate that Debian stable-backports
kernel binaries boot on the proposed hardware.  Alternately, the
vendor can work with the community to implement the necessary
functionality within osstest to enable it to build custom kernels for
build installs, or use alternate distributions which have better
baremetal support for the hardware.
---

 -George

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

  parent reply	other threads:[~2018-10-31 17:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 16:13 [OSSTEST PATCH] README.hardware-acquisition Ian Jackson
2018-10-30 16:27 ` Jan Beulich
2018-10-30 20:28 ` Julien Grall
2018-10-30 22:38   ` Stefano Stabellini
2018-10-31 15:39     ` [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] Ian Jackson
2018-10-31 18:37       ` Stefano Stabellini
2018-11-01 12:42         ` [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] [and 2 " Ian Jackson
2018-11-01 18:12           ` Stefano Stabellini
2018-11-02 10:16             ` Lars Kurth
2018-11-02 14:16               ` Wei Liu
2018-11-02 16:19               ` Stefano Stabellini
2019-02-15 11:56       ` [OSSTEST PATCH] README.hardware-acquisition [and 1 " Ian Jackson
2019-02-15 12:15         ` Juergen Gross
2019-02-15 13:47         ` Lars Kurth
2019-02-15 15:40           ` Ian Jackson
2019-02-15 16:04             ` Lars Kurth
2019-02-15 17:07               ` Ian Jackson
2018-10-31 14:44   ` [OSSTEST PATCH] README.hardware-acquisition Ian Jackson
2018-10-31 18:32     ` Julien Grall
2018-10-31 17:49 ` George Dunlap [this message]
2018-10-31 17:50   ` George Dunlap
2018-10-31 18:46     ` Stefano Stabellini
2018-11-01 11:29       ` George Dunlap
2018-11-01 11:49         ` Lars Kurth
2018-11-01 17:50           ` Stefano Stabellini
2018-11-02 11:37             ` Ian Jackson
2018-11-02 15:05   ` [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] [and 2 more messages] [and 2 more messages] Ian Jackson
2018-11-02 15:38     ` Julien Grall
2018-11-02 15:44       ` Ian Jackson
2018-11-02 16:10         ` Julien Grall
2018-11-02 16:40           ` Ian Jackson
2018-11-02 17:56     ` Stefano Stabellini
2018-11-02 18:08       ` Julien Grall
2018-11-02 23:44         ` Stefano Stabellini
2018-11-05 11:08           ` Julien Grall
2018-11-05 11:32             ` Ian Jackson
2018-11-09 19:48               ` Stefano Stabellini
2018-11-05 10:55       ` Ian Jackson

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=CAFLBxZabx3rG1t8C+6p-+kojxq1WNOqEXn23GyB+w0OgjDYLiQ@mail.gmail.com \
    --to=dunlapg@umich.edu \
    --cc=ian.jackson@eu.citrix.com \
    --cc=infra@xenproject.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.