From: Jan Beulich <jbeulich@suse.com>
To: Techguru <techguru@byiq.org>
Cc: Michal Orzel <michal.orzel@amd.com>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: Xen for Apple Silicon (M1 and beyond)
Date: Wed, 24 Jul 2024 09:07:37 +0200 [thread overview]
Message-ID: <afb2c8c8-e716-4079-9bfe-68032bdd09ec@suse.com> (raw)
In-Reply-To: <d5c3e0900db98aaaeb7fb52f16598257@mail.infomaniak.com>
On 24.07.2024 03:14, Techguru wrote:
> I am in the process of getting up to speed on your governance
> policies, applied for Coverity access to use some of the known issues
> there as training wheels, and putting my gitlab fork into good working
> order with CI.
>
> I would rather not duplicate effort which has already been proposed,
> so definitely open to any pointers, any requests for how to chunk
> things into smaller patches, any requests for particular
> ordering/sequencing of patch sets.
>
> Some obvious areas: 16k pages;
For this I'd suggest that you start with a conceptual model rather than
thinking of patches straight away. It has been the topic of past
discussions, without - iirc - conclusive results. I'm sure you're aware
that 4k page size is, sadly, baked into certain parts of the public
interface (see e.g. io/ring.h). Otoh it may well be that you're goal is
explicitly not to be able to run any guests working with 4k pages. If
so, what would need ensuring is that such guests would cleanly fail to
start, rather than crash early in a cryptic way.
Jan
> device trees; interrupts; power
> management; any essential device drivers.
>
>
>
next prev parent reply other threads:[~2024-07-24 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 1:14 Xen for Apple Silicon (M1 and beyond) Techguru
2024-07-24 7:07 ` Jan Beulich [this message]
2024-07-24 20:14 ` Stefano Stabellini
2024-07-25 18:56 ` Techguru
2024-07-25 22:41 ` Stefano Stabellini
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=afb2c8c8-e716-4079-9bfe-68032bdd09ec@suse.com \
--to=jbeulich@suse.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=techguru@byiq.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.