From: Peter Maydell <peter.maydell@linaro.org>
To: Danny Canter <danny_canter@apple.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Cameron Esfahani <dirty@apple.com>,
rbolshakov@ddn.com, agraf@csgraf.de
Subject: Re: [PATCH] hvf: arm: Allow creating VMs with > 63GB of RAM on macOS 15+
Date: Tue, 13 Aug 2024 10:31:54 +0100 [thread overview]
Message-ID: <CAFEAcA9XXhsUeHNjsVkjhjO2_Njkk=L00BG+24xtXWWKgJayRw@mail.gmail.com> (raw)
In-Reply-To: <E03A8C36-4079-468F-9596-328D713C3611@apple.com>
On Mon, 12 Aug 2024 at 23:18, Danny Canter <danny_canter@apple.com> wrote:
> On Aug 12, 2024, at 10:52 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
> > This is unfortunately probably going to imply a bit of extra
> > plumbing to be implemented for hvf -- that MachineClass::kvm_type
> > method is (as the name suggests) KVM specific. (Multi-patch
> > patchset for that, where we add the plumbing in as its own
> > separate patch (and/or whatever other split of functionality
> > into coherent chunks makes sense), rather than one-big-patch, please.)
>
> That’s perfectly fine, I’ll try and see how the plumbing was done
> for KVM and try and emulate where it makes sense
> for HVF. Agree though, that’d definitely push this into multi-patch
> territory. Curious if you think what’s here today should
> be multiple patches or the current work seems fine in one?
I think it was fine as one patch. My personal preference
when I write code tends to go for more-smaller-patches
over fewer-larger-patches, so I might have for example
split out "Add hvf_arch_vm_create()" into its own
patch, but that's very borderline, and I wouldn't ask for
that change at code review time unless the patch as a whole
was too big and unwieldy and I was looking for places to
suggest a split into multiple patches.
-- PMM
next prev parent reply other threads:[~2024-08-13 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 23:00 [PATCH] hvf: arm: Allow creating VMs with > 63GB of RAM on macOS 15+ Danny Canter
2024-07-29 16:27 ` Peter Maydell
2024-07-30 21:53 ` Danny Canter
2024-07-31 8:26 ` Peter Maydell
2024-08-12 14:52 ` Peter Maydell
2024-08-12 22:18 ` Danny Canter
2024-08-13 9:31 ` Peter Maydell [this message]
2024-08-17 0:36 ` Danny Canter
2024-08-20 13:42 ` Peter Maydell
2024-09-05 18:45 ` Danny Canter
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='CAFEAcA9XXhsUeHNjsVkjhjO2_Njkk=L00BG+24xtXWWKgJayRw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=agraf@csgraf.de \
--cc=danny_canter@apple.com \
--cc=dirty@apple.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rbolshakov@ddn.com \
/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).