netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Aleksandr Mikhalitsyn" <aleksandr.mikhalitsyn@canonical.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	stefanha@redhat.com, "Jason Wang" <jasowang@redhat.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	kvm@vger.kernel.org, virtualization@lists.linux.dev,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	mcgrof@kernel.org
Subject: Re: [PATCH v2] vhost/vsock: specify module version
Date: Wed, 6 Nov 2024 04:07:44 -0500	[thread overview]
Message-ID: <20241106040705-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20241002071602.793d3e2d@kernel.org>

On Wed, Oct 02, 2024 at 07:16:02AM -0700, Jakub Kicinski wrote:
> On Mon, 30 Sep 2024 19:03:52 +0200 Aleksandr Mikhalitsyn wrote:
> > > At this point my question is, should we solve the problem higher and
> > > show all the modules in /sys/modules, either way?  
> > 
> > Probably, yes. We can ask Luis Chamberlain's opinion on this one.
> > 
> > +cc Luis Chamberlain <mcgrof@kernel.org>
> > 
> > >
> > > Your use case makes sense to me, so that we could try something like
> > > that, but obviously it requires more work I think.  
> > 
> > I personally am pretty happy to do more work on the generic side if
> > it's really valuable
> > for other use cases and folks support the idea.
> 
> IMHO a generic solution would be much better. I can't help but feel
> like exposing an arbitrary version to get the module to show up in 
> sysfs is a hack.
> 
> IIUC the list of built in modules is available in
> /lib/modules/*/modules.builtin, the user space can't read that?


So what are we doing about this? Aleksandr?

-- 
MST


  reply	other threads:[~2024-11-06  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29 18:21 [PATCH v2] vhost/vsock: specify module version Alexander Mikhalitsyn
2024-09-29 19:03 ` Michael S. Tsirkin
2024-09-30 12:28   ` Aleksandr Mikhalitsyn
2024-09-30 14:05     ` Michael S. Tsirkin
2024-09-30 14:31       ` Aleksandr Mikhalitsyn
2024-09-30 14:27 ` Stefano Garzarella
2024-09-30 14:43   ` Aleksandr Mikhalitsyn
2024-09-30 15:42     ` Stefano Garzarella
2024-09-30 17:03       ` Aleksandr Mikhalitsyn
2024-09-30 19:47         ` Andrew Lunn
2024-10-02 14:16         ` Jakub Kicinski
2024-11-06  9:07           ` Michael S. Tsirkin [this message]
2024-10-03 19:48         ` Luis Chamberlain
2024-10-03 20:55           ` Lucas De Marchi

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=20241106040705-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=aleksandr.mikhalitsyn@canonical.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux.dev \
    /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).