All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sebelev, Vladimir" <vladimir.sebelev@auriga.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Drap Anton <drapas86@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Drap, Anton" <anton.drap@auriga.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: RE: [PATCH v3] Loading new machines and devices from external modules
Date: Fri, 26 Aug 2022 07:51:20 +0000	[thread overview]
Message-ID: <8b584a6fb2cf48c6ac28a9d6ea488dcf@auriga.com> (raw)
In-Reply-To: <CAFEAcA-C87Qgyvc_yqtiecA9EBE50J9CZgQY5FiAqDm+pQx67Q@mail.gmail.com>

Hi Peter,

Anton previously sent explanation of our position. Nobody commented. Could you please comment on it? It's necessary for us to better understand your position. From our point of view technical ban of external modules loading doesn't solve any of mentioned problems, but makes VP developer life harder.

Best Regards,
Vladimir

-----Original Message-----
From: Peter Maydell <peter.maydell@linaro.org> 
Sent: Monday, August 22, 2022 12:23 PM
To: Drap Anton <drapas86@gmail.com>
Cc: qemu-devel@nongnu.org; Sebelev, Vladimir <vladimir.sebelev@auriga.com>; Drap, Anton <anton.drap@auriga.com>; Daniel P. Berrange <berrange@redhat.com>; Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v3] Loading new machines and devices from external modules

On Mon, 22 Aug 2022 at 09:53, Drap Anton <drapas86@gmail.com> wrote:
>
> From: "Drap, Anton" <anton.drap@auriga.com>

>     This patch is to add two parameters `add_machine` and `add_modinfo`.
> `add_machine` is to add machines from external modules.
> `add_modinfo` is to add devices from external modules, needed for a 
> new machine, for example.
> Additional, 'arch' parameter of QemuModinfo is changed to a list.

I don't think there's much point in your continuing to post versions of this patchset, because the answer remains "we don't want to do this, as a policy and design decision". Until and unless you persuade us that it's a good idea to change that decision, time spent on code changes doesn't seem like a good use of effort to me.

thanks
-- PMM

  reply	other threads:[~2022-08-26 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  8:50 [PATCH v3] Loading new machines and devices from external modules Drap Anton
2022-08-22  9:22 ` Peter Maydell
2022-08-26  7:51   ` Sebelev, Vladimir [this message]
2022-08-26 14:46     ` Peter Maydell
2022-08-26 15:03     ` Daniel P. Berrangé

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=8b584a6fb2cf48c6ac28a9d6ea488dcf@auriga.com \
    --to=vladimir.sebelev@auriga.com \
    --cc=anton.drap@auriga.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=drapas86@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.