From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Shawn Anastasio <shawn@anastas.io>, xen-devel@lists.xenproject.org
Cc: tpearson@raptorengineering.com,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH 0/3] Initial support for Power
Date: Wed, 7 Jun 2023 20:30:09 +0100 [thread overview]
Message-ID: <704339f1-4103-62ad-49f8-b7df1fc8b7de@citrix.com> (raw)
In-Reply-To: <CT6NFAE37O7K.215IO8HD8PTWU@Shawns-Mac-mini.lan>
On 07/06/2023 8:01 pm, Shawn Anastasio wrote:
>> If you look around in the Xen tree at bb62c25e3e5c and take the makefile
>> override's in particular, you should be able to get `make -C xen build`
>> work without any magic TARGET= overrides, and without most of the
>> headers you've added in patch 1. The trick is to have a head.S which
>> doesn't include any files (except the config.h it gets implicitly).
> Perfect. I'll start work on a v2 without the TARGET= overrides and
> without the headers in patch #1.
Ok, in which case you probably want a first patch series doing:
1) New docker container (only - this wants to be taken early and set up
in CI)
2) one-or-more initial build system + head.S infinite loop patch.
Probably the maintainer patch too.
3) Wiring the build(s) into build.yaml
You'll want to join the https://gitlab.com/xen-project/ and I can set
you up with a place to run the full CI (we have a reasonably custom
setup which the communal runners don't like). You may also want to hang
out on oftc.org #xendevel and/or the matrix bridge thereof.
Then a second patch series doing early printk, and adding the smoke test
script and wiring it into test.yaml.
~Andrew
next prev parent reply other threads:[~2023-06-07 19:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 15:06 [PATCH 0/3] Initial support for Power Shawn Anastasio
2023-06-07 15:06 ` [PATCH 1/3] xen: Add files needed for minimal Power build Shawn Anastasio
2023-06-09 9:15 ` Jan Beulich
2023-06-09 15:34 ` Shawn Anastasio
2023-06-07 15:06 ` [PATCH 2/3] xen/ppc: Implement early serial printk on PaPR/pseries Shawn Anastasio
2023-06-09 9:22 ` Jan Beulich
2023-06-09 9:29 ` Andrew Cooper
2023-06-09 9:38 ` Jan Beulich
2023-06-09 9:43 ` Julien Grall
2023-06-09 9:43 ` Andrew Cooper
2023-06-09 9:46 ` Julien Grall
2023-06-09 9:54 ` Andrew Cooper
2023-06-09 10:12 ` Julien Grall
2023-06-09 15:01 ` Shawn Anastasio
2023-06-09 16:07 ` Julien Grall
2023-06-09 16:20 ` Shawn Anastasio
2023-06-12 15:19 ` George Dunlap
2023-06-12 15:31 ` Julien Grall
2023-06-13 14:59 ` Shawn Anastasio
2023-06-09 15:36 ` Shawn Anastasio
2023-06-07 15:06 ` [PATCH 3/3] maintainers: Add PPC64 maintainer Shawn Anastasio
2023-06-09 9:04 ` Jan Beulich
2023-06-09 15:40 ` Shawn Anastasio
2023-06-07 18:07 ` [PATCH 0/3] Initial support for Power Andrew Cooper
2023-06-07 19:01 ` Shawn Anastasio
2023-06-07 19:30 ` Andrew Cooper [this message]
2023-06-08 15:19 ` Shawn Anastasio
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=704339f1-4103-62ad-49f8-b7df1fc8b7de@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=shawn@anastas.io \
--cc=sstabellini@kernel.org \
--cc=tpearson@raptorengineering.com \
--cc=wl@xen.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).