mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: Christian Brauner <brauner@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>, Hans de Goede <hans@hansg.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: MAINTAINERS: take over vboxsf from Hans de Goede
Date: Sun, 14 Jun 2026 21:19:36 +0100	[thread overview]
Message-ID: <ai8M2PK5vH7FPj3d@casper.infradead.org> (raw)
In-Reply-To: <198160170.1699942.1781464305401@kpc.webmail.kpnmail.nl>

On Sun, Jun 14, 2026 at 09:11:45PM +0200, Jori Koolstra wrote:
> > Op 14-06-2026 21:10 CEST schreef Jori Koolstra <jkoolstra@xs4all.nl>:
> > I have no major plans for vboxsf, but I do want to support passing
> > physical addresses to the host; the communication protocol seems to
> > allow for it and it would mean we can get rid of some kmap calls.

I would love that.  I looked at doing it when I did e300830fcc40
(convert to writepages), but it was a little beyond me.  I really didn't
want to try to do it without having a way to test it.

Any chance you could also add large folio support?  I don't think it
should be much extra work once you've done physical address support.

  reply	other threads:[~2026-06-14 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-14 19:10 Jori Koolstra
2026-06-14 19:11 ` Jori Koolstra
2026-06-14 20:19   ` Matthew Wilcox [this message]
2026-06-19  9:36     ` Jori Koolstra
2026-06-15  8:34 ` Hans de Goede
2026-06-17 13:00 ` Christian Brauner

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=ai8M2PK5vH7FPj3d@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=brauner@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hans@hansg.org \
    --cc=jkoolstra@xs4all.nl \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®