dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chia-I Wu <olvaffe@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: kraxel@redhat.com, gurchetansingh@chromium.org
Subject: [PATCH v2 0/3] drm/virtio: rework command batching
Date: Fri,  7 Feb 2020 14:13:56 -0800	[thread overview]
Message-ID: <20200207221359.187340-1-olvaffe@gmail.com> (raw)
In-Reply-To: <20200206192214.86818-1-olvaffe@gmail.com>

Hi,

This series replaces the global disable_notify state by command-level bools to
control vq kicks.  When command batching is applied to more places, this
prevents one process from affecting another process.

v2: update to this convention

  virtio_gpu_cmd_foo: add foo and commit
  virtio_gpu_add_foo: add foo but do not commit

However, the spinlock is now grabbed twice in both add and commit.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-02-07 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 19:22 [PATCH 0/2] drm/virtio: rework command batching Chia-I Wu
2020-02-06 19:22 ` [PATCH 1/2] drm/virtio: remove the global pending_notify state Chia-I Wu
2020-02-06 19:22 ` [PATCH 2/2] drm/virtio: remove the global disable_notify state Chia-I Wu
2020-02-07  8:22   ` Gerd Hoffmann
2020-02-07 22:13 ` Chia-I Wu [this message]
2020-02-07 22:13   ` [PATCH v2 1/3] drm/virtio: remove the global pending_notify state Chia-I Wu
2020-02-07 22:13   ` [PATCH v2 2/3] drm/virtio: never kick in virtio_gpu_queue_ctrl_sgs Chia-I Wu
2020-02-11 12:57     ` Gerd Hoffmann
2020-02-07 22:13   ` [PATCH v2 3/3] drm/virtio: remove the global disable_notify state Chia-I Wu

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=20200207221359.187340-1-olvaffe@gmail.com \
    --to=olvaffe@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gurchetansingh@chromium.org \
    --cc=kraxel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox