mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Sasha Finkelstein <fnkl.kernel@gmail.com>
Cc: David Airlie <airlied@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Gurchetan Singh <gurchetansingh@chromium.org>,
	Chia-I Wu <olvaffe@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Simona Vetter <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org, asahi@lists.linux.dev
Subject: Re: [PATCH v2] drm/virtio: Align host mapping request to maximum platform page size
Date: Fri, 7 Feb 2025 18:38:59 +0300	[thread overview]
Message-ID: <b7eb131d-1ca6-44f1-aea1-ace991912c3e@collabora.com> (raw)
In-Reply-To: <CAMT+MTQrKWzNfsUqiDawCv=s84XOvUGwsrv34aqmZ6rR482OqA@mail.gmail.com>

On 2/6/25 18:17, Sasha Finkelstein wrote:
> On Wed, 29 Jan 2025 at 15:40, Dmitry Osipenko
> <dmitry.osipenko@collabora.com> wrote:
>> Otherwise, the proper solution would be to pass info about host's page
>> size to guest using extended virtio protocol.
> 
> It is not fully clear to me, as to what exactly is meant by that.
> IIUC, virtio is a spec managed externally, so does that mean
> that i should write to the virtio people to add the relevant bits
> to the specification?

Virtio people will only approve the new bits. You who will have to
research how to add new virtio feature, propose and discuss the virtio
spec change with virtio people till the change is accepted, implement
new feature in the code. Anyone can propose spec changes, the process is
documented and you may look up ML archives to find what other people did
for upstreaming new features.

Virtio spec is managed externally, but in reality is tightly coupled
with Linux, all virtio people are also Linux devs. For the first step
you may write a quick *kernel* RFC patches to spark the discussion. Cc
all relevant people, see how much interest will be in the new feature,
ask how to properly add the new property if unsure.

Could be that virtio crowd will reject the idea of having a common
generic property and then we may try to make it private to the
virtio-gpu device.

-- 
Best regards,
Dmitry

      reply	other threads:[~2025-02-07 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25 21:08 Sasha Finkelstein via B4 Relay
2025-01-27  7:31 ` Thomas Zimmermann
2025-01-27  9:05   ` Sasha Finkelstein
2025-01-29 14:39 ` Dmitry Osipenko
2025-02-06 15:17   ` Sasha Finkelstein
2025-02-07 15:38     ` Dmitry Osipenko [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=b7eb131d-1ca6-44f1-aea1-ace991912c3e@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=airlied@redhat.com \
    --cc=asahi@lists.linux.dev \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fnkl.kernel@gmail.com \
    --cc=gurchetansingh@chromium.org \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=olvaffe@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --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

all inboxes | Powered by JetHome®