From: Marc Zyngier <maz@kernel.org>
To: Bernhard Kauer <bk@alpico.io>
Cc: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: make uevents configurable
Date: Wed, 27 Nov 2024 09:04:55 +0000 [thread overview]
Message-ID: <86bjy1ujwo.wl-maz@kernel.org> (raw)
In-Reply-To: <Z0bao0moyeDgqBDU@mias.mediconcil.de>
On Wed, 27 Nov 2024 08:38:59 +0000,
Bernhard Kauer <bk@alpico.io> wrote:
>
> On Tue, Nov 26, 2024 at 11:23:10AM +0000, Marc Zyngier wrote:
> > > > I'm not overly keen on the command-line flag though, as this is the
> > > > sort of things you'd like to be able to control more finely. Or at
> > > > least without having to trigger a reboot.
> > >
> > > I compile KVM as module, so I can reload it with different parameters
> > > easily.
> >
> > arm64 doesn't (and cannot) build KVM as a module.
>
> Ah, I didn't realize it. But being able to patch EL2 from EL1 is probably
> more complicated than what is gained with it.
It is mostly pulling the rug from under your feet if you do that on
non-VHE systems, and make absolutely for things like pKVM.
> > > But I can make the module parameter read-write so that it is modifiable
> > > during runtime via /sys/module/kvm/parameters/ even when KVM is compiled
> > > into the kernel.
> >
> > I guess that'd be the next best thing.
>
> Ok, I will do that in v2 of the patch to be sent next week.
Thanks.
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2024-11-27 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 9:58 [PATCH] KVM: make uevents configurable Bernhard Kauer
2024-11-25 17:31 ` Marc Zyngier
2024-11-26 10:20 ` Bernhard Kauer
2024-11-26 11:23 ` Marc Zyngier
2024-11-27 8:38 ` Bernhard Kauer
2024-11-27 9:04 ` Marc Zyngier [this message]
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=86bjy1ujwo.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=bk@alpico.io \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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 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.